Send data to Attentive Mobile¶

Attentive Mobile is a personalized mobile messaging platform that improves brand engagement with mobile consumers.

Note

Changes to audience segments are not immediately available in Attentive Mobile. Allow for up to 24 hours after the point at which Amperity has finished sending audience updates for them to be available.

This topic describes the steps that are required to send subscriber lists to Attentive Mobile from Amperity:

Get details
Add destination
Add data template

Get details¶

Attentive Mobile requires the following configuration details:

The username and passphrase with permission to write data to Attentive Mobile SFTP.
The remote folder to which Amperity will send data: /uploads.
The public key to use for PGP encryption, if required.
Review the subscriber list upload topic for specific requirements for how to format the CSV file.
Do not include header rows in output.

Add destination¶

Configure Amperity to send data to Attentive Mobile using SFTP.

Important

Review the subscriber list upload topic for specific requirements for how to format the CSV file. Do not include header rows in output.

To add a destination

From the Destinations tab, click Add Destination. This opens the Add Destination dialog box.
Enter the name of the destination and a description. For example: “Attentive Mobile” and “This sends query results to “Attentive Mobile”.
From the Plugin drop-down, select Attentive Mobile.

This automatically selects attentive-mobile as the Credential Type and assigns sftp.attentivemobile.com as the location to which data is sent.
From the Credential drop-down, select Create a new credential. This opens the Create New Credential dialog box. Enter a name for the credential (typically “Attentive Mobile”), and then enter the username and password required to access this SFTP location.
Under Settings, enter the path to the remote folder.
From the File Format drop-down, select CSV.
Add a single character to be used as an escape character in the output file. (This should match the escape character required by Attentive Mobile.)

Note

If an escape character is not specified and quote mode is set to “None” this may result in unescaped, unquoted files. When an escape character is not specified, you should select a non-“None” option from the Quote Mode setting.
Specify the encoding method. Encoding method options include “Tar”, “Tgz”, “Zip”, “GZip”, and “None”.
Add the PGP public key that is used to encrypt files sent to Attentive Mobile.
Optional. Specify the line ending type: LF or CRLF.
Optional. Set the quote mode.

Note

If the quote mode is set to “None” and the Escape Character setting is empty this may result in unescaped, unquoted files. When quote mode is “None”, you should specify an escape character.
Optional. Select Include success file upon completion to add a .DONE file to indicate when an orchestration has finished sending data.

Tip

If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the .DONE file.
Optional. Select Include header row in output files if headers are included in the output.
Select Allow customers to use this destination.
Select Allow orchestrations from users with limited PII access. (A user with limited PII access has been assigned the Restrict PII Access policy option.)
Click Save.

Add data template¶

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

You have two options for setting up data templates for Attentive Mobile:

For use with campaigns
For use with orchestrations

About filename templates¶

A filename template defines the segment name as it will appear in the Segments tab in Attentive Mobile.

The following table shows how your segment name will appear in Attentive Mobile. These examples are for a one-time buyer campaign that is attempting to win a second purchase. The campaign is named “Winback” and it has sub-audiences for “Dress Shirts”, “Jeans”, and “Shoes”. Keep these patterns in mind when naming campaigns, recipient groups, and sub-audiences within your campaigns.

Pattern	Segment name(s)	Description
(empty)	WinbackDressShirts WinbackJeans WinbackShoes	An empty filename template setting is the equivalent of {{ campaign_name }}{{ given_name }}.
{{ campaign_name }}	Winback	Use this pattern for campaigns that do not have more than one recipient group or have sub-audiences. This will use the name of the campaign as the name of the segment in Attentive Mobile. Tip Use {{ campaign_name }} instead of {{ list_name }}.
{{ campaign_name }}_{{ given_name }}	Winback_DressShirts Winback_Jeans Winback_Shoes	Use this pattern for campaigns that have more than one recipient group and/or have sub-audiences. You may use an underscore (`_`) or a hyphen (`-`): {{ campaign_name }}_{{ given_name }} or {{ campaign_name }}-{{ given_name }}. You may put them next to each other (without using an underscore or hyphen): {{ campaign_name }}{{ given_name }}. You may switch the ordering: {{ given_name }}_{{ campaign_name }}. Tip Be sure to use descriptive names for campaigns and recipient groups and be careful to not use the default recipient group names when sending campaigns to Attentive Mobile. This will ensure that downstream users in Attentive Mobile will be able to understand what each segment is for and won’t have to view default naming patterns like “Winback_Recipient1”, “WinbackRecipient2”, etc.
{{ given_name }}	DressShirts Jeans Shoes	Use this pattern when to only use the names of recipient groups as segment names in Attentive Mobile. This will omit the name of the campaign and the name of the sub-audience from the segment name.

Important

The filename template, as used with Attentive Mobile (and unlike how it is used with other destinations), does not build a file name. Instead the filename template defines which strings (campaign and/or recipient group) will be used as the name of a segment in Attentive Mobile. Spaces in campaign and recipient group names are removed.

for campaigns¶

You can configure Amperity to send campaigns to Attentive. These results are sent from the Campaigns tab. Results default to a list of email addresses, but you may configure a campaign to send additional attributes to Attentive Mobile.

To add a data template for campaigns

From the Destinations tab, open the menu for a destination that is configured for Attentive Mobile, and then select Add data template.

This opens the Add Data Template dialog box.
Enter the name of the data template and a description. For example: “Attentive Mobile email list” and “Send email addresses to Attentive Mobile.”
Enable the Allow customers to use this data template option, and then enable the Make available to campaigns option. This allows users to send campaign results from Amperity to Attentive Mobile.
Verify all template settings and make any required updates.
Click Save.

for orchestrations¶

You can configure Amperity to send query results to Attentive. These results are sent using an orchestration and will include all columns that were specified in the query.

To add a data template for orchestrations

From the Destinations tab, open the menu for a destination that is configured for Attentive Mobile, and then select Add data template.

This opens the Add Data Template dialog box.
Enter the name of the data template and a description. For example: “Attentive Mobile customer profiles” and “Send email addresses and customer profiles to Attentive Mobile.”
Enable the Allow customers to use this data template option. This allows users to build queries, and then configure orchestrations that send results from Amperity to a configured destination.
Optional. Enable the Allow orchestrations from customers with limited PII access option. This allows users who have been assigned the Restrict PII Access policy option to send results from Amperity.
Verify all template settings and make any required updates.
Click Save.