FAQs

​

Why can’t I switch my Singular data source from SKAN to Unified?

The report mode — SKAN or Unified — is chosen when the data source is created and is permanent. The two modes use different attribution data, metrics, and breakdowns, so a data source is built for one or the other and cannot be converted after the fact. To move from one mode to the other, create a new Singular data source and select the other mode during setup. See How to connect Singular to Adriel. The original data source can stay connected in parallel, or be removed once the replacement is verified.

​

Why do my most recent SKAN numbers keep changing?

SKAN attribution follows Apple’s SKAdNetwork postback timer rather than arriving all at once. Installs and conversion values are reported across Postback 2 and Postback 3, which land on a delay after the install. Until those later postbacks arrive, the most recent days are incomplete and continue to settle as more data comes in. This is expected for SKAdNetwork data and is not a sync error. Older days, whose postback windows have already closed, stabilize and stop changing. For the schedule on which Adriel pulls fresh data, see the Singular data reference.

​

Why did my first Singular sync take several minutes?

Singular delivers reports asynchronously. Adriel submits a report job and waits for Singular to finish generating it before the data can be loaded, so the first sync of a wide date range takes longer than an instant refresh. Two things add to the initial wait:

• Backfill of older dates. After connection, Adriel retrieves an initial window of historical daily data. Because Adriel caches each day it fetches, the longer the data source stays connected, the more historical data is stored. Queries that reach back before the cached window trigger additional report jobs to fill the gap.
• Report generation time. Each report job is queued and processed on Singular’s side, which is where most of the wait comes from.

Subsequent refreshes are faster because already-cached days are skipped. See the Singular data reference for the initial import window and refresh details.

​

Can one Singular data source report on more than one app?

No. Each Singular data source maps to a single app, selected when the data source is created. A SKAN or Unified data source returns data only for its configured app. To report on several apps, create a separate Singular data source for each one, then combine them on a single dashboard by adding a widget per app or by aggregating across widgets. Metrics, breakdowns, and currencies are standardized, so widgets can read from multiple Singular data sources together.

​

Why don’t SKAN and Unified metrics appear in the same data source?

SKAN and Unified are mutually exclusive modes, and each exposes its own fixed set of metrics and breakdowns. A SKAN data source surfaces SKAdNetwork installs, conversion-value counts, and postback counts, plus any configured SKAN events. A Unified data source surfaces standard cross-network metrics such as ad-network and tracker installs, clicks, impressions, cost, video, and any cohort or conversion metrics configured in the account. Because a data source is one mode, the two metric sets never appear together. To see both, connect one data source in each mode and place their widgets on the same dashboard. Cohort and conversion metrics (Unified) and SKAN events (SKAN) are read from the account’s Singular configuration, so the exact list available depends on the workspace. For the full field list, see the Singular data reference.

​

Where do I set my attribution windows?

Attribution-window logic is configured per app inside Singular, not in Adriel. The connector reports whatever windows Singular returns. SKAN data additionally follows Apple’s SKAdNetwork postback timing, which is fixed by the platform rather than adjustable in either tool. To change how attribution is measured, update the app’s settings in Singular. The new configuration is reflected in Adriel on the next sync.

​

Related