About Siebel Contact and Campaign History Tables

When you load a campaign, the Campaign Load workflow process modifies data in the Siebel database after the Contact a integration component is mapped and the 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 who qualify for campaigns, as well as the Campaigns ID, Segment ID, Wave Number, and so on.

If you include optional integration component fields such as Account or Contact Address in the campaign load format, other 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 uses the Contact component user key to determine if the contact record exists. The following table contains the table update rules.

Siebel Contact Record	S_CONTACT	S_CAMP_CON
Exists	Update existing record	Insert new record
Does not exist	Insert new record	Insert new record

Note: If you use the Marketing Contact integration object, the lookup uses the User Key fields for Contacts and Accounts. The illustration in About the Marketing Contact Integration Object shows the integration components for the Marketing Contact integration object. If you use the Marketing Person integration object, the lookup only requires the Campaign Id, Load Number, Token Number, Contact Id, or Prospect Id to confirm that the person is present in the transaction database.