MNTN

​

Overview

MNTN is a Performance TV advertising platform for running campaigns on connected TV. With the MNTN destination, you can build MNTN audience segments from your warehouse data to target or suppress on your campaigns, and send conversion events such as purchases and sign-ups to measure campaign performance.

​

Supported syncing

For more information about sync modes, refer to the sync modes docs.

​

Connect to MNTN

Hightouch connects to MNTN with an Audience API key. One key covers both segment and event syncs. To create a key, sign in to MNTN, go to My Account > API, click Connect, and create an Audience API key. MNTN allows up to three Audience API keys per account, so you can keep Hightouch on its own key. Each key belongs to a single MNTN advertiser account, and every segment Hightouch creates or lists comes from that account. Enter the key as the Audience API key when you set up the destination in Hightouch. When you test the connection, Hightouch lists your MNTN segments to confirm the key works. If the test reports that the Audience API isn’t enabled, contact your MNTN account team to enable it for your account.

​

Sync configuration

Once you’ve set up your MNTN destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the MNTN destination you want to sync to.

​

Segment

Use a segment sync to keep an MNTN audience segment matched to your model. Hightouch adds people when they enter your model and removes them when they leave, so the segment stays current between runs. To suppress people, such as existing subscribers or recent purchasers, sync them to a segment and add that segment as an exclusion on your MNTN campaigns. MNTN uses the same kind of segment for targeting and suppression, and you choose on each campaign whether it targets or excludes the segment. Retargeting campaigns can only use these segments as exclusions. See MNTN’s guide to sourcing audiences with CRM data for how segments apply to each campaign type.

​

Select an existing segment or create a new one

Choose Create a new audience to have Hightouch create the segment on the first sync run. The segment uses the name you enter, or your model’s name if you leave it blank, and is created with the ID hightouch-<your sync's ID>. Choose Use an existing audience to sync to a segment that already exists in your MNTN account, and select it from the list.

​

Map identifiers

Map one or more identifier columns. MNTN matches each identifier to households, so mapping more identifiers reaches more of your audience. Hightouch formats each identifier the way MNTN expects before sending it: Hightouch hashes emails and phone numbers automatically. Values that are already SHA-256 hashed are sent as they are, so you can mix hashed and unhashed columns. If you set Would you like Hightouch to automatically detect if your PII data requires hashing? to No, Hightouch sends unhashed emails and phone numbers in plain text. An identifier that isn’t valid, such as a malformed phone number, IP address, or MAID, is left out, and the rest of the row’s identifiers still sync. Hightouch only rejects a row when it has no usable identifier at all.

​

Configure delete behavior

Keep Remove the MNTN record from the specified audience selected so people who leave your model are removed from the segment. For a suppression segment, this lets people back into your campaigns when they no longer qualify, for example after a subscription ends. Choose Do nothing only when the segment should keep growing and never drop anyone.

​

Event

Use an event sync to send conversions, such as purchases or sign-ups, to MNTN server-to-server.

​

Event properties

Configure these fields for each event:

• Event name: A column or static value naming the conversion, such as Purchase or Start Trial. Event names can be up to 128 printable ASCII characters.
• Timestamp: The column containing the time the conversion happened. Hightouch keeps sub-second precision.
• Identifiers: The same identifiers as segment syncs, formatted and hashed the same way. Map at least one so MNTN can attribute the conversion.

You can also map these optional fields:

• Event ID: A unique ID for the event, which MNTN uses to de-duplicate events sent more than once. Map it whenever your model has one.
• Order ID, Order amount, and Currency (ISO 4217 code): Order details for purchases. The currency must be a three-letter code such as USD.

Hightouch rejects an event when it has no usable identifier, its event name is empty or too long, its timestamp is empty, its order amount isn’t a number, or its currency isn’t a three-letter code.

​

Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .

​

Behavior and limitations

• MNTN doesn’t report per-person results. MNTN processes additions, removals, and events after accepting them, and doesn’t report which people it matched. A successful sync run means MNTN accepted the data, not that every person matched a household.
• Each sync manages its own segment members. Hightouch identifies people in a segment by your sync’s ID and your model’s primary key, so two syncs can share a segment without overwriting each other. If you delete a sync and create a new one for the same existing segment, the old sync’s members stay in the segment. To start from an empty segment, sync to a new one instead.
• Run segment syncs on a schedule. MNTN recommends refreshing segments daily or weekly so they stay current. Let your MNTN account team know which schedule you choose so they can monitor it.

​

Validate your setup

After your first segment sync completes, open your audience list in MNTN and find the segment by its name. MNTN lists new segments within minutes, and the segment is then available to add to campaigns as a target or an exclusion. For event syncs, MNTN accepts conversions without returning per-event results to Hightouch. Confirm with your MNTN account team that conversions are arriving and attributed to your campaigns.