Skip to main content
Microsoft Ads (Beta), OpenAI Ads (Beta), and Triple Whale (Beta) are available in the Integrations directory. Their setup and reporting surfaces can evolve faster than core integrations.
Validate Beta data against the provider before a material decision. Always name the Beta source, account, currency, attribution context, and completed date range.

Microsoft Ads (Beta)

Microsoft Ads (Beta) contributes read-only Microsoft Advertising spend and performance from explicitly selected accounts.

Connect Microsoft Ads (Beta)

  1. Open Integrations → Microsoft Ads (Beta).
  2. Choose Connect with Microsoft or Connect with Google, depending on the identity that reaches Microsoft Advertising.
  3. Complete provider authorization.
  4. In Choose the accounts to sync, select up to 25 accounts.
  5. Select Sync selected accounts. Even a single accessible account must be selected explicitly.
  6. Verify Authorized by, Accounts selected, and Connected.

Microsoft Ads (Beta) states

Sync can show Syncing, Syncing history, All synced, Last sync didn’t finish - Resync to retry, or Not synced yet. Use Resync or Retry sync only after authorization and selection are healthy. Microsoft Ads (Beta) is read-only. Selection is workspace-specific, and only the selected accounts enter reporting.

OpenAI Ads (Beta)

OpenAI Ads (Beta) uses API keys to connect one or more OpenAI Ads (Beta) accounts. Each account can use a separate key.

Connect OpenAI Ads (Beta)

  1. Open Integrations → OpenAI Ads (Beta).
  2. In OpenAI Ads (Beta), go to ads.openai.com → Settings → API Keys → Generate new key.
  3. Paste the value into API key and select Connect.
  4. If the source and workspace currencies differ, review Review currency mismatch and select Connect anyway only when conversion into the workspace currency is intended.
  5. Verify Connected accounts, Primary ad account or Ad account, Account ID, Currency, Timezone, masked API key, and Connected.
Paste an OpenAI Ads (Beta) key only into the integration’s API key field. Never place it in chat, Slack, documentation, or a support screenshot.

Multiple-account and replacement states

The page can show:
  • Connected · N accounts when every saved account is healthy.
  • Connected · N active · N need a key when healthy and rejected credentials coexist.
  • Replace API key or Replace API keys for affected accounts.
  • API key rejected · reconnect required when OpenAI Ads (Beta) rejects a saved key.
Replacing one key preserves the last-known account roster until validation succeeds. Healthy sibling accounts continue syncing. On a reconnect currency warning, use Reconnect anyway only after confirming the intended reporting currency. Use Resync after healthy keys and account identities are confirmed. Disconnect only the account or connection that should stop contributing.

Triple Whale (Beta)

Triple Whale (Beta) adds pixel-attribution reporting while keeping platform-reported Meta and Google performance separate.

Connect Triple Whale (Beta)

  1. Create or select a Triple Whale (Beta) API key with Pixel Attribution scope.
  2. Open Integrations → Triple Whale (Beta).
  3. Enter API key and, when needed, Shop domain (optional). Marketer can prefill the domain from Shopify context.
  4. Record the optional Filter context: Attribution window, Accounting mode, and Subscription filter.
  5. Connect and verify Shop domain, Account, Currency, masked API key, Attribution model, filter context, and Connected.
The filter context documents how to interpret imported numbers; it does not change them. Use Save filter context after editing it.

Triple Whale (Beta) states and recovery

Sync can show Syncing, Data ready · syncing past windows, All synced, Last sync didn’t finish - Sync to retry, or Not synced yet. Use Sync after the key is healthy. Do not treat Triple Whale (Beta) attribution as interchangeable with Meta Ads or Google Ads totals. Keep the recorded filter context with any comparison.

Beta verification checklist

  • Beta label included in the result
  • Correct workspace and provider account
  • Authorization or key health confirmed
  • Selected roster confirmed
  • Source and workspace currencies recorded
  • Attribution or filter context recorded
  • Last sync and completed coverage recorded
  • Provider comparison completed

Next step

Run one narrow, read-only source comparison. Save the account, date range, currency, Beta label, and interpretation so another reviewer can reproduce it.
Last modified on August 9, 2026