Skip to main content

​
Scope is a hard boundary

Concord only reads and acts on the advertisers and accounts an admin has put in scope. Anything out of scope is invisible: its campaigns cannot be read or edited, even when the platform connection itself is healthy. That boundary is enforced below the agent, not by asking it nicely. See Managing scope.

​
When synchronization happens

On connection — Concord discovers the accounts your credentials expose, so you can choose what to put in scope. On scope change — the advertisers you activate are synchronized, along with their campaigns. Overnight — a nightly pass refreshes scope and synchronizes live campaigns, along with campaigns that ended in the last few days. Paused campaigns are not part of the nightly pass; ask Concord to resync one when you need it. On demand — ask Concord to resynchronize an advertiser or a campaign and it will.

​
Why the platform and Concord can disagree for a while

A change you made by hand in the platform appears in Concord after the next synchronization of that object. Ask Concord to resync it and it will be picked up. Yesterday’s numbers keep moving. Advertising platforms restate delivery data after the fact — Google DV360 revises up to three days back. Concord always returns the freshest figures the platform will give it, which means a report run today and the same report run tomorrow can legitimately differ. Historical depth varies by platform. Each platform exposes a different history window and a different set of objects. Snapchat structures, for example, are backfilled only for entities updated on or after 1 January 2026; after that, a refresh imports only the most recent campaigns.
If something looks stale, say so in the conversation: “resync this campaign from the platform.” It is faster than hunting for a refresh button.