Send audiences to Cordial¶
Note
This topic contains information about configuring a destination that sends query results to Cordial using orchestrations. To configure a destination that sends audiences to Cordial using campaigns see this topic .
Cordial is a cross-channel marketing and data platform that collects all of your customer data in one platform for use with audience segments, trends, and automated customer experiences.
Use Amperity to manage contacts–attributes and list membership–in Cordial using the following REST APIs:
Account Contact Attributes to create contact attributes. Attributes that do not exist in Cordial are added as custom contact attributes.
Account Lists to fetch, create, and clear account lists, to which contacts are associated. An account list is overwritten each time results are sent from Amperity. An email address is added when it is not already a contact, after which it is assigned the subscribed status. An email address that is already a contact will retain its assigned subscription status.
Contact Imports to import contacts to Cordial, and then associate contacts to the account list.
Jobs to monitor the import job for completion.
Build a query or segment that contains the email field, along with any other fields that you want created or updated in Cordial and represented as contact attributes.
Note
Amperity recommends using the Cordial API to send email lists from Amperity to Cordial.
However, if you prefer to send a CSV or JSON file (one-time or recurring) instead of using the Cordial API you may configure Cordial Data Automations , and then enable that workflow using any of these destinations: SFTP, Amazon S3, or Google Cloud Storage.
Get details¶
Review the following details before configuring credentials for Cordial and before configuring Amperity to send email lists to Cordial.
|
Credential settings API key
API URL
Tip Use the IP address for allowlists for Amperity to configure the allowlist for the Cordial API. |
|
|
Required configuration settings Audience primary key
List name (Required at orchestration)
Subscription status
|
|
|
Cordial Rest API configuration The following Cordial REST API methods must be enabled: GET /accountcontractattributes
POST /accountcontractattributes
GET /accountlists
POST /accountlists
PUT /accountlists/{key}/clear
POST /contactimports
GET /jobs/{id}
|
Configure credentials¶
Configure credentials for Cordial before adding a destination.
An individual with access to Cordial should use SnapPass to securely share “API key” and “API URL” details with the individual who will configure Amperity.
To configure credentials for Cordial
|
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 Cordial. 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 “cordial” credential type, configure settings, and then click Save. API key
API URL
|
Add destination¶
Use a sandbox to configure a destination for Cordial. Before promoting your changes, send a test audience, and then verify the the results in Cordial. After the end-to-end workflow has been verified, push the destination from the sandbox to production.
To add a destination for Cordial
|
|
Open the Destinations page, and then click the Add destination button. 
To configure a destination for Cordial, do one of the following:
|
|
|
Select the credential for Cordial 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 Cordial. |
|
|
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”. Audience primary key
List name (Required at orchestration)
Subscription status
|
|
After this destination is configured, users may configure Amperity to:
to Cordial. |