Deployteq

A Deployteq integration sends campaign, subscriber, and custom data from Deployteq into SEINō. Use this page to connect Deployteq, see what SEINō receives, and extend the default setup if you need more data.

Supported channels

Deployteq uses different broadcast types for each channel.

Channel	Broadcast type	Description
Email	MAIL	Email sent via the Campaign Builder flow.
Email	QUICKMAIL	Scheduled email.
Email	SINGLEMAIL	One-to-one CRM email.
Email	SPLITRUNWINNER	Winner of a split-run campaign.
Email	SPLITRUNPART	Part of a split-run campaign. It shares a Campaign ID with the other parts and the winner.
Email	SMTP	Email sent via the SMTP protocol.
SMS	SMS	SMS message.
WhatsApp	WHATSAPPMESSAGE	WhatsApp message.
App push	PUSH	App push notification.

See the Deployteq Analytics API data fields for the full list of broadcast types and field definitions.

Set up integration

Connect Deployteq to SEINō and start syncing campaign data with the standard integration setup.

SEINō uses the Deployteq Analytics API. This is a paid API module that you can enable in your Deployteq store.

Follow these steps to connect Deployteq to SEINō:

1. Install the Analytics API app via the Deployteq store.
2. Install the Auth0 app via the Deployteq store.
3. Create a new app in Deployteq and generate a client ID and client secret.
4. Add and enable the Deployteq integration in SEINō.
5. Copy the client ID and secret into SEINō.
6. Check that SEINō returns the Deployteq brand name. That confirms the credentials are correct.
7. Save the integration to finish setup.
8. SEINō automatically imports historical data.

You can add multiple Deployteq brands to a single workspace. See Multiple integrations for more on that setup.

SEINō automatically imports two years of historical data. Any metadata you add later only syncs from the moment those fields are present in your template objects.

The initial import can take anywhere from 10 minutes to 24 hours, depending on your data size. After the import finishes, SEINō sends an email notification.

Campaign dataset

The Deployteq integration exposes the following default campaign-level data in the Campaigns dataset in SEINō.

Dimensions

Dimension	Description
Brand	Brand name in Deployteq. Only shown if you integrate multiple Deployteq brands.
Broadcast type	Type of broadcast or message sent.
Campaign ID	Unique identifier for the campaign.
Campaign Name	Display name of the campaign.
Content name	Name of the content or message version.
Mailing type	Mailing category or type.
Send date	Date the message was sent.
Event date	Date of the event recorded for the campaign.
Subject	Email subject line.
Send date day	Day component of the send date.
Send date week	Week component of the send date.
Send date month	Month component of the send date.
Send date year	Year component of the send date.
Send date year week	Year-week grouping for the send date.

Metric

Metric	Description
Sent	Number of messages sent.
Delivered	Number of messages successfully delivered.
Opens	Number of unique opens.
Open rate	Open rate calculated as a percentage of delivered messages.
Opens incl. bots	Opens including bot activity.
Open rate incl. bots	Open rate including bot activity.
Clicks unique	Number of unique clicks.
Click rate	Click rate calculated as a percentage of delivered messages.
Click to open rate	Click-to-open rate.
Clicks all	Total clicks including non-unique activity.
Clicks unique incl. bots	Unique clicks including bot activity.
Click rate incl. bots	Click rate including bot activity.
Bot opens	Number of opens attributed to bots.
Bot clicks	Number of clicks attributed to bots.
Soft bounces	Number of soft bounces.
Soft bounce rate	Soft bounce rate.
Hard bounces	Number of hard bounces.
Hard bounce rate	Hard bounce rate.
Complaints	Number of complaints received.
Complaint rate	Complaint rate.
Unsubscribes	Number of unsubscribe events.
Unsubscribe rate	Unsubscribe rate.
Deliverability	Deliverability rate.
Send date count	Count of distinct send dates.

Send additional campaign data

You can send additional data to SEINō by adding a Smarty variable named $metadata in a Deployteq template or object. Use this when you want to include values that are unique to each customer.

Use this pattern in your Deployteq template:

{{$metadata['key1'] = 'value'}}
{{$metadata['key2'] = $key}}

Default data attributes

SEINō also supports a set of default attributes that you can send with your Deployteq data:

{{$metadata['seino_market'] = $market}}
{{$metadata['seino_preheader'] = $preheader}}
{{$metadata['seino_url'] = "{{broadcast field='url'}}"}}
{{$metadata['seino_audience_name'] = "{{broadcast field='sourcename'}}"}}
{{$metadata['seino_audience_source'] = "{{broadcast field='sourcetype'}}"}}

The examples use $market and $preheader as placeholders.

You can add as many custom data attributes as you want. SEINō receives and stores them automatically. To make the data useful in your workspace, the SEINō team must map your attributes first.

If you want to add more data to your SEINō workspace, contact support@seino.ai.

Sync subscriber list sizes

SEINō can sync subscriber list sizes by snapshotting the list contents in Deployteq and comparing each day’s snapshot with the previous one. To do this, export a daily list of subscriber IDs. You can select subscribers from Deployteq profiles or groups. We recommend creating an export campaign that selects the subscribers you want and exports them through the Deployteq campaign object into your Google Cloud bucket.

Configure exports

1. Get the Google Cloud bucket credentials for your workspace in SEINō.
2. Create a new remote subfolder:
   • Folder name: SEINō remote Google Bucket
   • Type: Google Storage Bucket
   • Bucket name: paste your bucket name here
   • Path: deployteq_profiles
   • Google service account key: paste your JSON service key code here
3. Create a new campaign:
   • Start on interval: once per day at 1:00 am.
   • For each profile you want to calculate in SEINō:
     • Select the profile you want to monitor in SEINō.
     • Configure export:
       • Add system field Id.
       • Select the remote folder SEINō remote Google Bucket as the export destination.
       • Export file name: {{year type=yyyy}}-{{month type=mm}}-{{day type=dd}}_PROFILE DESCRIPTION.csv
       • PROFILE DESCRIPTION is the profile name shown in SEINō. For example:
         • Example name in Deployteq: {{year type=yyyy}}-{{month type=mm}}-{{day type=dd}}_**NL - All subscribers**.csv
         • Output in SEINō: NL - All subscribers
4. Start the campaign.

Refresh cadence

SEINō refreshes Deployteq data at these times:

• 05:17 UTC
• 08:17 UTC
• 11:17 UTC
• 14:17 UTC
• 17:17 UTC

Code examples

The examples below require deeper Deployteq knowledge and more technical skill. Reach out to support@seino.ai if you need technical support.

Ignore specific link clicks

You can ignore clicks in SEINō reporting by adding the seino_ignore parameter in the URL.

Example:

<a href="https://www.mywebsite.com?seino_ignore=true">
  This click will be ignored by SEINō reporting
</a>

SpotlerActive RFM segment

In this example, we loop through the Deployteq data model squeezely_segments, where all SpotlerActive segments are stored, and retrieve the active SpotlerActive segment ID for the customer. Put the Smarty code in your template objects. Make sure to use your own segment IDs.

Example:

{{foreach from=$customer.squeezely_segments|filter:"active":'yes' item='segment'}}
  {{if $segment.id == "90"}}{{$rfm = "Lost customers"}}
    {{elseif $segment.id == "89"}}{{$rfm = "Hibernating"}}
    {{elseif $segment.id == "88"}}{{$rfm = "About to lose"}}
    {{elseif $segment.id == "87"}}{{$rfm = "At risk"}}
    {{elseif $segment.id == "86"}}{{$rfm = "About to sleep"}}
    {{elseif $segment.id == "85"}}{{$rfm = "Need attention"}}
    {{elseif $segment.id == "84"}}{{$rfm = "Promising"}}
    {{elseif $segment.id == "83"}}{{$rfm = "New customers"}}
    {{elseif $segment.id == "82"}}{{$rfm = "Potential loyalists"}}
    {{elseif $segment.id == "81"}}{{$rfm = "Loyal"}}
    {{elseif $segment.id == "80"}}{{$rfm = "Champions"}}
  {{/if}}
{{/foreach}}
{{if empty($rfm)}}
  {{$rfm = "Not set"}}
{{/if}}
{{$metadata['seino_rfm'] = "$rfm"}}

Create buckets based on dates

In this Smarty example, we use the first order date from a customer option field, a custom Deployteq field, to create custom buckets. In this example, we use field E30. Make sure to use the correct ID for your custom field.

<!-- Current date -->
{{$current_day = "{{currentdate|@strtotime format='%Y-%m-%d'}}"}}
{{$current_y = $current_day|date_format:"%Y"}}
{{$current_m = $current_day|date_format:"%m"}}
{{$current_d = $current_day|date_format:"%d"}}

<!-- First Order Buckets -->
{{customer_option|htmlentities field='E30' assign='first_order'}}
{{if $first_order}}
  {{$first_order = $first_order|@strtotime}}
  {{$first_y = $first_order|date_format:"%Y"}}
  {{$first_m = $first_order|date_format:"%m"}}
  {{$first_d = $first_order|date_format:"%d"}}

  {{assign var=months_since value=(($current_y - $first_y) * 12) + ($current_m - $first_m)}}
  {{if $current_d < $first_d}}
    {{assign var=months_since value=$months_since-1}}
  {{/if}}

  {{if $months_since < 6}}
    {{$first_bucket = "0 - 6 months"}}
  {{elseif $months_since < 9}}
    {{$first_bucket = "6 - 9 months"}}
  {{elseif $months_since < 12}}
    {{$first_bucket = "9 - 12 months"}}
  {{elseif $months_since < 15}}
    {{$first_bucket = "12 - 15 months"}}
  {{else}}
    {{$first_bucket = "15 - 24+ months"}}
  {{/if}}
{{else}}
  {{$first_bucket = "No orders"}}
{{/if}}

<!--{$metadata['seino_first_bucket'] = $first_bucket}-->

Link web sessions to custom dimensions

If you push additional data from Deployteq and want to link website events to the same level, you need to add the additional data to your UTM tags. Best practice is to add the additional data points to utm_term as an MD5 hash.

Example:

<!-- Set global utm_term with hashed value -->
{{$globals.utm_term = "{{$first_bucket}}-{{$rfm}}"|md5}}

<!-- Set global utm_term with hashed value -->
<a href="https://www.mywebsite.com/?utm_term={{$globals.utm_term}}">
  Click me
</a>