MNTN Audiences

Not available yet. MNTN Audiences appears in the destinations list and accepts credentials, but it cannot sync audiences. Do not plan campaigns around it. To sync an audience today, use Vibe CTV Audiences.

MNTN Audiences will let you send the members of an Ours Privacy audience to MNTN as an audience segment you can target with connected-TV campaigns. This page covers what you can do today and what to get ready in MNTN.

Not the same as the MNTN destination. MNTN sends events (page views and conversions) so MNTN can measure what your CTV campaigns drove. MNTN Audiences (this page) sends audience membership so MNTN has a list of people to target. They are separate destinations with separate settings, and most accounts will eventually want both. If you are trying to measure campaign performance, you want MNTN.

---

What works today

You can add the destination and save its API key, so the setup is ready in advance. That is the extent of it.

Attaching an audience to this destination has no effect in MNTN: no segment is created, and no members are uploaded. The attempted sync is recorded against the audience as failed, with a message saying the destination cannot sync yet, so it will not look like a healthy sync that quietly produced nothing.

---

MNTN-side prerequisites

Get these in place before you plan campaigns around the destination.

• An active MNTN advertiser account.
• Access to the MNTN Integrations Marketplace, so you can add the Ours Privacy connector and generate an API key. This is the same marketplace you use for the MNTN events destination, but generate a key for the audience connector rather than reusing one issued for something else.
• The right MNTN account. The API key is the only credential this destination takes, and it is what tells MNTN which account owns the audience. A key issued from a different MNTN account creates audiences your campaigns cannot target, and nothing about the sync will look wrong when that happens.
• An audience worth targeting. MNTN does not publish a minimum audience size, but a very small audience is unlikely to yield enough matched viewers to run a campaign against.

---

Credentials it will ask for

When you add the destination, the settings page asks for one field:

• MNTN API Key generated from the Ours Privacy connector in the MNTN Integrations Marketplace. Copy it as soon as MNTN shows it. There is no advertiser ID or account ID to enter: the key identifies the account by itself.

---

What to expect when it ships

It will work the way the other Audience Destinations do, described on Audience Destinations: the audience syncs daily, and the audience's Export Name is the only label MNTN sees.

Two things worth knowing now, because they affect how you name and size an audience:

• MNTN displays the Export Name in its own interface, so keep it meaningless rather than descriptive. Ours Privacy blocks Export Names carrying health context regardless of destination.
• The matched audience in MNTN will be smaller than the count in Ours Privacy. MNTN can only match people it already recognizes in its connected-TV graph.

This page gets updated with the setup steps, the identifiers used for matching, and the exact sync behavior when it goes live. To be told when that happens, contact your account representative.

---

Next Steps

• Audience Destinations for how audience syncing works.
• Vibe CTV Audiences for the Audience Destination available today.
• MNTN to send page views and conversions to MNTN, which works today.
• Audience Builder to build and export audiences now.

Need help? Contact support@oursprivacy.com.