Experian Marketing Suite Connector Setup Guide | Server-Side Connectors

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.

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

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

To configure your vendor, follow these steps:

In the Configure tab, provide a title for the connector instance.
(Optional) Enter the Client ID that you received from Experian.
Enter the Consumer Key that you received from Experian’s API ACCESS screen.
Enter the Consumer Secret that you received from Experian’s API ACCESS screen.
Provide additional notes about your implementation.
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

Parameter	Description
Table	Required. Specify the desired table to update.
Table Entry Data	Required. Match values to columns in the table.
Upward Relations	Link this table entry to other tables.
Date Formats	Format incoming data using a specific format.
Import Options	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.