Skip to main content

Send MNTN Data to Measurement Platforms

Learn the four ways MNTN data can be shared with external measurement platforms.

Updated today

Overview

If you use a measurement platform outside of MNTN, there are four ways your MNTN data can be shared with it:

  1. Impression tracking

  2. Verified Visit tracking

  3. API or automated report exports

  4. Custom integrations

The method used depends on what data the platform needs. Some platforms measure ad exposure, while others need visit events or campaign performance metrics.

Before You Begin

Before setting up an external measurement partner, confirm what data the platform requires from your MNTN campaigns.

Start with these questions:

  • What data does the platform need to measure campaign performance?

  • Does it require impression exposure data?

  • Can it accept Verified Visit events in place of click events?

  • Does it ingest reporting metrics from advertising platforms?

Once you know what data the partner needs, you can choose the correct integration method.

Four Ways to Send Data From MNTN Campaigns

1. Impression Tracking

Impression tracking sends ad exposure data to another platform when an ad is served.

When the impression fires, a request is sent to the measurement platform so it can record the exposure event. Platforms can then use this data in their own reporting, measurement or lift models.

Use impression tracking when the platform needs:

  • Household ad exposure data

  • Impression-level campaign delivery information

2. Visit Tracking

Visit tracking sends Verified Visit events to another platform.

When the MNTN pixel confirms a Verified Visit, that event can also be sent to an external platform using a webhook endpoint. This allows the platform to incorporate MNTN visit activity into its own measurement.

Use visit tracking when the platform needs:

  • Site Visit events

  • Event-level data, such as click events or view-through visits


๐Ÿ“ Note: Visit tracking requires the receiving platform to support webhook-based event ingestion.


3. API or Automated Report Exports

MNTN reporting data can also be shared through the MNTN API or automated report exports (namely CSV files). This allows measurement platforms to ingest campaign metrics directly from the MNTN reporting dashboard.

Examples of metrics that may be shared include:

  • Spend

  • Impressions

  • Verified Visits

  • Conversions

  • Revenue

Use this method when the platform needs:

  • Campaign performance metrics

  • Reporting data from advertising platforms


โš ๏ธ Warning: Conversion and revenue data exported from MNTN reflect MNTN attribution and are not deduplicated across other marketing channels.

All metrics except conversions are aggregated daily and are not available at the event level. This means impressions and visits do not include timestamps or unique event IDs.


4. Custom Integrations

Some platforms require a more tailored data exchange than the standard options provide. In these cases, a custom integration may be implemented to send the specific data required by the partner platform.

Custom integrations are typically used when a platform has unique technical or ingestion requirements.

Choose the Right Method

The correct method depends on the type of data the platform needs.

If the platform needs

Use this method

Ad exposure data at the household level

Impression tracking

Verified Visit events

Visit tracking

Campaign reporting metrics

API or automated report exports

A tailored data setup

Custom integration

If you're unsure which option is appropriate, start by confirming what data the platform requires.

Quick Answers

Can MNTN send visit events to another platform?

Yes. Verified Visit events can be shared if the receiving platform supports webhook ingestion.

Can reporting data be exported from MNTN?

Yes. All campaign metrics can be shared through the MNTN API or automated report exports.

Did this answer your question?