All Collections
Campaign Creative
Creative Tracking
Understanding MNTN's Creative Tracking Feature
Understanding MNTN's Creative Tracking Feature

Details on how MNTN's Creative Tracking feature can streamline third-party measurement.

Kelsey Dupere avatar
Written by Kelsey Dupere
Updated over a week ago

MNTN's Creative Tracking Feature: How It Works

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.

MNTN's Creative Tracking feature has two components:

⭐️Default Visit Tracking: This enables you to add third-party visit webhook URLs as MNTN macro-enabled visit tracking tags. These tags then pass MNTN cross-device verified visit data to your third-party measurement platform at the time of the site visit.

⭐️Default Impression Tracking: This enables you to add third-party impression URLs as macro-enabled impression tags. These tags pass MNTN impression data to your third-party measurement platform for viewability, measurement, attribution, and real-time verification of your ads at the time of the ad impression.

πŸ’‘ Note: MNTN's Macro-Enabled Visit Tracking is only compatible with third-party platforms that support webhook URLs. If your third-party measurement platform doesn't support webhooks URLs, refer to our Site-Served Visit Tracking article.

By including your third-party webhook URLs and impression tracking URLs as MNTN macro-enabled tags, you establish a connection between MNTN and your third-party measurement partner for attribution and/or reporting purposes.

These URLs you've added contain macros, or placeholders, which serve as containers for specific data points. When an MNTN event occurs, the data associated with the macros is dynamically transmitted from MNTN to your third-party platform in real-time, allowing complete visibility into your MNTN campaign performance within your third-party measurement platform.

πŸ” Example Data Points: timestamp, IP address, device ID, etc.

πŸ’‘ Note: For MNTN's Creative Tracking service to pass back these data points, your appended third-party webhook URLs must adhere to our creative tracking formatting requirements.

What's even better is that 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. Details on implementing your third-party URLs are outlined here.

πŸ’‘ 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. More on site-served tracking tags here.


MNTN Creative Tracking: Formatting Requirements

To ensure the MNTN Creative Tracking functionality operates as intended, your third-party webhook URLs must meet the requirements below.

πŸ’‘ URL formatting is case-sensitive. If your URL needs capitalization, contact the Platform Experience team via a support request.

Default 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.

  • Standard UTM Tags

  • Macros that do not match the MNTN Tracking Service syntax seen above.

  • iFrame tags

  • Javascript tags

  • Image Tags

  • VAST tags

Not sure if we can pass data to your platform?

Reach out to a member of the MNTN support team.

Default Impression Tracking: Formatting Requirements

In addition to the macros listed below, your third-party webhook impression tracking URL must meet the following requirements to function as a MNTN macro-enabled impression tracking tag:

Accepted Tag Types

Unaccepted Tag Types

Supported Destination Tracking Servers

  • Valid URL Strings

  • Image (IMG) Tags

**The URL must return an HTTP 200 code when it's called.

  • Standard UTM Tags

  • Macros that do not match our MNTN Tracking Service syntax seen above.

  • iFrame tags

  • Javascript tags

  • VAST tags

Not sure if we can pass data to your platform?

Reach out to a member of the MNTN support team.

All Creative Tracking Tags: 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.

πŸ’‘ Note: The use of event in the below table is dependent upon the tag your team is using:

  • If using a macro-enabled visit tracking tag, event refers to MNTN verified visit.

  • If using a macro-enabled impression tracking tag, event refers to MNTN ad impression.

Macro

Description

Notes

${aid}

Returns the advertiser ID associated with the event.

This is a unique identifier set by MNTN.

${cagid}

Returns the campaign ID of the campaign associated with the event.

This is a unique identifier set by MNTN.

${campaign_name}

Returns the name of the campaign that the creative was attached to at the time it was served

${cgid}

Returns the creative group ID for the creative set associated with the event.

This is a unique identifier set by MNTN.

This macro provides the specific ID of the creative (video or MT) associated with the event.

${creative_name}

Returns the name of the creative that was served

${device_id}

Returns the device ID for the device the event occurred on.

${crid}

Returns the creative ID of the specific ad size associated with the event.

${ip}

Returns the IP address the event occurred on.

${random}

Returns a random number associated with the event that acts as a cache buster.

This is generally used as a cache buster for URL called from a browser.

${timestamp}

Returns the time the event occurred in GMT.

The timestamp is returned in milliseconds.

${useragent}

Returns the user agent of the device the event occurred on.

Did this answer your question?