Bookshelf Home | Contents | Index | PDF |
Siebel Marketing Installation and Administration Guide > Designing Marketing Campaign Load Formats > About Marketing Integration Objects > About the Marketing Contact Integration ObjectThe Marketing Contact integration object provides field mappings to typical contact- and account-related information from the external data sources. The predefined integration object, Marketing Contact, defines the information that is exchanged between the external data source and Siebel Marketing, using EAI technology. For more information about EAI, read Overview: Siebel Business Application Integration Volume I. For a list of fields for the Marketing Contact integration object, read Field Names for Marketing Integration Components. Figure 2 shows the integration components for the Marketing Contact integration object. Required fields apply when a new contact is inserted into the Siebel transactional database. During campaign load, integration component User Keys determine if a record already exists in the component (for the given values) and if the record is unique. Required fields cannot be a null value for the new record. Table 18 describes the Marketing Contact integration components. Mapping Rules for the Marketing Contact Integration ComponentsUsing contact information for campaign load requires the following integration components:
Use the following rules when mapping components:
Sample Mappings for Contact Key ComponentsThe combination of keys that are mapped in the campaign load report depend upon the target levels that you use. Table 19 describes examples of Key mappings for sample target levels. Changes for Segmentation Bridge UsersIf you use the Marketing Segmentation Bridge to execute campaigns in Siebel Marketing 6.3, 7.0, or 7.5, the campaign load formats have a some modifications from the 7.7 format. Segmentation Bridge User Key columnsTo populate campaigns in Siebel 6.3, 7.0, and 7.5, modify the required user key columns to match the user keys in the pre-7.7 version of Siebel Marketing. Table 20 shows the integration components and required columns for Siebel Marketing versions 6.3, 7.0, and 7.5. When you move your environment from a segmentation bridge environment to a nonbridged environment (Siebel Enterprise and Marketing Server on the same version), make the following changes to convert your campaign load format:
End of Line CharacterTo populate campaigns in Siebel 6.3, 7.0, and 7.5, the end of each line of the campaign load file (loaded by EAI) must have a tilde character (~) concatenated to the end of the last column. In a nonbridged environment, the tilde character is not required. Modify the column formula for the last (rightmost) column to remove the concatenation. Campaign Load File Header ModificationsTo populate campaigns in Siebel 6.3, 7.0, and 7.5, the campaign load file (the EAI file) required a header with the following four lines: # Marketing Contact A nonbridged environment requires only two lines. For nonbridged environments, remove the time stamp and record count lines from the bridge version as follows: |
Siebel Marketing Installation and Administration Guide | Copyright © 2006, Oracle. All rights reserved. | |