Connecting Singular on Clarisights

Singular is a unified marketing analytics platform that aggregates ad-network spend with mobile attribution. Connecting Singular to Clarisights pulls Singular's event, cohort (LTV / ROAS), and SKAdNetwork reports and joins them onto your ad channels, so you can analyze post-install performance side-by-side with your direct ad-channel data in Clarisights.

Set up by Clarisights. Singular is not available on the Integrations page. Your Clarisights account manager connects it for you using the Reporting API key you provide. The steps below explain what to prepare.

At a glance

Authentication	API key (Singular Reporting API)
Permissions needed	Reporting API access on your Singular organization
Account discovery	App-based: Clarisights connects the Singular apps you list when you share your API key
Data freshness	Daily
Lookback window	Each daily run covers the longest cohort period configured for your workspace (up to 30 days)
Backfill on connect	On request from your Clarisights account manager
Timezone	Report dates as returned by Singular (day-level granularity)
Currency	As reported by Singular; converted to your reporting currency by Clarisights
Levels supported	Joined onto your ad channel's Campaign · Ad Group · Ad · Keyword
Limited rollout	Yes. Not available on the Integrations page; contact your Clarisights account manager to connect it.

Prerequisites

• An active Singular account with at least one app and one connected ad-network source

• A Singular Reporting API key

• The ad channels you want Singular data joined onto (for example Facebook, Google Ads, Apple Search Ads, TikTok, Snapchat, Twitter, Bing, or a Custom Advertising channel), already connected in Clarisights

Steps to Connect

Step 1: Get your Reporting API key in Singular

Sign in to Singular and copy your Reporting API Key. The key grants read access to every app and source under your Singular organization.

Singular explains where to find your API key (Developer Tools > API Keys) in its guide: Reporting API Reference.

Treat the Reporting API key like a password. Share it with Clarisights only through the secure channel your account manager provides, never in a plain email. If it is exposed, rotate it in Singular.

Step 2: Contact your Clarisights account manager

Send your account manager:

• The Singular apps you want to connect

• The Clarisights ad channels Singular data should be joined onto

• The cohort periods you need (Clarisights supports actual, 1d, 3d, 5d, 7d, 14d, and 30d)

• Any custom in-app events or SKAN events you want exposed as metrics

Clarisights then connects the apps, configures how Singular campaigns, sub-campaigns, and creatives join onto each ad channel, and confirms when data is flowing.

Verify the connection

• First data appears within 24 hours of setup. Singular builds reports asynchronously, so a run can take several minutes on Singular's side.

• Quick start: open a report on one of your joined ad channels (for example Facebook), add Campaign, and add Singular metrics such as Installs or a cohort metric such as Revenue (7d) from the Singular metric groups.

Data available

Hierarchy

Singular returns data along the original ad network's hierarchy. Clarisights joins it onto the matching ad channel's levels:

Native level (Singular)	Clarisights level
App	Connected Singular app
Source (Singular ad-network name)	Ad channel (for example Facebook, Google Ads, Apple Search Ads)
Unified Campaign	Campaign
Ad Network Sub-Campaign	Ad Group (Ad Set / Ad Group / Ad Squad depending on the ad channel)
Ad Network Creative	Ad
Keyword	Keyword (Apple Search Ads only)

Dimensions

Singular data is joined onto your ad channel's objects, so you slice it by that ad channel's dimensions (Account, Campaign, Ad Group, Ad, Keyword, and so on). Singular's own Source, Unified Campaign, Sub-Campaign, Creative, and Keyword fields are used to route and join the data. Platform is exposed through iOS, Android, and Web variants of each metric.

Metrics

Singular metrics appear in four metric groups: Singular Standard Metrics, Singular Custom Events, Singular Cohort Events, and Singular Skan Events.

Standard metrics

Metric	Description
Installs	Attributed installs
Re-engagements	Attributed re-engagements
Tracker Clicks / Tracker Installs	Clicks and installs recorded by Singular's tracker
Standard in-app events	For example Add to Cart, Checkout Initiated, Complete Registration, Ecommerce Purchases, Logins, Start Trial, Subscribe, Tutorial Complete

Platform-specific metrics: iOS, Android, and Web variants of each metric are generated automatically (for example IOS : Installs, ANDROID : Installs).

Cohort metrics (LTV by cohort window): returned for the cohort periods configured for your workspace. Each cohort metric is exposed once per period, for example Revenue (7d):

Metric	Description
cohort metric (period)	Any cohort metric configured in Singular (revenue, ROAS, ARPU, retention, and so on) at each configured period. Precision is 2 decimal places.

Supported cohort periods: actual (no window), 1d, 3d, 5d, 7d, 14d, 30d.

SKAdNetwork (SKAN) metrics

SKAN installs and the SKAN events configured in your Singular SKAN schema, for the events your account manager enables for your workspace.

Limitations & known constraints

• Set up by Clarisights: there is no Singular card on the Integrations page. Connecting apps, adding ad channels, and changing cohort periods or events all go through your Clarisights account manager.

• Async report latency: Singular builds reports asynchronously. Very wide pulls or delays on Singular's side can postpone a daily update.

• Singular row limits: Singular caps how many reporting rows an organization can pull per day and per query. Keep cohort periods and events to what you need.

• Source required for joining: rows without a Singular source that maps to a Clarisights ad channel cannot be joined and are skipped.

• Cohort actuals vs windows: actual period metrics measure events on the report day; windowed metrics (1d, 7d, 30d) measure cohort accumulation. Windowed metrics for recent installs keep updating for the length of the longest cohort period.

• Key revocation: if the Reporting API key is rotated or revoked in Singular, the integration stops syncing until you share a new key with your account manager.

Operating notes

• Refresh schedule: data is pulled daily.

• Lookback: each run re-fetches up to the largest configured cohort period (up to 30 days), so maturing cohorts stay current.

• Adding new ad channels: when you start running a new ad network through Singular, contact your Clarisights account manager so it can be joined onto the right Clarisights ad channel.

• Currency conversion: Clarisights converts Singular revenue to your reporting currency.

• Credential rotation: share the new Reporting API key with your Clarisights account manager.

Need help?

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

• The Singular app and source affected

• Which report type is affected (Event, Cohort, or SKAN)

• The exact error message or screenshot

• The metric, date range, and report where the issue is visible

• When the issue started