Connecting Vibe TV on Clarisights

Vibe is a CTV / OTT advertising platform that runs streaming TV campaigns across major connected-TV channels. Connecting Vibe to Clarisights lets you analyze impressions, completed views, installs, purchases, and signups per advertiser, campaign, strategy, and creative alongside your other paid channels.

At a glance

Authentication API key issued by Vibe (sent as X-API-KEY header)

Permissions needed An API key with read access on Vibe's get_advertiser_ids and create_async_report endpoints

Account discovery Automatic — every advertiser linked to your API key is offered

Data freshness Hourly

Lookback window Rolling 3 days (re-pulled on each refresh)

Backfill on connect Last 3 days; longer history available on request via channel config start_date / end_date

Timezone UTC

Currency USD (default; account-level overrides supported)

Levels supported Account (Advertiser) · Campaign · Strategy (Ad Group) · Creative (Ad)

Limited rollout No

Prerequisites

An active Vibe advertiser account at clear-platform.vibe.co
A Vibe API key issued for your account — request from your Vibe Customer Success Manager. See Vibe's API reporting docs for context.
Knowledge of the attribution window you want to use — Vibe supports 1h, 6h, 12h, 24h, 48h, 72h, 7 days, and 30 days. Default is 7 days.

Steps to Connect

Step 1 — Obtain your Vibe API key

Contact your Vibe CSM and request an API key for your advertiser. Copy the full key value — you'll paste it into Clarisights in Step 3.

Treat your API key like a password. It grants read access to all advertisers linked to it.

Step 2 — Add Vibe TV in Clarisights

In Clarisights, go to Integrations → Vibe TV → Add Account.

[TODO: Screenshot needed — Integrations page Vibe TV row with Add Account button]

Step 3 — Enter credentials

Provide a friendly Account Name for this connection and paste your API Key. Click Validate.

Clarisights authenticates with Vibe (get_advertiser_ids) and retrieves every advertiser linked to your key.

⚠ "Invalid API key. Please check your authentication credentials and try again." → The API key has either expired, been revoked, or was copied with extra whitespace. Re-issue or re-copy the key from Vibe and retry. If the key is recent, confirm with your Vibe CSM that it has been activated for the Reporting API.

Step 4 — Select advertisers

Pick the advertisers you want to connect, optionally rename them, and click Create Accounts. Each advertiser appears as a separate Account in Clarisights.

Verify the connection

Go to Integrations → Vibe TV. Each connected advertiser should show a "Connected" status with the Vibe advertiser ID visible.
First data appears within ~1 hour (Vibe data syncs hourly). Vibe's reporting endpoint is asynchronous — Clarisights submits a report request and polls for completion (up to 5 minutes per pull).
Quick start: create a new report, add Vibe TV as the data source, and add Account · Campaign · Strategy · Impressions · Spend · Completed Views.

Data available

Hierarchy

How Vibe's native levels map to the standard Clarisights levels:

Native level (Vibe)

Clarisights level

Advertiser

Account

Campaign

Strategy

Ad Group (Vibe Strategies are the targeting / bidding unit; surfaced as Ad Groups in Clarisights)

Creative

Dimensions

Dimension

Level

Description

Advertiser ID / Advertiser Name

Account

Vibe advertiser identifier and display name

Campaign ID / Campaign Name

Campaign

Vibe campaign identifier and display name

Strategy ID / Strategy Name

Ad Group

Vibe strategy identifier and display name

Creative ID / Creative Name

Vibe creative identifier and display name

Impression Date (timestamp)

—

Always returned by Vibe; used as the date dimension in Clarisights

Metrics

Metric

Description

Impressions

Total CTV impressions served

Spend

Total spend in account currency

Completed Views

Impressions where the creative played to 100%

Installs

App installs attributed to a Vibe impression / view

Number of Purchases / Amount of Purchases

Purchase events and total revenue attributed to Vibe

Number of Signups

Signup events attributed to Vibe

Number of Custom 1 / 2 / 3 · Cost per Custom 1 / 2 / 3

Up to three customer-defined custom conversion events plus their cost-per-event efficiency metric

Limitations & known constraints

Async reporting + rate limits: Vibe's create_async_report endpoint is rate-limited to 15 requests / hour / user. Clarisights queues report requests and respects this limit; very large account sets may take longer to backfill.
Polling timeout: each report is polled for up to 5 minutes (30 attempts at 10s). Reports that exceed this window are retried on the next pull cycle.
Default 3-day rolling window: regular pulls cover the last 3 days. Reach out to support to backfill longer history via the start_date / end_date channel options.
Segment-by-segment dimensions: Vibe restricts create_async_report to fetching one segment dimension per request — some segment breakdowns will require multiple report runs.
Currency: defaults to USD. Non-USD reporting requires the account-level currency override on the Clarisights ad account.
Timezone: reporting is in UTC; conversion to advertiser-local time is handled by Clarisights' reporting layer.

Operating notes

Refresh schedule: hourly DAG named vibe-tv.
Lookback: rolling 3 days.
Multi-account: a single API key can connect every advertiser linked to it. Use separate keys to onboard advertisers managed by different Vibe CSMs.
Currency conversion: spend is sent in USD by default and converted to your reporting currency by Clarisights.
Credential rotation: rotate the API key any time from Integrations → Vibe TV → Edit API Token.
Attribution window: configurable via the channel config; default 7 days. Supported values: 1h, 6h, 12h, 24h, 48h, 72h, 7 days, 30 days.
Event time selection: choose between event_time (default) and impression_time via channel config.

Need help?

When contacting support from the in-app messenger, please include:

The integration name and Vibe advertiser ID (Integrations → Vibe TV)
The exact error message or screenshot
The step where the issue occurred
When the issue started