Connect
OAUTH1 with encrypted credential storage and explicit external approval requirements.
ads integration
X Ads, with the activation boundary visible.
X Ads uses OAuth 1.0a and requires separately approved Ads API access and an eligible commercial access tier.
Lifecycle
A consistent operating path
Select and validate
Discover permitted advertising accounts, select one, validate permission health, and surface reconnect state.
Sync or ingest
Use the production CSV/API contract now; activate provider-native access only after the required approval.
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
Requires an approved provider SDK or commercial access path.
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