Click tracking

The DOM path feature is available when setting up click tracking. When you click an element on the page, the VEC options menu displays. In addition, the corresponding DOM path displays at the bottom of the page. You can use the DOM path to quickly see information about the selected element (type, ID, and class) and move up or down the DOM path to select the desired element.

Like when creating experiences in Step 1 in the activity-creation workflow, the DOM path selector at the bottom of the page lets you choose an element. On selecting an element from the DOM path, the corresponding element in the VEC displays as “Selected.” To unselect a selected element, you can click the element again in the DOM path selector or click the “Selected” box within the VEC.

For more information, see Navigate elements using the DOM path in Visual Experience Composer Options.

You can browse to a different page to track clicks on a page where you might not be changing content. This different page must be included in the activity using the multipage feature and at.js must be implemented on it.

If you select more than one element, if an entrant clicks on any one of the chosen elements, the click is counted. To count each item separately, set up individual success metrics for each element. To count one item by clicking several elements on a page, edit the CSS Element Selector to match multiple elements.

Make sure you select the level of element you want to track. For example, when specifying a button, make sure you select the link and not the button text.

Click events are sent to Target on the same page as the click.

If the click-tracking metric is the Goal metric of an Analytics for Target (A4T) activity, the visitor must click this element within 60 seconds of the page loading for the metric to track.

Click tracking does not work on elements that include escaped characters in their selectors, including the following:

If you use at.js click tracking and you also use Analytics AppMeasurement, at.js click tracking cancels all other click event handlers. As a result, the AppMeasurement click handler never executes.

at.js has special handling for click tracking when the underlying element is an A (link) tag or FORM tag.

The following steps are executed by at.js when the click tracking event is attached to an A (link) tag or a FORM tag:

1. Invoke event.preventDefault().

2. Fire Target request.

3. On Target request success or error callback, execute default behavior:

   • A (link) tag: The default behavior is to navigate to the URL defined by HREF attribute.
   • FORM tag: The default behavior is to submit the form.

This default behavior might interfere with Analytics click tracking. If you are using Analytics, you should rely on Analytics for click tracking rather than Target.

Click tracking is not recorded on pages where the page and activity URL belong to different properties. Enterprise user permissions is a Target Premium feature. For more information, see Enterprise user permissions.

Click-tracking metrics are not linked to any specific experience in an activity.

Use audiences if it is necessary to restrict the scope of the click-tracking metrics.

Multiple activities can define a click-track metric for the same selector. If so, when a visitor qualifies for one of those activities and clicks that selector, the click-track metric increases for all associated activities that the visitor qualified for.