/
Email and Social Input

Email and Social Input

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. The key difference between this and the Realtime Input template is that in this Template the data is passed via the URL querystring instead of the body of a HTTP POST. This allows it to be embedded into links contained in an email, social media post or web page without any requirement for JavaScript.

 

Input data

Field

Description

Example

Field

Description

Example

ClientIP

IP address of the individual opening or clicking on the email. This is automatically populated by Alterian CX so does not need to be manually added.

109.151.137.25

recipient

Recipient email address, this is normally easily provided by using the personalisation options your ESP provides.

someone@isp.com

redirect

Where the link should redirect to and defines whether we track as a open or click - Should be URL encoded.

https://www.alterian.com/real-time-customer-experience-platform/forrester-wave-leader/

campaign

Campaign name

Newsletter Jan 2021

link

Name of the link which maps to position in the tracking

forrestor_wave_leader

channel

Channel utilising this Rule. This will default to Email if this is not provided in the input data or changed in the parameter

email

Configuration

Field

Description

Example

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 pixel hosted by Alterian CX will be used.

https://dde.alterian.net/tracking-pixel.gif

defaultChannel

This template has been created to allow links of all types to be tracked with Alterian CX. Email is the default value added as this is the most commonly used. This can also be used to track other social media. The channel can be added into the query or the parameter can be changed to change the channel using the Rule.

email

Output Data

Field

Description

Example

Field

Description

Example

emailAddress

Recipient is changed to emailAddress so it maps easily with the Get CXID tile

someone@isp.com

AlterianQueue_position

Link is changed to AlterianQueue_position so it maps easily with the Get CXID

forrestor_wave_leader

AlterianQueue_location

Taken from Campaign concatenated with emailEventType

Newsletter Jan 2021-click

ClientIP

IP address of the recipient, automatically created

109.151.137.25

campaign

Campaign name provided by the Input request

Newsletter Jan 2021

emailEventType

Either Click or Open when concatenated with campaign forms the AlterianQueue_location

click

message

Automatically added

 

channel

channel utilising this Rule. This will default to Email if this is not provided in the input data or changed in the parameter

email

redirect

Where a tracking link is required this is the URL of the page the link should redirect to.

https://www.alterian.com/real-time-customer-experience-platform/forrester-wave-leader/

loopcount

Automatically added

 

Rule Group

Automatically added

 

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

 

Related content