Bookshelf Home | Contents | Index | Search | PDF

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

Recommended Campaign Load Mappings-Examples

---

Settings for campaign load mappings depend on the following:

The Data source. The data source includes Siebel Data Warehouse, Siebel database, or a non-Siebel data source.
The Data elements required to be imported into Siebel. These elements include Contact fields, Account fields, Contact address, and so on.
Contact Qualification. Determine if new contacts or existing contacts qualify for a campaign.
Presence of contacts and prospects in the Siebel database. Determine if all contacts and prospects are already present in the contact and prospect tables in the Siebel database.

The examples in this section describe a few recommended mappings. The examples do not include all the required fields but do provide the recommended field mappings for certain integration component fields.

The following topics contain examples of recommended campaign load mappings:

Mapping to the Siebel Data Warehouse
Mapping to the Siebel Database
Mapping to a Non-Siebel Database

Mapping to the Siebel Data Warehouse

Table 9 contains the recommended mappings when no contacts have been deleted and no new contacts have been added to the Siebel database during Campaign Load. Use the recommended mappings in Table 10 when contacts have been deleted. Other fields from available components may need to be mapped based on program or campaign requirements.

Table 9 shows the recommended mappings when the following conditions are met:

Data source. Siebel Data Warehouse.
New contacts. No new contacts added to Siebel database during Campaign Load and no contacts deleted.
Prospects. Prospects are not included in the campaign.
Customer hierarchy. Accounts to Contacts.

Table 9.  Mapping to the Siebel Data Warehouse

Integration Component	Integration Component Field	List Measure Field	Comment
Contact	Person UID	W_PERSON_D.PRSP_CON_UID
Contact	Contact Organization	W_PERSON_D.CON_BU_NAME
Contact Key	Key 1	W_PERSON_F.ACCNT_WID, W_ORG_D.ROW_ID	The field can vary depending on customer hierarchy mappings.
Contact Key	Key 2	W_PERSON_F.CONTACT_WID, W_CONTACT_DM.ROW_WID	The field can vary depending on customer hierarchy mappings.

Table 10 shows the recommended mappings when the following conditions are met:

Data source. Siebel Data Warehouse.
New contacts. Contacts have been deleted.
Prospects. Prospects are not included in the campaign.
Customer hierarchy. Accounts to Contacts.

Siebel Data Warehouse may not be synchronized with the Siebel database when contacts have been deleted and the deleted contacts should not be included in campaigns. Use the recommended mappings in Table 10 when contacts have been deleted.

Table 10.  Mapping to the Siebel Data Warehouse When Contacts Deleted

Integration Component	Integration Component Field	List Measure Field	Comment
Contact	Person UID	S_CONTACT.PERSON_UID	Equal join from W_PERSON_D.PRSP_CON_UID to S_CONTACT.PERSON_UID.
Contact	Contact Organization	S_BU.NAME	Equal join S_CONTACT.BU_ID to S_BU.PAR.ROW_ID.
Contact Key	Key 1	W_PERSON_F.ACCNT_WID, W_ORG_D.ROW_ID	The field can vary depending on customer hierarchy mappings.
Contact Key	Key 2	W_PERSON_F.CONTACT_WID, W_CONTACT_DM.ROW_WID	The field can vary depending on customer hierarchy mappings.

Mapping to the Siebel Database

Use the recommended mappings in Table 11 when prospects are not included in the campaign. Use the recommended mappings in Table 12 when prospects might be included. Other fields from available components may need to be mapped based on program or campaign requirements.

Table 11 shows recommended mappings when the following conditions are met:

Data Source. Siebel database.
Prospects. Prospects are not included in the campaign.
Customer hierarchy. Accounts to Contacts.

Table 11.  Mapping to the Siebel Database-Prospects Not Included

Integration Component	Integration Component Field	List Measure Field	Comment
Contact	Person UID	S_CONTACT.PERSON_UID	Equal join from W_PERSON_D.PRSP_CON_UID to S_CONTACT.PERSON_UID.
Contact	Contact Organization	S_BU.NAME	Equal join S_CONTACT.BU_ID to S_BU.PAR_ROW_ID.
Contact Key	Key 1	S_ORG_EXT.ROW_ID	The field can vary depending on customer hierarchy mappings.
Contact Key	Key 2	S_CONTACT.ROW_ID	The field can vary depending on customer hierarchy mappings.

Use the recommended mappings in Table 12 when the following conditions are met:

Data Source. Siebel database.
Prospects. Prospects might be included in the campaign.
New contacts. No new contacts or prospects are introduced into the Siebel database during Campaign Load.
Customer hierarchy. Person (one targeting level).

Table 12.  Mapping to the Siebel Database-Prospects Might Be Included

Integration Component	Integration Component Field	List Measure
Contact Key	Key 1	Integration ID
Contact Key	Contact Id	Contact ID (Pseudo-field)
Contact Key	Prospect Id	Prospect ID (Pseudo-field)

Mapping to a Non-Siebel Database

Use the recommended mappings shown in Table 13 when new contacts are added to the Siebel database during Campaign Load. Use the recommended mappings shown in Table 14 when new contacts are added to the Siebel database during Campaign Load. Other fields from available components may need to be mapped based on program or campaign requirements.

Table 13 contains the recommended minimum mapping requirement when the following conditions are met:

Data source. Non-Siebel database.
New contacts. New contacts are introduced into the Siebel database during Campaign Load. External contacts have a pre-assigned Organization.
Customer hierarchy. Household to Individual.

Table 13.  Mapping to a Non-Siebel Database-New Contacts in Campaign Load

Integration Component	Integration Component Field	Required	List Measure	Comment
Contact	Person UID	Yes	Individual ID	ID of the customer hierarchy mapping to Siebel Contact.
Contact	Contact Organization	No	Organization field	The organization names in the source database must match exactly with Siebel organization setup (S_BU).
Contact	First Name	Yes	Individual's First Name
Contact	Last Name	Yes	Individual's Last Name
Contact Key	Key 1	Yes	Household ID
Contact Key	Key 2	No	Individual ID

Table 14 contains the recommended minimum mapping requirement when the following conditions are met:

Data source. Non-Siebel database.
New contacts. During campaign load, no new contacts are introduced into the Siebel database. External contacts do not have a preassigned organization.
Customer hierarchy. Household to Individual.
Targeting level equivalent to Siebel Contact. Individual.

Table 14.  Mapping to a Non-Siebel Database-No New Contacts in Campaign Load

Integration Component	Integration Component Field	Required	List Measure	Comment
Contact	Person UID	Yes	Individual ID	ID of the customer hierarchy mapping to Siebel Contact.
Contact Key	Key 1	Yes	Household ID
Contact Key	Key 2	No	Individual ID

Bookshelf Home | Contents | Index | Search | PDF