Bookshelf v7.5.2: Mapping Rules for Integration Components (Marketing Contact)

Siebel Marketing Guide > Campaign Load Mapping and Analytic Adapters > About Marketing Integration Objects and Components >

Mapping Rules for Integration Components (Marketing Contact)

Siebel Marketing integration requires at least three integration components: Contact, Contact Key, and Campaign Contact. Campaign Contact is automatically generated by the Marketing Server component.

Use the following rules when mapping components:

A parent integration component must be mapped before mapping a child component. For example, the Account Address component cannot be mapped unless Account is mapped.

User Key fields must be mapped for each integration component if one or more fields for the component is mapped. There are two exceptions:

Siebel Marketing Server will generate user key fields Master Key and Family Level ID for the Contact Key integration component. However, Key1 is a required field and must be mapped.

If Contact Organization is not mapped for a campaign contact, Siebel Marketing Server will default the Contact Organization to the organization set for the Enterprise server user name (usually SADMIN).

Required fields must be mapped for each integration component if one or more fields for the component are mapped.

Map Contact Keys (Key 1, Key 2, and so on) for the targeting level at which the Campaign Load Mapping is defined, and the levels above it.

For example, a customer hierarchy might have three targeting levels—Household (primary targeting level), Individual, and Personal Accounts. You might choose the third targeting level, Personal Accounts, as the level for the campaign load mapping. If you map the keys for the Personal Accounts level, you must also map the keys for the Individual level and Household level.

When the targeting level that equates to a Siebel Contact is below the level at which the Campaign Load Mapping is defined, then the level identifying a Siebel Contact should also be mapped. Using the previous example, if you select Household as the level for the Campaign Load Mapping, you must map the Individual level as well. Typically the targeting level that maps to Contact Integration component fields such as first name and last name is the equivalent of a Siebel Contact.

Siebel Marketing defaults the Account Organization for the campaign contact to Default Organization if the account organization field is not mapped.

Fields that are mapped to keys should not contain the tilde (~) character. For example, if Customer_ID is mapped to Key1, Customer_ID data should not contain the tilde character.