Send email and phone lists to Attentive

Note

This topic contains information about configuring a destination that sends query results to Attentive using orchestrations. To configure a destination that sends audiences to Attentive using campaigns see this topic .

Amperity uses the subscriber segment upload process to manage segments. This process does not use an endpoint and is not subject to Attentive API rate limits . Updates appear on the Segments page within your audience in Attentive.

Why are there two ways to send data to Attentive?

Amperity uses the Subscriptions and Custom Attributes endpoints to send custom profile attributes to Attentive. Use these attributes to apply customizable data or characteristics to each of your subscribers, and then use that information to build segments for use with campaigns and journeys.

Note

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

Get details

Review the following details before configuring credentials for Attentive and before configuring Amperity to send CSV files to Attentive.

Credential settings Credentials for Attentive require a “username” and “passphrase”. Set the hostname to “ftp5.attentivemobile.com”.

Required configuration settings File format Configure Amperity to send CSV files to Attentive. Some file formats allow a custom delimiter. Choose the “Custom delimiter” file format, and then add a single character to represent the custom delimiter. Review the subscriber segment upload topic for specific requirements for how to format the CSV file. Remote folder The remote folder to which Amperity will send data. A “/” (forward slash) must be used as the first character for this value. For example: “/folder”. For example: “/folder”. If the path to the remote folder contains a space, use a backslash (\) character to escape that space. For example, a folder named “From ACME” should be entered as “From\ ACME”. Note All other Amperity file format settings for Attentive are optional.

Configure credentials

Configure credentials for Attentive before adding a destination.

An individual with access to Attentive should use SnapPass to securely share “username”, “hostname”, and “passphrase” details with the individual who will configure Amperity.

To configure credentials for Attentive

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Attentive. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential are determined by the credential type. For the “attentive-mobile” credential type, configure settings, and then click Save. Hostname Required Required. The hostname for Attentive. For example: “ftp5.attentivemobile.com”. Passphrase Required The passphrase that is associated with the username. Username Required Required. A username with access to Attentive. This username must be allowed to write data to the remote folder to which Amperity will send data.

Add destination

Use a sandbox to configure a destination for Attentive. Before promoting your changes, send a test audience, and then verify the the results in Attentive. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Attentive

	Open the Destinations page, and then click the Add destination button. To configure a destination for Attentive, do one of the following: Click the row in which Attentive is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Attentive. Start typing “att”. The list will filter to show only matching destinations. Select “Attentive”.
	Select the credential for Attentive from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Attentive.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Important Be sure to use “Segments” in the destination title so that users of Amperity who will send segments to Attentive will be able to identify this destination. Review the subscriber segment upload topic for specific requirements for how to format the CSV file. Do not include header rows in output. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
	Configure the following settings, and then click “Save”. Compression The compression format to apply to the file. May be one of “GZIP”, “None”, “TAR”, “TGZ”, or “ZIP”. Escape character The escape character to use in the file output. Applies to CSV, TSV, PSV, and custom delimiter file types. When an escape character is not specified and the quote mode is “None” files may be sent with unescaped and unquoted data. When an escape character is not specified, you should select a non-“None” option as the quote mode. File format Required Configure Amperity to send CSV files to Attentive. Review the subscriber segment upload topic for specific requirements for how to format the CSV file. Filename template A filename template defines the naming pattern for files that are sent from Amperity. Specify the name of the file, and then use Jinja-style string formatting to append a date or timestamp to the filename. Header Enable to include header rows in output files. Line ending The line ending to use in file output. May be one of “LF” or “CRLF”. PGP public key The PGP public key that Amperity will use to encrypt files. Quote mode The quote mode to use within the file. May be one of “all fields”, “all non-NULL fields”, “fields with special characters only”, “all non-numeric fields” or “None”. Unescaped, unquoted files may occur when quote mode is set to “None” and an escape character is not specified. Remote folder Required The remote folder to which Amperity will send data. A “/” (forward slash) must be used as the first character for this value. For example: “/folder”. For example: “/folder”. If the path to the remote folder contains a space, use a backslash (\) character to escape that space. For example, a folder named “From ACME” should be entered as “From\ ACME”. Success file Enable to send a “.DONE” file when Amperity has finished sending data. If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the “.DONE” file. Use Zip64? Enable to apply Zip64 data compression to very large files.
	After this destination is configured, users may configure Amperity to: Use orchestrations to send query results Use orchestrations and campaigns to send audiences Use orchestrations and campaigns to send offline events to Attentive.

About filename templates

A filename template defines how the names of segments and campaigns will appear in Attentive.

The following table shows how your segment name will appear in Attentive. These examples represent 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 types of patterns in mind when naming campaigns, treatment groups, and sub-audiences within your campaigns that will be sent to Attentive.

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