Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > Campaign Load Mapping and Analytic Adapters > About Analytic Adapters >

Setting Up Analytic Adapters

---

Mappings and other setup procedures that need to be performed on Analytic Adapter tables depend on the type of information imported into Siebel Marketing and other end-user requirements.

Some general recommendations for mapping tables, setting up joins, and building attribute families are provided in the following sections. For details, see External Data Mapping.

Mapping Tables for Analytic Adapters

Map the following tables from Siebel Marketing Repository server:

Analytic Adapter data table (X_DD_TRGTGRPMBR). Set the table Type as Analytic Adapter.
Analytic Adapter lookup table (S_DD_TRGT_GRP). Set the table Type as Regular.

Mapping Analytic Adapter Tables to a Customer Hierarchy

The mapping depends on the level at which the data is exported from the analytic tool and the Siebel Marketing customer hierarchy. Table 15 shows some sample mappings.

Table 15.  Sample Mapping to Customer Hierarchy

Data Source	Exported Data	Customer Hierarchy	Mappings	Comment
Siebel Data Warehouse	Account ID, Contact ID	Account to Contact	X_DD_TRGTGRPMBR.KEY_01 to Account Level and X_DD_TRGTGRPMBR.KEY_02 to Contact level
Siebel Data Warehouse	Contact ID	Account to Contact		No mappings needed
External Data Source	Customer ID, Model score	Customer	X_DD_TRGTGRPMBR.KEY_01 to Targeting level
External Data Source	Individual ID	Household to Individual		No mappings needed

Creating Joins for Analytic Adapters

In the Joins view, you must join the customer table in the data source to the Analytic Adapter data table. The parent table and the joining fields depend on the level at which the data is exported from the analytical tool. In the join examples shown in Table 16, the parent table may differ depending on your implementation requirements.

Join X_DD_TRGTGRPMBR to S_DD_TRGT_GRP using the S_DD_TRGT_GRP_ID and ROW_ID fields respectively. Set this join for Cache.
Set up a start point join to both the Analytic Adapter data table and the lookup table.

The sample joins may need to be set as Outer joins, if records that are not part of the target group are needed for a snapshot build (for example, if you are combining members of a target group with other contacts in your database). In addition, the joins should be designed for Cache (Cache check box) if X_DD_TRGTGRPMBR is not mapped in the Customer Hierarchies view.

Table 16.  Sample Joins

Data Source	Exported Data	Customer Hierarchy	Parent Table	Join
Siebel Data Warehouse	Account ID, Contact ID	Account to Contact	W_PERSON_F	W_PERSON_F.ACCNT_WID to X_DD_TRGTGRPMBR.KEY_01 and W_PERSON_F.CONTACT_WID to X_DD_TRGTGRPMBR.KEY_02
Siebel Data Warehouse	Contact ID	Account to Contact	W_PERSON_F.CONTACT_WID	W_PERSON_F.CONTACT_WID to X_DD_TRGTGRPMBR.KEY_01
External Data Source	Customer ID, Model score	Customer		CUSTOMER.ID to X_DD_TRGTGRPMBR.KEY_01
External Data Source	Individual ID	Household to Individual		INDIVIDUAL.ID to X_DD_TRGTGRPMBR.KEY_01

Using Fields for Data Retrieval

Enable the target group name in the Analytic Adapter Lookup table for Data Retrieval (S_DD_TRGT_GRP.NAME). Data is not automatically retrieved for this field after a target group load.

Creating Attribute Families for Analytic Adapters

You must create an attribute family based on the Analytic Adapter tables, using the source of the Target Group and the Target Group Name as attributes. The base field is X_DD_TRGTGRPMBR.DD_TRGT_GRP_ID. The attributes are detailed in Table 17.

Table 17.  Attributes for Attribute Family

Attribute Name	Code Table	Code Field	Label Table	Label Field
Target Groups	S_DD_TRGT_GRP	ROWID	S_DD_TRGT_GRP	NAME
Sources	S_DD_TRGT_GRP	SRC_TOOL_NAME	S_DD_TRGT_GRP	SRC_TOOL_NAME

When you have finished defining the attribute family, define an attribute hierarchy using Sources to Target Groups as attributes in the hierarchy.

Bookshelf Home | Contents | Index | Search | PDF