About the translation table
A translation table is typically configured by IT or other technical personnel when the Digital Analytics-Campaign integration is initially configured.
The translation table tells Campaign which Digital Analytics IDs correspond to which Campaign Audience IDs. A translation table is required when running a flowchart that includes Digital Analytics segments as input. Without the table, Campaign does not know how to translate IDs from one product to the other.
Illustration of a translation table and a temporary table
A translation table must adhere to the following guidelines:
*
The translation table must be configured on the user data source from which Campaign selections take place. This data source must allow table creation permission so Campaign can create a temporary table for the list of IDs that meet the segment definition.
*
A translation table consists of at least two columns, one for the Digital Analytics key and one or more for the corresponding Campaign Audience ID.
*
For this release, the Digital Analytics key must be the exact value: registrationid.
*
The data type of the registrationid in the translation table must be the same data type defined for the registrationID in Digital Analytics. For example, they must both be VARCHAR.
*
The Campaign Audience ID is defined by the customer when the integration is configured. For example, it might be CustomerID.
*
If your primary Campaign audience consists of multiple physical keys (compound keys), the translation table must contain the same number of columns for that audience. For example, if your primary audience consists of the keys CustomerID and AccountID, then the translation table must have three columns: 1) The Digital Analytics key 2) CustomerID 3) AccountID. This requirement pertains only if you are mapping for a compound audience.
*
For performance and storage reasons, the best practice is to use single-key audiences.
*
You must ensure that the translation table name and the Digital Analytics key (registrationid) defined in the table are specified in the Campaign configuration settings. The values used in the translation table must exactly match the values defined in the configuration settings. See Campaign | partitions | partition[n] | Coremetrics.
*
The method for populating a translation table depends on each customer's specific requirements and configuration. A common logic needs to be determined that allows for identifying which Digital Analytics registration ID matches which Campaign Audience ID. Your implementation partner can assist you in this process.
*
The translation table must be mapped in Campaign. See Mapping the translation table.
*
When a flowchart runs, Campaign detects if there is a mismatch between the number of Digital Analytics keys and Campaign Audience IDs in the mapped translation table. This situation can occur, for example, if the ETL routines are still running). In this case, Campaign writes a message to the flowchart log file asking you to verify that the mapped translation table contains updated records. To resolve this situation, (re)match the online and offline keys according to your corporate policy and repopulate the translation table with up-to-date data. The user must rerun the flowchart after the mapped translation table is updated.
Copyright IBM Corporation 2015. All Rights Reserved.