> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Ad Platform Resource Capabilities
> Which audiences, signals, and event sources each connected ad platform can report — and how complete each read is
When Scope3 reads audiences, signals, or event sources from a connected ad
platform account (see [Connecting Ad Platform
Accounts](/v2/guides/connecting-ad-platforms)), 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](/v2/concepts/adcp-on-the-buy-side#linked-account-scope).
Direct adapter storefronts do not expose that tool.
## Reading the tables
Each read falls into one of four coverage classes:
| Coverage | Meaning |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Full inventory** | A discovery read returns every eligible object in the account. Treat the result as the account's complete inventory. |
| **Bound only** | The platform reports only objects that were created or synced through Scope3. Objects created directly in the platform's own UI are invisible — the result under-counts the real account inventory. |
| **Synthesized** | The result is a single entry derived from the account itself (for example, a tag id computed from the account id), not a read of the platform's inventory. |
| **Seller managed** | The platform returns objects it manages natively — you did not create them and cannot modify or delete them through Scope3. |
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.
| Platform | Coverage | Notes |
| ---------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meta | Full inventory | All customer-list Custom Audiences in the ad account |
| Google Ads | Full inventory | |
| Reddit | Full inventory | |
| Spotify | Full inventory | |
| Pinterest | Full inventory | |
| LinkedIn | Full inventory | |
| TikTok | **Bound only** | Only audiences created through Scope3 are visible. Custom Audiences created in TikTok Ads Manager do not appear — the read under-counts the account. |
| Snap | **Bound only** | Only audiences created through Scope3 are visible. Customer Lists created in Snap Ads Manager do not appear — the read under-counts the account. |
| Amazon Ads | Not available | Amazon DSP audience reads require AMC integration, which is not yet supported |
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.
| Platform | Availability |
| -------------------------------------------------------------------- | ---------------------------------------- |
| Meta, Google Ads, TikTok, Snap, Reddit, Pinterest, LinkedIn, Spotify | Available |
| Amazon Ads | Not available — requires AMC integration |
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.
| Platform | Coverage | What comes back |
| ---------- | -------------- | -------------------------------------------------------------------------------------------------------------- |
| Meta | Full inventory | All pixels in the account |
| TikTok | Full inventory | All pixels in the account |
| Snap | Full inventory | All pixels in the account |
| Reddit | Full inventory | All pixels in the account |
| Spotify | Full inventory | One pixel per measurement dataset in the ad account |
| Google Ads | Seller managed | Conversion actions, all managed by the platform — visible but not created, modified, or deleted through Scope3 |
| Amazon Ads | Seller managed | A single built-in entry for Amazon Attribution; Amazon has no external conversion API |
| Pinterest | Synthesized | A single tag entry derived from the account id — not a read of the account's tag inventory |
| LinkedIn | Synthesized | A single tag entry derived from the account id — not a read of the account's tag inventory |
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.
## Related
How account access is granted and what write access means
Organization vs advertiser accounts and how discovered accounts map to advertisers