Configure campaigns for Monetate

Monetate offers solutions for customer segmentation and targeting, campaign testing and optimization, 1:1 personalization, audience insights, and customer recommendations.

Configure Amperity to send CSV files to Monetate.

Get details

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

	Credential settings Credentials for Monetate require a “username” and “passphrase”. Set the host name to “sftp.monetate.com”.
	Required configuration settings File format Configure Amperity to send CSV files to Monetate. Some file formats allow a custom delimiter. Choose the “Custom delimiter” file format, and then add a single character to represent the custom delimiter. Remote folder The remote folder to which Amperity sends data. Use a forward slash–“/”–as the first character for this value. For example: “/folder”. If the path to the remote folder has 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 Monetate are optional.
	Monetate requirements Note Files sent to Monetate must: Not exceed 10 GB uncompressed or 100 million rows Contain at least one column and may not contain more than 30 Include a single row per unique identifier Use double quotes around fields that include a comma Include a header row for new datasets Review the customer dataset upload requirements for additional information.

Configure credentials

Configure credentials for Monetate before adding a destination.

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

To configure credentials for Monetate

	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 Monetate. 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 vary by credential type. For the “monetate” credential type, configure settings, and then click Save. Hostname Required Required. The host name for Monetate. For example: “sftp.monetate.com”. Passphrase Required The passphrase associated with the username. Username Required Required. A username with access to Monetate. This username must have permission to write data to the remote folder to which Amperity sends data.

Add destination

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

To add a destination for Monetate

	Open the Destinations page, select the New destinations button, and then select Campaign. To configure a campaign for Monetate, do one of the following: Click the row in which Monetate is located. Destinations list alphabetically and you can scroll up and down the list. Search for Monetate. Start typing “mone”. The list filters to show only matching destinations. Select “Monetate”.
	Select the credential for Monetate from the Credential dropdown, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Monetate.
	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. 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 limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	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 are 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 Monetate. Filename template A filename template defines the naming pattern for files that 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 uses 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 “None” and an escape character is not specified. Remote folder Required The remote folder to which Amperity sends data. Use a forward slash–“/”–as the first character for this value. For example: “/folder”. If the path to the remote folder has 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. Split outputs Split delimiter-separated output–CSV, PSV, TSV, or files with custom delimiters–into multiple files to ensure downstream file limits are not exceeded. Choose “Rows” and set “Rows limit” to a value between “50000” and “10000000”. This is the maximum number of rows for split output files. Choose “Megabytes” and set “Megabytes limit” to a value between “1 MB” and “2000 MB”. This is the maximum file size. Additional configuration is required for filename templates. Set the value of “Split filename template” to “{{file_number}}.csv” to apply a unique seven digit left-padded integer to the filename. For example: “0000001.csv”, “0000002.csv”, and “0000003.csv”. Use the “Split file directory template” to name the directory into which split files are added. For example: if the value of “Split file directory template” is {{now|format:’YYYY’}}.tgz and the value of “Split filename template” is “{{file_number}}.csv” Amperity will output a gzipped tarball named “2025.tgz” with subfiles named “0000001.csv”, “0000002.csv”, and “0000003.csv”. Use Zip64? Enable to apply Zip64 data compression to large files. Campaign file settings Under Campaign settings select one of the following: Send audience list as separate files This option sends a standalone file for each treatment group sending an audience to Monetate. Send audience lists as a single file This option consolidates all treatment groups into a single file before sending the audience to Monetate.
	After configuring this destination users may send campaigns to Monetate.

Workflow actions

A workflow will occasionally show an error that describes what prevented a workflow from completing successfully. These first appear as alerts in the notifications pane. The alert describes the error, and then links to the Workflows tab.

Open the Workflows page to review a list of workflow actions, choose an action to resolve the workflow error, and then follow the steps that are shown.

	You may receive a notifications error for a configured Monetate destination. This appears as an alert in the notifications pane on the Destinations tab. If you receive a notification error, review the details, and then click the View Workflow link to open this notification error in the Workflows page.
	On the Workflows page, review the individual steps to determine which step(s) have errors that require your attention, and then click Show Resolutions to review the list of workflow actions that were generated for this error.
	A list of individual workflow actions are shown. Review the list to identify which action you should take. Some workflow actions are common across workflows and will often be available, such as retrying a specific task within a workflow or restarting a workflow. These types of actions can often resolve an error. In certain cases, actions are specific and are shown when certain conditions exist in your tenant. These types of actions typically must be resolved and may require steps that must be done upstream or downstream from your Amperity workflow. Amperity provides a series of workflow actions that can help resolve specific issues that may arise with Monetate, including: Invalid credentials SFTP site unavailable
	Select a workflow action from the list of actions, and then review the steps for resolving that error. After you have completed the steps in the workflow action, click Continue to rerun the workflow.

Invalid credentials

The credentials that are defined in Amperity are invalid.

To resolve this error, verify that the credentials required by this workflow are valid.

1. Open the Credentials page.

2. Review the details for the credentials used with this workflow. Update the credentials for Monetate if required.

3. Return to the workflow action, and then click Resolve to retry this workflow.

SFTP site unavailable

The SFTP site at “sftp.monetate.com” is unavailable. This may be due to any of the following issues:

• A configuration error within Amperity.

• The SFTP server is unavailable or unresponsive.

• The SFTP server does not have enough storage space.

• Too many connection attempts were made to the SFTP server.

Note

Amperity will make multiple attempts to connect to an SFTP server before showing this workflow error.

To resolve this error, do any of the following.

1. Verify the configuration for “sftp.monetate.com”.

2. Verify that the SFTP server is available and responsive.

3. Verify the amount of storage space that is available on the SFTP server.

4. Decrease the number of couriers in Amperity that are configured to connect to “sftp.monetate.com”.

5. Return to the workflow action, and then click Resolve to retry this workflow.