Skip to main content

MNTN

MNTN is a platform that lets brands of any size create and launch TV commercials on shows, movies, and live sports. This source reads campaign, creative, and advertiser reporting data from the MNTN Reporting API 3.0 (api3.mountain.com).

Prerequisites​

  • An MNTN account with access to Reporting.
  • Your MNTN Reporting API key.

To find the key, sign in to MNTN, open My Account from the account dropdown, click API in the left navigation, then click Copy next to Reporting API. See Access your Reporting API key for details. Every user on your MNTN account can read this key, so treat it like a password.

This source uses MNTN API 3.0. If you also query MNTN from a BI tool or script that still points at api.mountain.com, note that API 1.0 stopped returning reporting data on April 1, 2026.

Configuration​

InputTypeDescriptionDefault Value
api_keystringAPI Key.
start_timestringstart_time.2023-01-01

Set start_time to a date in YYYY-MM-DD format. It becomes the begin date of every reporting query, so it also sets how far back the first sync of the incremental streams reads.

Streams​

Stream NamePrimary KeyPaginationSupports Full SyncSupports Incremental
CampaignDetailsIDNo pagination✅❌
CreativeDetailsID.DayNo pagination✅✅
CampaignID.DayNo pagination✅✅
CreativeID.DayNo pagination✅✅
AdvertiserID.DayNo pagination✅✅

The streams fall into two groups:

  • CampaignDetails and CreativeDetails return configuration data. CampaignDetails returns one row per campaign with its name, status, budget, flight dates, and goal. CreativeDetails returns one row per creative per day with its name, creative group, active flag, template creative, and click URL.
  • Campaign, Creative, and Advertiser return daily performance metrics at the campaign, creative, and account level: impressions, spend, visits, conversions, order value, ROAS, reach, and frequency.

Sync behavior and limitations​

  • Performance metrics use First Touch attribution, which is the API 3.0 default. Each performance stream also carries the equivalent Last Touch fields, such as LastTouchConversions and LastTouchROAS, so you can compare both models.
  • Every field, including numeric metrics and dates, arrives as a string. Cast the values you need in your destination or transformation layer.
  • The incremental streams use Day as the cursor and read one day per request. A first sync that starts several years in the past therefore issues one request per day in that range, which takes a while. Set start_time no earlier than you need.
  • CampaignDetails has no date dimension, so it's full refresh only: every sync reads from start_time through the current date in a single request. What your destination does with those rows depends on the sync mode you choose for the stream.
  • The connector calls MNTN's synchronous reporting endpoint. MNTN recommends its asynchronous /batch endpoint for requests that cover more than four months of data, return high-cardinality data, or time out. CampaignDetails requests your entire window in one call, so keep that guidance in mind when you set an early start_time.
  • MNTN doesn't publish rate limits for the reporting API.

Reference​

Config fields reference

Field
Type
Property name
API Key
required
string
api_key
string
start_time

Changelog​

Expand to review
VersionDatePull RequestSubject
0.0.132026-11-0389296Update dependencies
0.0.122026-10-1388719Update dependencies
0.0.112026-10-0687917Update dependencies
0.0.102026-09-2987263Update dependencies
0.0.92026-09-2286728Update dependencies
0.0.82026-09-1586150Update dependencies
0.0.72026-09-0885583Update dependencies
0.0.62026-08-2685027Enable acceptance test suite with GSM test secrets
0.0.52026-08-1884647Update dependencies
0.0.42026-08-1184027Update dependencies
0.0.32026-08-0483541Update dependencies
0.0.22026-07-2883005Update dependencies
0.0.12026-07-2781334Initial release by @Ella6882 via Connector Builder
Was this page helpful?