Adobe Target lets you track clicks on any element as a success metric.
Tracking clicks is not supported on the global Target request when it is used as a location in a form-based activity.
When setting your goals on the Goals & Settings page for your activity , select the Conversion success metric.
For the action, select Clicked an element, then click Select elements.
Your page opens in the Visual Experience Composer (VEC).
Select any elements that you want to track.
See the Considerations section below for tips on selecting elements.
Click the check mark at the top of the screen to save your selections.
When an activity entrant clicks a selected element, that click is counted as a conversion.
For A/B Test, Experience Targeting (XT), Automated Personalization (AP), and Multivariate Test (MVT) activities, a Selected Elements panel lists all of the selected elements for click tracking on the right side.
There are a several actions that can be applied when you hover over an element in the Selected Elements panel. The following table describes each action that can be performed on an element:
|Information||Displays the element type and the full DOM path to the selector.|
|Edit||Lets you edit the CSS selector.|
|Delete||Deletes the element.|
If you already know the DOM path to the selector, you can add it manually by clicking the plus icon located at the top of the panel.
After selecting multiple elements for click tracking, you can click the Elements Selected link on the activity’s Goals & Settings step to see the full list of elements selected for click tracking. The list contains the full DOM path for the element to help you validate that the selected element is to be used for click tracking.
There are several things to consider when selecting elements:
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.
Just 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 again click the element 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 or mbox.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 on 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 A4T activity, the visitor must click this element within 60 seconds of the page loading in order for the metric to track.
Click tracking does not work on elements that include escaped characters in their selectors, including the following:
|#||Number sign or Hash|
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
The following steps are executed by at.js when the click tracking event is attached to an
A (link) tag or a
Fire Target request.
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.
FORMtag: 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.
This video includes information about creating click-tracking success metrics.