| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Marketing Guide > Campaign Load Mapping and Analytic Adapters > Creating Campaign Load Mappings >
Siebel Contact and Campaign History Tables
When you generate a contact list (Load Campaign), the Marketing Server modifies data in the Siebel database after Contact and Contact Key integration components are mapped and campaign load mapping data is modified.
- Contacts table (S_CONTACT). The Contacts table stores contact-level information.
- Campaign History table (S_CAMP_CON). The Campaign History table contains the history of contacts that qualify for campaigns, as well as the Campaigns ID, Segment ID, Wave ID, and so on.
- External Keys table (S_DD_USER_KEY). The External Keys table contains customer hierarchy keys data for a contact in addition to target-level ID. Database keys (such as Account Number and Customer ID) that are mapped to the Contact Key integration component fields for each targeting level are recorded in this table for every contact targeted by a marketing program.
If you include optional integration component fields such as Account or Contact Address in the campaign load mapping, other Siebel tables are updated with data according to the integration fields that are mapped.
For every record that qualifies for a campaign the Campaign Load process first determines if the contact record exists based on the Contact component user key. The following actions are performed, as shown in Table 6:
NOTE: If you use the Marketing Contact integration object, the lookup uses the User Key fields for Contacts and Accounts (see Figure 2). If you use the Marketing Person integration object, the lookup only requires the Contact ID or Prospect ID to confirm that the person is present in the transaction database.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Marketing Guide, Version 7.5, Rev. A Published: 18 April 2003 |