About the Marketing Person Integration Object
Most deployments of the Siebel Marketing application use the Marketing Contact integration object for loading campaign data. The Marketing Contact integration object is most commonly used because it supports inserting new contact and account names into the transaction database. In contrast, the Marketing Person integration object only supports inserting new records into the Campaign History table for contacts or prospects that already exist in the transaction database.
When all the customer data resides in the Siebel transaction database, the load process can avoid inserting new customers and improve the load time. The Marketing Person integration object supports this simple lookup load process.
Only use the Marketing Person integration object when all target contacts, accounts and prospects in the campaign already exist in the transaction database. The only required mapping is between the Row ID from the Contact and Prospect tables in the Siebel transactional database and the external data source, typically the Siebel Data Warehouse. For a list of fields for the Marketing Person integration object, see Field Names for Marketing Integration Components.
The following figure shows the integration components for the Marketing Person integration object. Required fields apply when a new campaign contact record is inserted into the Siebel transactional database.
The following table describes the integration component for the Marketing Person integration object.
| Component | Comment |
|---|---|
Campaign Contact |
Maps the required campaign history columns and keys that store the unique IDs from the data warehouse for the party being loaded. User Key: Campaign Id, Load Number, Token Number, and one or more of the following:
|