Understanding Response Tracking Codes
An RTC provides information about user interactions that result in conversions or responses from users. To understand what information the RTC data can provide, ensure that you are familiar with these basic concepts:
A conversion occurs when a user completes a goal. For example, if your goal is for users to subscribe to your newsletter, then the act of subscribing to your newsletter is a conversion. For more information about conversions, see Understanding Analytic Results.
Both a contact and a response represent an interaction with a user. Typically, a response happens as a result of a contact that is initiated by your organization. When you create a task, you can choose when contact and response events are created.
- You can enable a task to create a default contact event when the task’s impression event is triggered. For example, you can create an email task that generates a contact event when an email is sent.
- You can classify primary and secondary metrics as contact events or response events. For example, if the primary metric on a web task is a click-through event on a specific spot, you can specify that the click-through event be classified as a response. As a result, when a user clicks that spot, a response event is created.
An occurrence is a single execution of an item and is generated either on a recurring schedule or from a user manually running the item. Currently, only these items generate occurrences:
- bulk tasks (direct marketing, email, and mobile push)
- on-premises segment maps
The occurrences of an item are listed on the Orchestration
HistoryOccurrences tab of an item.