Experian Marketing Suite cross-channel marketing platform empowers brands to manage and execute all customer interactions within a single system, in real-time—removing the need for multiple, disparate platforms and individual channel vendors. This article describes how to configure Experian Marketing Suite in your Customer Data Hub account.

Table of Contents Placeholder

Requirements

  • Experian Marketing Services Account
  • Consumer Key (found on the API ACCESS screen)
  • Consumer Secret (found on the API ACCESS screen)

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Insert Data to Table

Configure Settings

Go to the Connector Marketplace and add a new Experian Marketing Suite connector. Read the Connector Overview article for general instructions on how to add a connector.

To configure your vendor, follow these steps:

  1. In the Configure tab, provide a title for the connector instance.
  2. (Optional) Enter the Client ID that you received from Experian.
  3. Enter the Consumer Key that you received from Experian's API ACCESS screen.
  4. Enter the Consumer Secret that you received from Experian's API ACCESS screen.
  5. Provide additional notes about your implementation.
  6. Click Test Connection to verify the keys.

Action Settings: Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up actions and trigger them.

This section describes how to set up parameters and options for each action.

Action: Insert Data to Table

Parameters

  1. Table (REQUIRED): Specify the desired table to update.
  2. Table Entry Data (REQUIRED): Match values to columns in the table.
  3. Upward Relations (OPTIONAL): Link this table entry to other tables.
  4. Date Formats (OPTIONAL): Format incoming data using a specific format.
  5. Import Options (OPTIONAL): Specify additional options for data inserts.

Options: Upward Relations

Upward relations allow for linking table data together. For example, there are 2 tables, order_item and order:

order_item order
item_id id
quantity date
order  

order_item's item_id and quantity will be mapped in the Table Entry Data section. order_item's order and order's item_id,quantity will need to be mapped in the Upward Relations Section. The resulting mapping will look like:

Attribute Path
event_order_id order/id
event_timestamp order/date

Where "eventorder_id" and "event_timestamp" are single entry event/audience array attributes, allowing for several _Upward Relations to be specified.

Options: Date Formats

Specify date formats per table field (also applies to Upward Relation paths). The format must follow Java's template standard.

Some popular formats include:

Format Result
MM/DD/YYYY 05/25/1977
MM/dd/yyyy hh:mm a 05/25/1977 07:15 PM
yyyy/MM/dd HH:mm:ss 1977/05/25 19:15:37
yyyy/MM/dd HH:mm:ss x 1977/05/25 19:15:37 +0000

Custom/incoming dates are assumed to be milliseconds since January 1st, 1970 UTC (epoch).

Options: Import Options

Option Values Description
Do Not Update Existing  true or false  true to insert a new record instead of updating a matching record

A CustomValue can be specified for import options not listed above.