Ad Accounts

Manage the ad accounts Adlyse is connected to. Every connected account produces a daily dashboard snapshot, feeds the Explorer and Reports, and is a valid target for the MCP write tools.

Connecting an account#

Click Connect on the Ad Accounts page and choose the platform. Each platform uses OAuth with scopes that allow read access to metrics and, where supported, write access for mutations (pause / resume / budget). Adlyse only writes when explicitly asked — either through the UI, the in-app assistant, or an MCP write tool with preview=false.

Google Ads — pick one or more customer IDs after sign-in. If the signed-in user is part of an MCC (manager account), Adlyse discovers the child accounts automatically.
Meta Ads — OAuth through a Facebook account that has Business Integration System User access. Adlyse prefers a long-lived System User access token when available and falls back to the user token otherwise.
TikTok Ads — read-only sync supported; mutations are on the roadmap.

What Adlyse syncs#

Per account, each sync run pulls:

Campaigns, ad sets (Google: ad groups), and ads with their current configuration
Daily metrics for the last 30 days: spend, impressions, clicks, conversions, conversion value, plus derived CTR / CPC / CPA / ROAS
Change events — edits, budget changes, creative swaps, status flips — detected from the platform’s native change history where available, and from a snapshot-diff when not (Meta)
Search terms (Google only) for the Search Terms view
Creatives (Meta only) with media URLs for the creative-audit workflows

Everything is stored in a platform-normalized data table, so the same MCP tool returns the same shape regardless of which network the row came from.

Sync status#

Each account has a sync indicator: pending (first sync queued), syncing, success (with timestamp), or error (with the platform’s error message). Syncs run automatically on a schedule; you can also trigger an immediate sync from the ”…” menu.

If an account shows error, check:

OAuth credentials — the linked account may have revoked consent or the token may have expired. Click Reconnect to re-run the OAuth flow.
Permissions — the OAuth user must still have access to the ad account on the platform side.
Rate limits — platform rate limits occasionally surface as errors. They usually resolve themselves within the hour.

Disconnecting#

Disconnecting an account stops future syncs. Historical data, snapshots, and decision-log entries are preserved. You can reconnect later; Adlyse matches on the platform’s external account id and resumes syncing forward.

Deleting an account (soft-delete) hides it from the UI but also preserves historical data, so the org-level aggregate snapshot can continue to include it if you undelete.

From MCP#

adlyse-insights.list_ad_accounts — connection + sync status for every account.
adlyse-ads — cross-platform reads and gated writes scoped to an ad_account_id.

Connecting an account#

Google Ads — pick one or more customer IDs after sign-in. If the signed-in user is part of an MCC (manager account), Adlyse discovers the child accounts automatically.

Meta Ads — OAuth through a Facebook account that has Business Integration System User access. Adlyse prefers a long-lived System User access token when available and falls back to the user token otherwise.

TikTok Ads — read-only sync supported; mutations are on the roadmap.

What Adlyse syncs#

Per account, each sync run pulls:

Campaigns, ad sets (Google: ad groups), and ads with their current configuration

Daily metrics for the last 30 days: spend, impressions, clicks, conversions, conversion value, plus derived CTR / CPC / CPA / ROAS

Change events — edits, budget changes, creative swaps, status flips — detected from the platform’s native change history where available, and from a snapshot-diff when not (Meta)

Search terms (Google only) for the Search Terms view

Creatives (Meta only) with media URLs for the creative-audit workflows

Everything is stored in a platform-normalized data table, so the same MCP tool returns the same shape regardless of which network the row came from.

Sync status#

If an account shows error, check:

OAuth credentials — the linked account may have revoked consent or the token may have expired. Click Reconnect to re-run the OAuth flow.

Permissions — the OAuth user must still have access to the ad account on the platform side.

Rate limits — platform rate limits occasionally surface as errors. They usually resolve themselves within the hour.

Disconnecting#

Deleting an account (soft-delete) hides it from the UI but also preserves historical data, so the org-level aggregate snapshot can continue to include it if you undelete.