Connect
OAUTH2 with encrypted credential storage and explicit external approval requirements.
ads integration
Google Ads, with the activation boundary visible.
Use an approved Google Ads developer token and OAuth consent screen; manager-account access may be required.
Lifecycle
A consistent operating path
Select and validate
Discover permitted advertising accounts, select one, validate permission health, and surface reconnect state.
Sync or ingest
Run the direct reporting adapter, or use CSV/API ingestion when the provider app is not activated.
Observe
Inspect source, account, permission status, last sync, errors, and sync history from the integration centre.
Disconnect
Attempt provider revocation, then remove encrypted credentials, connection state, and provider metric rows locally.
Automate
Route real sync, failure, and connection events through signed webhooks or the workflow packs.
Capabilities
Read-only by default
Account discovery
Included in the provider contract.
Reporting
Canonical campaigns and daily insight rows preserve provider identity, currency, source, and provider update time.
No silent mutation
The adapter does not change budgets or campaign state. Any future write requires elevated role, dry run, exact diff, explicit confirmation, idempotency, and audit.
Ready when the data is