Use this template to track email opens and clicks using Alterian CX. The Input identifies whether the request is an “Open” where it provides back the tracking beacon or a “Link” being tracked where it allows the user to control the redirect being used.
Input data
Field | Description | Example |
|---|---|---|
ClientIP | IP address of the individual opening or clicking on the email | |
recipient | Recipient email address, this is normally easily provided by using the personalisation options your ESP provides. | |
redirect | Where the link should redirect to and defines whether we track as a open or click - Should be URL encoded. | |
campaign | Campaign name | |
link | Name of the link which maps to position in the tracking |
Configuration
Field | Description | Example |
|---|---|---|
tracking pixel url | Set by the Parameter “tracking Pixel url” this allows the user to provide the loction of the tracking pixel ( beacon). By default the user can use a pixel hosted by Alterian CX. |
Output Data
Field | Description | Example |
|---|---|---|
AlterianCX_channelagentid1 | Recipient is changed to AlterianCX_channelagentid1 so it maps easily with the Get CXID | |
AlterianQueue_position | Link is changed to AlterianQueue_position so it maps easily with the Get CXID | |
AlterianQueue_location | Taken from Campaign concatenated with emailEventType | |
ClientIP | IP address of the recipient, automatically created | |
campaign | Campaign name provided by the Input request | |
emailEventType | Either Click or Open when concatenated with campaign forms the AlterianQueue_location | |
message | Automatically added | |
redirect | Where a tracking link is required this is the URL of the page the link should redirect to. | |
loopcount | Automatically added | |
Rule Group | Automatically mapped | |
Rule Type | Automatically added by Alterian queues | |
Sequence Number | Automatically added | |
Time Stamp | Automatically added | |
Trace | Automatically added | |
Is Control | Standard Is Control flag will be mapped by the Get CXID |