Link Tracking data

Important: This topic contains legacy content. See Adobe Analytics integration for updated information.

All link tracking events are sent with the 'o' type of Other/General.

All event data is sent in an object called contextData, which can be used to map into an Adobe eVar or as a condition for the new processing rule to run.

See the following sections for additional details:

contextData
eventNames

contextData

The following table contains contextData variables that can be used as eVars in the integration.

Important: The only mandatory variable for the integration is eventName. The others are optional and can be used to enrich data.

Table 1. contextData variables
Variable name	Description
eventname	Name of the Digital event that occurred.
formid	Digital survey identifier.
accountid	Digital account identifier.
websiteid	Digital property identifier.
feedbackuuid	Unique identifier of the specific feedback that was sent to Digital. The feedbackuuid will be generated only when the survey is actually opened. For example, events button_clicked or invite_accepted will generate no uuid.
pagenumber	(For form_page_displayed event); indicates which page of the survey was displayed to the customer.
LTR	NPS field and its value.
osat_11	OSAT field and its value.

eventNames

The following tables lists Digital events that are supported and reported to Adobe Analytics. These events come into your Adobe account only when the eventName is set up as a contextData variable first in the processing rule.

Table 2. eventName variables
Variable	Description
form_displayed	Digital survey was displayed to the customer.
invite_triggered	Digital invite (intercept) was triggered according to a se of trigger rules
invite_accepted	Customer that has seen an invitation (intercept) has agreed to provide feedback.
invite_rejected	Customer that has seen an invitation (intercept) has rejected the invitation; will not be presented with a survey.
button_clicked	Customer has clicked an always-on feedback button.
feedback_submitted	Customer has submitted a survey.
form_close_no_submit	Customer has closed the survey without submitting.
form_page_displayed	Customer has navigated between pages in a multi-page survey.
screen_capture_init	Customer is presented with the screen capture widget. This is only relevant for surveys that include the screen-capture capability.
capture_image_click	Customer captured an image to submit with the feedback. This is only relevant for surveys that include the screen-capture capability.
cancel_capture_click	Customer has canceled the screen capture. This is only relevant for surveys that include the screen-capture capability.
form_next_page	Customer has clicked the Next button on the survey.
form_back_page	Customer has clicked the Back button on the survey.
thankyou_displayed	The Thank You page was displayed to the customer. This is the last page of the survey and displayed after the customer clicks the Submit Feedback button.
thankyou_close	Customer closed the Thank You page.
showform_called	ShowForm API called.
form_close_submitted	Customer closed the survey. During the survey display, the customer submitted feedback.