Pull from Cordial

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.

Cordial can send contact and activity data to Amperity for use with a variety of email engagement workflows.

This topic describes the steps that are required to pull contact and activity data to Amperity from Cordial:

  1. Get details

  2. Add courier

  3. Run courier

  4. Review feed and domain table

  5. Add to courier group

Get details

Cordial requires the following configuration details:

  1. The API key and secret for Cordial.


Use SnapPass to securely share configuration details for Cordial between your company and your Amperity representative.

Add courier

A courier brings data from an external system to Amperity. A courier relies on a feed to know which fileset to bring to Amperity for processing.

To add a courier

  1. From the Sources page, click Add Courier. The Add Source page opens.

  2. Find, and then click the icon for Cordial. The Add Courier page opens.

    This automatically selects cordial as the Credential Type.

  3. Enter the name of the courier. For example: “Cordial”.

  4. From the Credential field, select an existing credential or select Create a new credential.

    To add a credential, enter the name of the credential, a description, the Cordial API key and secret. Click Save.

  5. Under Select Data, enable Contacts or Contacts Activities.

  6. Click Create.

Run courier manually

Run the courier again. This time, because the load operations are present and the feeds are configured, the courier will pull data from Cordial.

To run the courier manually

  1. From the Sources tab, open the    menu for the courier with updated load operations that is configured for Cordial, and then select Run. The Run Courier dialog box opens.

  2. Select the load option, either for a specific time period or all available data. Actual data will be loaded to a domain table because the feed is configured.

  3. Click Run.

    This time the notification will return a message similar to:

    Completed in 5 minutes 12 seconds

Review feed and domain table

After running the Cordial courier a feed is created automatically with a pre-defined list of fields. You may apply semantic tags to these fields and you may make the domain table available to Stitch, depending on your use cases. A domain table named Cordial:Email will be added.

Email contacts

The feed and domain table for email contacts will match the following fields:

The contacts ingress type will only capture all data, regardless of if a date restriction is placed in the UI.

  • _id (assigned the ck semantic tag)

  • emailAddress (assigned the email semantic tag)

  • cID

  • createDate

  • ID

  • subscribedAt

  • subscribeStatus

Contact activities

Contact activities capture all activities or events - opens, clicks, and custom actions created by the user. Contact activities are linked with a customer via their primary and secondary identifier. The secondary identifier can have multiple values i.e. email address, phone number, customer ID, etc. For this reason, contact activities can encompass email activity, web engagement, etc.

The feed and domain table for contact activities will match the following fields:

  • _id (assigned the ck semantic tag)

  • browser

  • cID

  • jobID

  • device

  • fromSubscribeStatus

  • platform

  • activityDate

  • toSubscribeStatus

  • activityType

  • fromSubscribeStatus

Add to courier group

A courier group is a list of one (or more) couriers that are run as a group, either ad hoc or as part of an automated schedule. A courier group can be configured to act as a constraint on downstream workflows.

To add the courier to a courier group

  1. From the Sources tab, click Add Courier Group. This opens the Create Courier Group dialog box.

  2. Enter the name of the courier. For example: “Cordial”.

  3. Add a cron string to the Schedule field to define a schedule for the orchestration group.

    A schedule defines the frequency at which a courier group runs. All couriers in the same courier group run as a unit and all tasks must complete before a downstream process can be started. The schedule is defined using cron.

    Cron syntax specifies the fixed time, date, or interval at which cron will run. Each line represents a job, and is defined like this:

    ┌───────── minute (0 - 59)
    │ ┌─────────── hour (0 - 23)
    │ │ ┌───────────── day of the month (1 - 31)
    │ │ │ ┌────────────── month (1 - 12)
    │ │ │ │ ┌─────────────── day of the week (0 - 6) (Sunday to Saturday)
    │ │ │ │ │
    │ │ │ │ │
    │ │ │ │ │
    * * * * * command to execute

    For example, 30 8 * * * represents “run at 8:30 AM every day” and 30 8 * * 0 represents “run at 8:30 AM every Sunday”. Amperity validates your cron syntax and shows you the results. You may also use crontab guru to validate cron syntax.

  4. Set Status to Enabled.

  5. Specify a time zone.

    A courier group schedule is associated with a time zone. The time zone determines the point at which a courier group’s scheduled start time begins. A time zone should be aligned with the time zone of system from which the data is being pulled.


    The time zone that is chosen for an courier group schedule should consider every downstream business processes that requires the data and also the time zone(s) in which the consumers of that data will operate.

  6. Set SLA? to False. (You can change this later after you have verified the end-to-end workflows.)

  7. Add at least one courier to the courier group. Select the name of the courier from the Courier drop-down. Click + Add Courier to add more couriers.

  8. Click Add a courier group constraint, and then select a courier group from the drop-down list.

    A wait time is a constraint placed on a courier group that defines an extended time window for data to be made available at the source location.

    A courier group typically runs on an automated schedule that expects customer data to be available at the source location within a defined time window. However, in some cases, the customer data may be delayed and isn’t made available within that time window.

  9. For each courier group constraint, apply any offsets.

    An offset is a constraint placed on a courier group that defines a range of time that is older than the scheduled time, within which a courier group will accept customer data as valid for the current job. Offset times are in UTC.

    A courier group offset is typically set to be 24 hours. For example, it’s possible for customer data to be generated with a correct file name and datestamp appended to it, but for that datestamp to represent the previous day because of the customer’s own workflow. An offset ensures that the data at the source location is recognized by the courier as the correct data source.


    An offset affects couriers in a courier group whether or not they run on a schedule.

  10. Click Save.