Skip to main content
GET
List account presences
Deprecated. This page documents the v2 buyer API, which is closed to new API clients and switches off on 1 December 2026. Use V3 instead: see Move a v2 buyer REST integration to V3. The conversion endpoint, Log event, stays open.
This operation is read-only.
Returns the presence edges the platform has recorded for one connected account: audiences and event sources the seller reports (tracked), plus any buyer-level audiences or event sources already delivered to that account through AdCP pass-through (pushed). This is a reference-only surface — identity, names, sync status, counts and health — never member lists or event payloads. See Presences: audiences and event sources for the tracked/pushed model. The platform reads the account’s audiences and event sources from the seller about once an hour for an account with tracked campaigns, so a new object can take up to an hour to appear. Named operation: list_storefront_connection_account_presences

Request

Parameters

Response

Every row carries direction:
  • tracked — an upstream-discovered object. There is no buyer-level master yet; audienceId/eventSourceId are omitted entirely until the object is explicitly adopted.
  • pushed — a buyer-level object already delivered to this account through AdCP pass-through. The matching master id (audienceId for objectType: "audience", eventSourceId for objectType: "event_source") is always present.
managedBy says who manages an event source, as the seller reports it:
  • buyer — a destination you or your tags set up on the account, such as a pixel or dataset.
  • seller — a source the platform owns, such as its own on-site or in-app events. It is listed so you can see it, but it can never be mapped to one of your event sources.
managedBy is null for audiences, and for an event source whose seller did not say. name is the seller’s name for the object. sellerReport is what the seller reported about it in the same read, in AdCP’s own shape (snake_case fields):
  • Event sources: event_types (the AdCP event types it records; absent when it declares none, so it receives every type), action_source, and health, the seller’s AdCP EventSourceHealth for it. A pixel that is set up but has received nothing yet reads that way in health.
  • Audiences: status, matched_count, effective_match_rate, and match_breakdown (matches by identifier type), as the seller reports them. Many platforms report size as an approximation and some report no match rate at all, so a field the seller did not send is absent.
name and sellerReport are null until the account’s next read, or when the seller reported nothing. mappedTo lists your event sources and audiences mapped to the object on this account, each with its advertiser, its id, its name, and the status of its sync to the account (see Event sources). An empty list means the object is only on this storefront, which needs no action. Several of your objects can map to one seller object, such as one Meta dataset that receives both purchases and leads. mappedTo lists at most 10 of them; mappedToTotal counts them all. rowCount and lastSyncedAt reflect the last successful sync only; the platform never stores the members or events themselves (custody is a separate, explicitly consented capability — see Presences: audiences and event sources). retiredAt is null unless the upstream provider reported a terminal status (deleted, suspended, failed) for the object; pass includeRetired=true to see retired edges. total is the count across all pages. Results use offset pagination (take / skip); see Pagination.

Errors

  • 404 NOT_FOUND — the connection/account does not belong to this customer, or does not exist.
See Errors for the full error contract.

Campaigns on connected provider accounts

Connected provider account presences live on

Ad platform accounts

Connecting and mapping provider accounts

Pagination

Offset-based list paging