MNTN's Creative Tracking feature allows you to pass MNTN impression and visit data into a third-party database for use in performance measurement and attribution.
In this article we'll review:
MNTN's Creative Tracking Feature: How It Works
MNTN's Creative Tracking feature has two components:
⭐️Impression Tracking: This enables you to add third-party impression URLs as impression tags. These tags pass MNTN impression data to your third-party measurement platform for viewability, measurement, and real-time verification of your ads at the time of the ad impression.
⭐️Macro Enabled Visit Tracking: This enables you to add third-party visit webhook URLs as MNTN macro-enabled visit tracking tags, otherwise known as VISTA tags. These tags then pass MNTN Cross-Device Verified Visit data to your third-party measurement platform at the time of the site visit.
When an MNTN event occurs, data is returned to the macro and sent to your third-party platform, giving you full visibility into your MNTN impressions or Verified Visits. These tags can be applied at either the account or creative level, giving you complete control over the MNTN data transferred to your third-party measurement platform.
💡 Note: You cannot append hardcoded UTMs here, only dynamic tags. Hardcoded UTMs, suffix tags and site-served visit tracking tags should be implemented within every video ad's tracking parameters.
MNTN Creative Tracking: Formatting Requirements
For the MNTN Creative Tracking functionality to pass back these data points, your links appended third-party webhook URLs must meet our formatting requirements below:
Macro-Enabled Visit Tracking: Formatting Requirements
In addition to the macros listed below, your third-party webhook visit tracking URL must meet the following requirements to function as a MNTN Macro-Enabled Visit Tracking tag:
Accepted Tag Types | Unaccepted Tag Types | Supported Destination Tracking Servers |
Valid URL Strings.
**The URL must return an HTTP 200 code when it's called. |
| Not sure if we can pass data to your platform?
Reach out to a member of the MNTN support team. |
Impression Tracking: Formatting Requirements
In addition to the macros listed below, your impression tracking URL must meet the following requirements to function as a MNTN Impression tracking tag:
Accepted Tag Types | Unaccepted Tag Types | Supported Destination Tracking Servers |
**The URL must return an HTTP 200 code when it's called. |
| Not sure if we can pass data to your platform?
Reach out to a member of the MNTN support team. |
💡 Note: URL formatting is case-sensitive. If your URL needs capitalization, contact the Platform Experience team via a support request.
Available Macros
For the MNTN Creative Tracking Service to send the correct data to your third-party measurement platform, your third-party webhook URL's macros must meet the supported syntax outlined below.
The macros seen in the table below are the only dynamic macros our Creative Tracking service allows for.
Macro | Description |
${aid} | Returns the advertiser ID associated with the event. |
${campaign_name} | Returns the name of the campaign that the creative was attached to at the time it was served |
${creative_name} | Returns the name of the creative that was served |
${cagid} | Returns the campaign ID of the campaign associated with the event. |
${cgid} | Returns the creative group ID for the creative set associated with the event. |
${crid} | Returns the creative ID of the specific ad size associated with the event. |
${ip} | Returns the IP address the event occurred on. |
${device_id} | Returns the device ID for the device the event occurred on. |
${timestamp} | Returns the time the event occurred in GMT, recorded in milliseconds. |
${publisher} | Returns the name of the TV Network or web domain your ad was served on. |
${random} | Returns a random number associated with the event that acts as a cache buster. |
${useragent} | Returns the user agent of the device the event occurred on. |
⚡️ You may see a higher number of Creative IDs and Creative Group IDs in your 3rd party reporting than the number of creatives you have running in MNTN. This is because our system assigns multiple creative IDs per creative group for backend ad-serving purposes.
We recommend that you also leverage the creative name macro, ${creative_name} when using the Creative ID and Creative Group ID macros to assist in associating the IDs to the proper creatives.
Related Articles: