As you create your offers, remember that the Interact API can reference the following information from the offer:
As you map offers in Campaign to offers on your touchpoint, for example HTML code for a banner ad, keep in mind what information is available for naming conventions. For example, you may want to save all the banner ads in files named the same as the offer code for easy reference.
When creating a postEvent call that logs offer acceptance or rejection, you must include the offer treatment code. However, if you enable cross-session response tracking, you can match on the treatment code, offer code, or a custom code particular to your environment. For more details about cross-session response tracking, see the
Interact Administrator's Guide.
You can use nameValuePair class of the
Interact API to define or retrieve data from custom offer attributes.
You must enable the IP ID and IPName offer attributes for all offers used by Interact. These attributes must exist, and are automatically populated during runtime, overwriting any default IP ID or IPName attributes you defined. The IP ID is the internal ID and the IP Name the name for the interaction point associated with the offer. This data is required for reporting. If you do not enable
Allow offers created from this template to be used in real-time interactions, you can still use the offers with treatment rules; however,
Interact is unable to include those offers in reports.
If your offer template contains the offer effective date and offer expiration date, you can define the dates relative to the Flowchart run date. For example, you can define the Offer Effective date to be the Flowchart run date. The offer can then expire some number of days after the effective date. In the case of Interactive flowcharts, the
Flowchart run date is the time at which the runtime environment recommends the offer to the touchpoint for presentation.
