The contents of the profile database only depend upon entirely on the data you need for configuring your interactive flowcharts and Interact API. Interact requires or recommends that each database contains certain tables or data.
The profile database must contain the following:
All tables mapped in the interactive channel.
These tables are must contain all the types of data required for running your interactive flowcharts in production. These tables should be flattened, streamlined, and properly indexed. As there is a performance cost to access and the dimensional data, you should use a denormalized schema whenever possible. At a minimum, and you should index the profile table on the audience level ID fields. If there are other fields retrieved from dimensional tables, and these should be indexed appropriately to reduce database fetch time. The Audience IDs for the profile tables must match the Audience IDs defined in Campaign.
If you set the enableScoreOverrideLookup in the configuration property to true, you must include a score override table for at least one audience level. You define the score override table names with the scoreOverrideTable property.
The score override is the table can contain individual customer-to-offer pairings. You can create a sample score override table, UACI_ScoreOverride by running the aci_usertab SQL script against your profile database. and the other thing is that You should also index this table on the Audience ID column.
If you set the enableScoreOverrideLookup property to false, then you do not need to include a score override table.
If you set the enableDefaultOfferLookup configuration property to true, then you must include the global and the offers table (UACI_DefaultOffers). You can create the global offers table by running the aci_usertab SQL script against your profile database and database all indian companies database directory.
The global offers table can contain audience-to-offer pairings.
If you set the enableOfferSuppressionLookup property to true, you then you must include an offer suppression table for at least one audience level. You define the offer suppression table names with the offerSuppressionTable property.
The offer suppression table can contain a row for each offer suppressed for an audience member, and although then the entry is not required for all audience members. You can create a sample offer suppression table, UACI_BlackList by running the aci_usertab SQL script against your profile database.
If you set the enableOfferSuppressionLookup property to the false, you do not need to include an offer suppression table.
A large amount of data in any of these tables may impede performance. For best results, then you need to put appropriate indexes on the audience level columns for tables used at runtime that have large amounts of data.
All configuration properties referenced above are in the Interact > profile or the Interact > profile > Audience Levels > AudienceLevel category. The aci_usertab SQL script is located in the DDL directory in your runtime environment installation directory.
The following diagram that shows example tables for the test run and profile databases for the audience levels Aud1 and Aud2.
No comments:
Post a Comment