Siebel Marketing Installation and Administration Guide > Designing Marketing Campaign Load Formats > About Marketing Integration Objects >

About the Marketing Person Integration Object


Most deployments of the Siebel Marketing application use the Marketing Contact Integration Object for loading campaign data. Marketing Contact Integration Object is most commonly used because it supports inserting new contact and account names into the transaction database. When all the customer data resides in the Siebel transaction system, the load process can avoid inserting new customers and improve the load time. The Marketing Person integration object supports this simple lookup load process.

The Marketing Person integration object should be used only 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.

Figure 4 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.

Figure 4.  Marketing Person Integration Components

Table 20 describes the integration component for the Marketing Person integration object.

Table 20.  Marketing Person Integration Component Description
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:

  • Contact Id
  • Prospect Id

Mapping Rules for the Marketing Person Integration Components

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

  • 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.
  • 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.
Siebel Marketing Installation and Administration Guide