About destinations

Destinations are connections between Amperity and downstream systems that enable users of Amperity to send data to those systems.

A destination is a connection between Amperity and a downstream system that enables users of Amperity to send data to that system.

After a destination is configured, users of Amperity can:

• Use orchestrations to send the results of any query to any configured destination.

• Use segments to define audiences, and then assign those segments to single-touch campaigns or to nodes in a journey. More than one destination can be configured for a campaign or for a node in a journey.

Add destinations

To add destinations to your Amperity tenant, do the following:

1. Get details

2. Configure credentials

3. Add destination

Get details

Each destination requires configuration, such as:

• Providing credentials that allow Amperity to access the downstream location

• Ensuring that certain fields are named in certain ways

• Configuring Amperity to send the correct file type for file-based destinations

• Configuring Amperity for audience identifiers, such as audience names, list IDs, or activation IDs

Configuration requirements are unique to each destination and use case. Review the “Get details” section for each destination that your brand wants to configure in Amperity. Review any links to external documentation to help ensure that your brand understands destination-specific requirements.

After a destination is configured, run a test using a small audience. Verify that the data has arrived correctly. Make adjustments, if necessary, before sending an audience that will be used with your brand’s marketing activity.

Configure credentials

Use the Credentials page to view and manage credentials for data sources and destinations. After you have added a credential for a destination you can configure Amperity to send data to that destination.

Add destination

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

To add a destination

	Open the Destinations page, and then click the Add destination button. To configure a destination for a destination, do one of the following: Click the row in which a destination is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for a destination. Start typing the first three characters of the destination. The list will filter to show only matching destinations. Select the plugin for the destination.
	Select the credential for a destination 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 a destination.
	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 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”. Settings are documented on the individual pages for each destination.
	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 a destination.