Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > Campaign Load Mapping and Analytic Adapters > Creating Campaign Load Mappings >

Mapping Rules for Integration Components (Marketing Person)

---

When creating a campaign load mapping using the Marketing Person integration object, use the following guidelines:

Only the Contact Key integration component is required to be mapped. The only required field is Key 1.
The Contact ID and Prospect ID values imported from the external data source must match the Row IDs for the Contact or Prospect in the Siebel contact or prospect tables.
A single campaign can be based only on a single contact source table (each campaign can only use one campaign load mapping).

In a single campaign load record, you can map an integration component's integration component field to only one measure. For example, in a campaign load record for the Contact integration component, if you map the First Name integration component field to a measure called HH First Name, you cannot create another mapping record in the same campaign load record for the First Name integration component field to a different measure.

If all incoming target names are contacts, then you do not need to map Prospect ID. Alternatively, you might use the Marketing Contact integration object. If all incoming target names are prospects, then you do not need to use Contact ID. If the target list includes both contacts and prospects, then both fields are required.
Mappings for the Campaign Contact integration component are required only if Allow Repeated Contacts is selected for the campaign load mapping. This is because a contact might appear in the campaign for more than one account.

To create a campaign load mapping using the Marketing Person integration object

From the application-level menu, choose View > Site Map > Marketing Administration > External Data Mapping.
Map the data source table that contains Contact ID and Prospect ID. For the Siebel Data Warehouse, this table is W_PERSON_D.
Click the Tables view tab and add two pseudo-fields to the table using the following information:

Reference Name	Expression
Contact_ID	Case when contact_type_i = `Contact' then integration_id else null end
Prospect_ID	Case when contact_type_i = `Prospect' then integration_id else null end

From the Show drop-down list, select Measures.
Click the List view tab and create list measures for the following:
Contact_ID.
Prospect_ID.
Create a list measure for Customer or Integration ID in the Data Warehouse (this value will map to Key 1).

In the Siebel Data Warehouse, this field is INTEGRATION_ID field in the W_PERSON_D table and should uniquely identify the contact or prospect in the external data source.

From the Show drop-down list, select External Data Mapping and click the Campaign Load Mapping view tab.
In the Campaign Load Mapping list, create a new record, selecting Marketing Person in the Integration Object field.
In the Mappings list, create a new record.
In the new record, select the Contact Key integration component and map the following fields:

Integration Component Field	Measure
Contact Id	Contact ID
Key 1	Integration ID
Prospect Id	Prospect ID

As an optional step, if you selected the Allow Repeated Contacts check box, create another record in the mappings list for the Campaign Contact integration component and map the Account ID field.
Create a new customer hierarchy with one targeting level, mapping the Integration ID field from the external table to the targeting level.

For instructions, see procedures in Creating Customer Hierarchies.

Campaign Load Mapping Mappings depend on the following:

The Data source. The data source includes Siebel eBusiness 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 following scenarios show some recommended mappings. The scenarios do not include all the required fields for each example, but provide the recommended field mappings for certain integration component fields.

Scenario 1

In this scenario, use the recommended mappings shown in Table 8.

Data source. Siebel eBusiness Data Warehouse.
New contacts. No new contacts introduced into Siebel database during Campaign Load.
Prospects. Prospects are not included in the campaign.
Customer hierarchy. Accounts to Contacts.

Table 8. Scenario 1 Recommended Mappings

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.

Scenario 2

In this scenario, use the recommended mappings shown in Table 9.

Data source. Siebel eBusiness Data Warehouse.
New contacts. No new contacts introduced into the Siebel database during Campaign Load.
Prospects. Prospects are not included in the campaign.
Customer hierarchy. Accounts to Contacts.
Deleted contacts. Siebel eBusiness Data Warehouse may not be synchronized with the Siebel database because contacts have been deleted, and the deleted contacts should not be included in campaigns.

Table 9. Scenario 2 Recommended Mappings

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.

Scenario 3

In this scenario, use the recommended mappings shown in Table 10.

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

Table 10. Scenario 3 Recommended Mappings

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.

Scenario 4

In this scenario, use the recommended mappings shown in Table 11. The table displays the recommended minimum mapping requirement. Other fields from available components may need to be mapped based on program or campaign requirements.

Data Source. Siebel database.
Prospects. Prospects may 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 11. Scenario 4 Recommended Mappings

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)

Scenario 5

In this scenario, use the recommended mappings shown in Table 12. The table displays the recommended minimum mapping requirement. Other fields from available components may need to be mapped based on program or campaign requirements.

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 12. Scenario 5 Recommended Mappings

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

Scenario 6

In this scenario, use the recommended mappings shown in Table 13. The table displays the recommended minimum mapping requirement. Other fields from available components may need to be mapped based on program or campaign requirements.

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 13. Scenario 6 Recommended Mappings

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