MNTN (Connected TV)

This is a working draft for this integration.

Integrating MNTN with Spacetime allows you to track Connected TV (CTV) performance alongside your other marketing channels. Since CTV ads are viewed on a television and aren't clickable, MNTN relies on Verified Visits — a view-through attribution model that matches TV ad exposure to subsequent website activity using IP-based signals.

---

How It Works

MNTN attribution differs from search and social ad platforms in a few important ways:

• No click-through tracking. TV ads can't be clicked, so MNTN uses server-side webhooks (VISTA Tags) to notify Spacetime when a verified visit occurs after ad exposure.

• IP-based matching. MNTN identifies visitors by correlating the IP address from the TV impression with the IP address of the subsequent website visit. This is effective for most residential traffic, though match rates may be lower in environments with shared IPs (e.g., corporate networks or hotel lobbies) or VPN usage.

• Clickable display ads. MNTN also supports "Multi-Touch" display and interactive ad formats that do support click tracking via URL macros.

---

Prerequisites

• An active MNTN account with API access enabled

• Admin access to your Spacetime property

• Access to the Creative Tracking settings in your MNTN account

---

1. Connect Your Reporting API Key

MNTN uses a static Reporting API Key for authentication — no OAuth flow or token refresh is required.

1. Sign in to your MNTN account.

2. From the account dropdown in the top-right corner, select My Account.

3. In the left navigation pane, select the API tab.

4. Copy your Reporting API Key.

5. In your Flip.to platform, go to Platform → Mission Control → Integrations → MNTN and paste the key into the API Key field.

6. Click Save.

Your API key does not expire. Spacetime uses it to perform automated daily syncs of your campaign spend and performance metrics.

API Version: MNTN has transitioned to API 3.0. Spacetime connects to api3.mountain.com for improved performance and data granularity. If you encounter issues with legacy API endpoints (api.mountain.com), confirm your account has been migrated to API 3.0 in your MNTN account settings.

---

2. Set Up VISTA (Verified Visit) Tracking

VISTA Tags are the primary attribution mechanism for CTV. When MNTN detects that a user visited your site after being exposed to a TV ad, it fires a server-side webhook to Spacetime with the visitor's IP and campaign metadata.

1. In your Flip.to platform, go to Platform → Mission Control → Integrations → MNTN and copy your unique Webhook Listener URL.

2. In the MNTN platform, navigate to My Account → Creative Tracking.

3. Locate the Default Macro-Enabled Visit Tracking section.

4. Paste your Spacetime Webhook URL and append the required macros:

https://spacetime.flip.to/webhook?mntn_campaign_id=${cagid}&mntn_ad_id=${crid}&ip_address=${ip}

1. Click Save Changes.

Data Freshness & Attribution Delay

VISTA webhooks are fired in near real-time as verified visits are detected. However, MNTN's Cross-Device matching — which correlates a TV impression on one device with a website visit on another (e.g., TV ad → mobile visit) — typically takes 2–5 minutes to complete. During initial testing, this is normal and does not indicate a configuration problem.

Daily reporting data synced via the API typically reflects the prior day's finalized activity.

---

3. Add URL Macros for Clickable Ads

For Multi-Touch display or interactive ads that support clicks, add tracking parameters to your destination URL so Spacetime can attribute the visit to the correct campaign.

1. Go to the Tracking Parameters section of your MNTN ad.

2. In the Visit URL field, append your parameters using the ${macro} syntax:

utm_source=mntn&mntn_campaign_id=${cagid}&mntn_ad_id=${crid}

Syntax Note: MNTN macros use a dollar sign and curly braces ${macro}. The double-brace format {{macro}} used by other platforms will not work. Don't include a leading ? — MNTN's Visit Tracking field automatically appends a ? to the destination URL before your parameters. Starting your string with ? will result in a malformed URL (??utm_source=...). Enter your parameters starting directly with the first key (e.g., utm_source=mntn...).

Available Macros

Data Point	Macro	Description
Campaign ID	${cagid}	Unique ID for the MNTN campaign
Creative ID	${crid}	Unique ID for the specific ad creative
Advertiser ID	${aid}	Unique ID for your MNTN account
IP Address	${ip}	Visitor IP (required for CTV visit matching)

---

4. Enable Conversion Matching (Optional)

This step is optional but recommended for properties that want to tie CTV exposure directly to booking revenue.

For properties that track direct bookings, MNTN can match specific transactions back to TV ad impressions using an order_id field. This enables revenue attribution in both Spacetime and MNTN reporting.

1. Ensure your MNTN conversion pixel includes the order_id parameter, populated with your booking confirmation or transaction ID.

2. Spacetime will reconcile these order_id values against on-site conversion events to provide accurate revenue attribution for your CTV campaigns.

---

API Rate Limits

The MNTN Reporting API does not publish strict rate limits, but Spacetime's daily sync cadence is well within normal usage thresholds. If you manage a large number of properties under a single MNTN account, Spacetime batches requests to avoid excessive API calls.

---

Troubleshooting

Low verified visit match rates

IP-based matching works best with residential internet connections. If your property sees high traffic from corporate networks, hotel WiFi, or VPN users, expect lower match rates. This is a known limitation of CTV attribution and not specific to the Spacetime integration.

Webhook data not appearing

• Verify that the Webhook Listener URL in MNTN exactly matches the URL shown in Platform → Mission Control → Integrations → MNTN.

• Confirm that all three required macros (${cagid}, ${crid}, ${ip}) are present in the URL.

• Check that the VISTA tag is saved under Default Macro-Enabled Visit Tracking, not a campaign-specific override.

• Allow 2–5 minutes during testing. Cross-Device matching introduces a short attribution delay before verified visits appear. If data still hasn't arrived after 10 minutes, check the URL configuration above.

Reporting data delayed

Daily reporting syncs pull the prior day's finalized data. If you recently connected your API key, the first sync will occur within 24 hours.