Tracking events for creatives gives you and your team an even deeper understanding of how audiences are interacting with creatives. This knowledge helps you improve users' experience, and ultimately improves your campaign performance.
NEXD Campaign Manager creatives track all of the most important actions a user can take within the creative, and much of this is already available within the analytics dashboard.
This can include, for example, what assets have been viewed the most and which of those have generated the most clicks.
Access events
The full event list can be seen in your analytics dashboard at the bottom of the page.
You can also order daily event reports to be sent directly to your inbox by exporting the campaign from the analytics dashboard.
Default events
Different layouts use different sets of metrics, but these events are shown regardless of layout:
CTR
- how many users clicked on the ad that directed them to your landing page. This does not include clicks that interact differently with the ad (eg pausing or unmuting a video).Unique [Hover]
- how many users hovered with their mouse over the ad. As you probably guessed, hovering cannot be tracked on mobile devices.Unique [Touch]
- how many users touched the ad, including click, swipe, scratch, etc.Unique [Gyro]
- how many users used the gyro or motion sensor feature on their phones.
Video-specific events
When you have added video asset(s) to the creative you get the following events for every video asset (named video_1, video_2, ..., video_n):
VTR [0...n]
- number of users that viewed the length of the video in percentages. Percentages are in 25% steps: 0, 25, 50, 75, and 100.Play
- number of users that played the video (including automatic play).Pause
- number of users that paused the video.Mute
- number of users that muted the video.Unmute
- number of users that unmuted the video.
Page-based layouts
Some layouts have pages, sides, cards, etc that produce special events:
CTR [Asset X]
- how many users clicked on the asset on the ad (eg "First media", "Second media", "Overlay logo").Page seen [Asset Y]
- how many users saw the asset on the ad (eg "First media", "Second media", "Overlay logo").Navigation Left/Right
- number of users who first swiped or dragged the mouse to the left or right. The event is fired after 10 pixels of movement.
Error events
Sometimes you might notice the following error in the Campaign Manager UI.
ERROR: CLICKURL MISSING - This error appears when there is no asset-specific URL nor global click URL. To fix this, add an asset-specific URL or a global click URL. The latter will always be the fallback.
Layout-specific events
3D cube, Blinds swipe, Carousel and Train
Left arrow image
orRight arrow image
– number of users who clicked the control icon to see the next asset. Please note that only for Train, the control icons are shown by default.
3D cube (horizontal), Blinds swipe and 3D roller (horizontal)
Left
orRight
– number of users who navigated to the left or right.
3D cube and 3D roller (vertical)
Up
orDown
– number of users who navigated to up or down.
Flip
Flipped
– number of users who scrolled past 50% (so the asset flipped and showed the next one).
Scratch
Scratched
– number of users who scratched the top surface.
Scroll to map
Navigation [Map]
– number of users who scrolled up to see the interactive map.Navigation [Location X]
– number of users who clicked on a location namedLocation X
on the map. The location name is taken from the spreadsheet that you uploaded and what is visible to the user.
CTR [Location Y]
- number of users who clicked on the location namedLocation Y
.
Map, Map with horizontal drag and Map with vertical drag
Navigation [Map]
– number of users who swiped to see the interactive map.Navigation [First]
– number of users swiped back to first media.Navigation [Location X]
– number of users who clicked on a location namedLocation X
on the map. The location name is taken from the spreadsheet that you uploaded and what is visible to the user.CTR [Location Y]
- number of users who clicked on the location namedLocation Y
and viewed the directions from their default navigation app.
Scroll to zoom
Zoomed to max
– number of users who scrolled the layout to the top to see the image in full view.
Slider
In addition to the page-based layout events:
Navigation Drag
– number of users who dragged the slider more than 30% of the placement width.Navigation Replay
- number of users who clicked on the “Back to start” icon
Survey
Navigation Intro
andNavigation Outro
– number of users who saw the intro or outro screen.CTR (question A) (choice B)
- number of users who clicked on the choice B in the question A.
Tiles
Flipped
– number of users who dragged the asset or used the gyroscope to flip the asset and were shown the next one.
All mobile fullscreen layouts
Closed
- number of users who closed the ad from the Close icon.
CTR State [1...n]
- number of users who clicked on an element that led to the state in the brackets.
Feature-specific events
CTR [Overlay Element X]
- how many users clicked on the additional overlay asset namedOverlay Element X
. You can set the name when you add or edit the new element.
CTR [Calendar Google]
- how many users opened the calendar with Google CalendarCTR [Calendar Auto]
- how many users opened the event with the user's default calendar application. Please note that we are not able to detect exactly what application it is (for example Apple Calendar, Microsoft Outlook, etc)CTR [Calendar ICS]
– how many users downloaded calendar event in ICS format. This is a very widely used format, so we default to this option when no calendar application is available and the user is not using Google Calendar.
data-onevent-dragto-left="tracker-url-for-left-tracking" - how many users first dragged to left
data-onevent-dragto-right="tracker-url-for-right-tracking" - how many users first dragged to right
Using your own tracking platform
You can also use your own tracking platform with 3rd party events. In a nutshell see the event name above, normalize (replace spaces with hyphens and use lowercase) and add data-onevent-
before it. For example:
Event named
Scratched
becomesdata-onevent-scratched
in the tagEvent names
Navigation [Map]
becomesdata-onevent-navigation-map
in the tag
For more details see the third-party trackers article.