Connect Meta Ads, Google Ads and Analytics

Connect accounts once per workspace under Settings → Integrations. Idun Blue owns the provider apps; you do not create or paste your own API keys.

The connection is read-only. Idun can read results and show them beside traffic and real Idun purchases, but it cannot create ads, change budgets, or publish campaigns.

Before you start

Sign in as a person who:

• is an owner or administrator in the Idun workspace,
• has access to the correct Meta or Google ad account,
• and, for Analytics, has access to the correct GA4 property.

An agency login or Google Ads manager account is fine. After sign-in, choose the client account this workspace should read.

Connect Meta Ads

1. Go to Settings → Integrations.
2. Under Meta Ads, choose Connect account.
3. Sign in at Meta and approve read access.
4. Back in Studio, choose the Meta ad account.
5. Open Statistics, the Marketing tab, and check that the source is current.

The password is entered at Meta and never shared with Idun. Idun stores the granted access token encrypted and scoped to the workspace.

Connect Google Ads and Google Analytics

Google uses one shared connection flow:

1. Under Google Ads & Analytics, choose Connect account.
2. Sign in at Google and approve read access for Google Ads and Analytics.
3. Choose a regular Google Ads account. A manager account is only the route to its client accounts and cannot be selected as a reporting source.
4. Choose a Google Analytics property.
5. Open Statistics, the Marketing tab, and check spend and traffic.

You can use Analytics on its own even if Google Ads access is not yet active for Idun.

One connection per workspace

Every workspace has its own encrypted tokens, discovered accounts, and selected data sources. Connecting Meta in a client workspace does not affect another client, a personal account, or another company.

The same person can work across several workspaces, but opens each workspace and connects its accounts separately. Never move a client’s ad account into another workspace just to reuse a connection.

What the numbers mean

Under Statistics, in the Marketing tab, three different sources of truth sit side by side:

• Meta/Google Ads reports spend, clicks, and the platform’s own conversions.
• Google Analytics reports website traffic and events.
• Idun reports settled orders and net revenue in Idun.

A UTM source shows how an order was tagged. It does not, by itself, prove that an ad caused the purchase. Idun therefore keeps platform attribution and Idun order data separate and calculates a combined ROAS only when currency and coverage are genuinely comparable.

Idun AI, MCP and API

You can ask Idun AI to check connection status or prepare the right handoff link. A human must always complete provider sign-in and consent at Meta or Google.

MCP provides dedicated tools to check status, start OAuth, select an exact account id supplied by you, and disconnect after confirmation. Raw Meta accounts and campaigns are not sent to external AI models.

The direct API lives under /api/marketing: status, OAuth start, account selection, disconnect, and the combined overview. Tokens are never returned by the API.

If it does not work

• Connect account is disabled: Idun Blue’s platform app is not configured yet. This cannot be fixed by pasting personal keys.
• No accounts found: check that the signed-in person has provider access.
• Needs attention: access expired or was revoked. Choose Reconnect.
• Google Ads is missing but Analytics works: Google Ads developer access is inactive, or the Google account has no ad accounts.
• Wrong account selected: choose another item. This only changes the data source Idun reads.

Disconnect

Choose Disconnect and confirm. Idun removes the saved grant, discovered accounts, and cached reports for that provider. Nothing is deleted at Meta or Google.