The SQL to match by treatment code must return all the columns in the XSessResponse table for this audience level plus a column called OfferIDMatch. The value in the
OfferIDMatch column must be the
offerId that goes with the treatment code in the XSessResponse record.
The following is a sample of the default generated SQL command that match treatment codes. Interact generates the SQL to use the correct table names for the audience level. This SQL is used if the
Interact > services > crossSessionResponse > OverridePerAudience > AudienceLevel > TrackingCodes > byTreatmentCode > SQL property is set to
Use System Generated SQL.
The values UACI_XsessResponse,
UA_DtlContactHist,
CustomerID, and
UA_ContactHistory are defined by your settings in
Interact. For example,
UACI_XsessResponse is defined by the
Interact > profile > Audience Levels > [AudienceLevelName] > crossSessionResponseTable configuration property.
If you have customized your contact and response history tables, you may need to revise this SQL to work with your tables. You define SQL overrides in the Interact > services > crossSessionResponse > OverridePerAudience > (AudienceLevel) > TrackingCodes > byTreatmentCode > OverrideSQL property. If you provide some override SQL, you must also change the
SQL property to
Override SQL.
The SQL to match by offer code must return all the columns in the XSessResponse table for this audience level plus a column called TreatmentCodeMatch. The value in the
TreatmentCodeMatch column is the Treatment Code that goes with the Offer ID (and Offer Code) in the XSessResponse record.
The following is a sample of the default generated SQL command that match offer codes. Interact generates the SQL to use the correct table names for the audience level. This SQL is used if the
Interact > services > crossSessionResponse > OverridePerAudience > AudienceLevel > TrackingCodes > byOfferCode > SQL property is set to
Use System Generated SQL.
The values UACI_XsessResponse,
UA_DtlContactHist,
CustomerID, and
UA_ContactHistory are defined by your settings in
Interact. For example,
UACI_XsessResponse is defined by the
Interact > profile > Audience Levels > [AudienceLevelName] > crossSessionResponseTable configuration property.
If you have customized your contact and response history tables, you may need to revise this SQL to work with your tables. You define SQL overrides in the Interact > services > crossSessionResponse > OverridePerAudience > (AudienceLevel) > TrackingCodes > byOfferCode > OverrideSQL property. If you provide some override SQL, you must also change the
SQL property to
Override SQL.
You must define this alternate code in the UACI_TrackingType table in the
Interact runtime environment tables.
You must provide SQL or a stored procedure in the Interact > services > crossSessionResponse > OverridePerAudience > (AudienceLevel) > TrackingCodes > byAlternateCode > OverrideSQL property which returns all the columns in the XSessResponse table for this audience level plus the columns
TreatmentCodeMatch and
OfferIDMatch. You may optionally return the
offerCode in place of
OfferIDMatch (in the form of
offerCode1,
offerCode2, …
offerCodeN for N part offer codes). The values in the
TreatmentCodeMatch column and
OfferIDMatch column (or offer code columns) must correspond to the
TrackingCode in the XSessResponse record.
Where <x> is the tracking code defined in the
UACI_TrackingType table.