Skip to main content
When Scope3 reads audiences, signals, or event sources from a connected ad platform account (see Connecting Ad Platform Accounts), what comes back depends on the platform. Some platforms return the account’s complete inventory. Others can only see objects that were created through Scope3, or return a single derived entry rather than a real inventory read. This page documents that coverage per platform so you know when a result is the whole picture and when it is not.
This page covers direct ad platform adapter connections (Meta, TikTok, Google Ads, and similar). On platform-composed storefronts, the same question is answered by the get_account_resources tool, which labels capability and coverage per source on every response — see AdCP on the buy side. Direct adapter storefronts do not expose that tool.

​
Reading the tables

Each read falls into one of four coverage classes: Two more distinctions matter when interpreting any of these reads:
  • Discovery is not attachment. These reads answer “what exists in the account right now” by asking the platform directly. An object appearing in a discovery read does not mean it is attached to, or usable by, any particular campaign — and an object synced through Scope3 remains tracked even if a later discovery read cannot see it.
  • Only a full-inventory read is authoritative. A bound-only or synthesized result is still real data, but absence from it proves nothing about the account. Never treat a partial read as evidence that an object does not exist.

​
Audiences

Audience inventory is read with a discovery-mode sync_audiences call (no audience list supplied, so nothing is created or modified). No audience membership data is ever returned — identity, status, and match counts only.
On TikTok and Snap, an audience discovery read is a trust boundary: it shows what Scope3 manages, not what the account contains. Do not use it to audit the account’s full audience inventory on those platforms.

​
Signals

Signals are read with get_signals, a read-only projection of the platform’s audience inventory into AdCP signal references. Signal coverage follows the platform’s audience coverage above: on a platform whose audience read is bound-only, the signal projection inherits the same limitation.

​
Event sources

Event sources (pixels, tags, conversion actions) are read with a discovery-mode sync_event_sources call. No event payloads or setup secrets are returned. Seller-managed entries describe measurement the platform performs natively. Synthesized entries confirm the platform’s tagging surface exists for the account but say nothing about which tags are actually installed.

Connecting Ad Platform Accounts

How account access is granted and what write access means

Ad Platform Accounts

Organization vs advertiser accounts and how discovered accounts map to advertisers