Troubleshoot integrations

Most integration problems belong to one of four layers: authorization, resource selection, data sync, or interpretation. Start at the top; later layers cannot repair an earlier one.

​

First: preserve uncertain state

Marketer keeps the safe last-known connection summary when a provider status read fails. Use the exact provider message and last successful time in an escalation.

​

The diagnostic order

​

State-to-action matrix

​

Provider-specific checks

​

Meta Ads

• Verify Facebook user and every group under Assets granted.
• Use Finish setup for unresolved selections and Add a Facebook Page only for publishing readiness.
• Check whether Backsyncing is paused. A frozen last-sync time can explain stale reporting while Meta continues running.
• Confirm conversion source and account currency before reconciling totals.

​

Google Ads

• Confirm selected leaf customer IDs under Synced Google Ads accounts.
• If an account shows Access lost, restore provider access or remove it with Manage accounts.
• Use Refresh account access when the current authorization resolves no selectable roster.
• Recommendation auto-apply state is separate from reporting sync.

​

Google Analytics

• Search by property ID if names are ambiguous.
• Use Refresh property access when the Google identity has a grant but no selectable properties appear.
• Compare GA4 attribution with ad-platform attribution before classifying a total mismatch as a sync problem.

​

Shopify

• Reconnect only the affected store.
• Check Include in revenue rollup before investigating blended revenue, ROAS, or MER.
• For older reporting, verify Full order history; without it, orders older than 60 days can be missing.
• Check each store’s source currency.

​

Slack

• Installation and Finish Slack setup are different steps.
• If channel listing reports missing permission, use Reconnect Slack to grant the current scope set.
• If direct messages are not linked, use Open Slack to finish and run /marketer whoami.
• Confirm Post to Slack, the selected Channel, severity floor, and event groups.

​

Beta integrations

• Always retain the Beta label in a result.
• For Microsoft Ads (Beta), select at least one account explicitly; No accounts is a provider-access problem.
• For OpenAI Ads (Beta), replace only rejected account keys; healthy siblings can remain active.
• For Triple Whale (Beta), confirm Pixel Attribution scope and keep the displayed filter context with comparisons.

​

Freshness is not one timestamp

Use all of these signals together:

• connection state;
• selected resource roster;
• sync stage;
• last successful sync;
• historical coverage;
• provider processing or attribution delay; and
• whether the current day is complete.

Data ready · syncing past performance means recent reporting may be usable while older history is still filling. Define the usable date range instead of calling the whole source complete.

​

Before disconnecting

Review what will lose source context:

• blended analytics and comparisons;
• campaign and creative analysis;
• Meta audiences, pixels, catalogs, or publishing readiness;
• Shopify revenue rollups;
• Slack alerts, approvals, and identity links; and
• workflows or agent requests that depend on the provider.

Disconnect only when removal is intended, not as a generic refresh technique.

​

Prepare a useful escalation

Include:

• workspace name and your effective role;
• provider and exact page state;
• selected account, property, store, or asset identifier;
• exact error text;
• last successful sync and requested date range;
• expected versus actual result; and
• a sanitized screenshot.

Never include OAuth codes, reset links, full API keys, passwords, or payment information.

​

Next step

After recovery, rerun the smallest read-only comparison that originally failed. Confirm source, resource, currency, attribution context, and completed coverage before resuming automation.