Loading tutorials…
Loading tutorials…
These two integrations are where 60% of Triple Whale value lives. Done wrong, you get partial spend data and broken attribution. Done right, you have one number for blended ROAS that you can actually trust.
Who this is forShopify owners on Triple Whale running Meta Ads and/or Google Ads. Especially urgent if you have a Business Manager with multiple ad accounts, or if your Google Ads sits under an MCC (manager account).
What you'll need
Step 1
Before clicking "Connect" in Triple Whale, confirm you have Business Manager Admin OR full Advertiser + Pixels: Manage. Without it, the integration will look successful but Sonar CAPI will fail later.
Open business.facebook.com → Business settings → Users → People.
Find your user. Click your name. Verify "Admin access" is enabled for the Business Manager OR — at minimum — "Advertiser" on the ad account(s) + "Manage" on the Pixel(s).
If you only have "Standard access" or "Advertiser" without Pixel: Manage, request an upgrade from the BM Admin before continuing. The Triple Whale OAuth flow will technically succeed without these scopes but Sonar to Meta CAPI will silently fail and you'll lose 30-50% of attribution lift.
If the BM is owned by an agency, message the agency now requesting Pixels: Manage access for your user. This often takes 2-5 business days.
If you don't have a Business Manager yet (you're running ads from a personal ad account), STOP. Migrate to a Business Manager first — Triple Whale's integration doesn't fully work with personal ad accounts.
Step 2
Triple Whale → Settings → Integrations → Meta Ads → Connect. Authenticate with the Facebook user that has full BM access.
In Triple Whale, Settings → Integrations → Meta Ads → click "Connect."
A Facebook OAuth popup opens. Log in as the user with full BM access (NOT a personal Facebook you only use for social).
On the permissions screen, KEEP ALL DEFAULT PERMISSIONS CHECKED. The most commonly mis-unchecked ones: "Manage your business," "Read insights," "Read your pages." All of these are required.
On the "Choose what you allow" screen, select ALL ad accounts you want Triple Whale to read. If you have inactive ad accounts you don't need, exclude them — but include all active ones.
Click "Done." The integration page should show your ad accounts listed under "Connected accounts."
Triple Whale will pull the last 90 days of spend, impressions, clicks, and Meta-side conversions. This takes 30-90 minutes depending on account size.
Step 3
Sonar to Meta CAPI sends Triple Whale's server-side conversion data BACK to Meta — improving Meta's own bidding optimization. This is the highest-leverage Meta integration setting.
In Triple Whale → Settings → Integrations → Meta → "Sonar to Meta CAPI" section.
Click "Enable Sonar to Meta CAPI."
Select which Pixel(s) Triple Whale should send conversions to. Pick the same Pixel(s) you use for Meta Ads campaigns.
Triple Whale will start firing server-side purchase events to Meta CAPI alongside Meta's own pixel. This recovers iOS attribution Meta would otherwise miss.
Validate in Meta Events Manager → your Pixel → Overview → "Connections." You should see "Triple Whale" listed as a connected source within 24-48 hours.
Expected impact: Meta's "Event Match Quality" score improves by 1-3 points within 14 days. Meta's reported ROAS often improves 15-30% as it now has more conversion signal.
Step 4
Triple Whale → Settings → Integrations → Google Ads → Connect. If your account sits under a manager account (MCC), connect at the MCC level — not the child account.
In Triple Whale, Settings → Integrations → Google Ads → click "Connect."
Google OAuth popup opens. Sign in with the Google account that owns or manages the Google Ads account.
KEEP ALL DEFAULT PERMISSIONS CHECKED. The Google Ads scope Triple Whale needs is read-only — it won't modify your campaigns.
If you see a "Choose an account" screen with both an MCC (manager account) and child accounts listed, select the MCC. This auto-flows any current AND future child accounts to Triple Whale.
If you don't have an MCC, select the individual account.
The integration page should now show your Google Ads account listed with the last 90 days syncing.
Step 5
Triple Whale needs to know which ad accounts belong to which Shopify store. If you only have one Shopify store, this is automatic. If you have multiple, the mapping matters.
In Triple Whale → Settings → Integrations → "Store Mapping."
For each ad account (Meta and Google), confirm it's mapped to the correct Shopify store.
If you have multiple Shopify stores under one Triple Whale workspace (Scale tier+), be deliberate: spend on the wrong account inflates the wrong store's ROAS.
If you have one Shopify store but multiple ad accounts (e.g., one for US, one for UK), map all relevant accounts to that store.
Save the mapping. Triple Whale recomputes the last 90 days of attribution based on the new mapping (can take 30-60 minutes).
Step 6
After 24 hours, audit: Triple Whale Meta spend should match Meta Ads Manager spend within 1%. Same for Google Ads. If off, the integration is missing accounts.
In Triple Whale → Dashboards → Summary, look at "Meta Ad Spend (Last 7 Days)" and "Google Ad Spend (Last 7 Days)."
Compare to Meta Ads Manager → All campaigns → Last 7 Days spend. Should match within 1-2%.
Compare to Google Ads → Campaigns → Last 7 Days spend. Should match within 1-2%.
If Meta is off by 5%+: usually an unconnected ad account. Settings → Integrations → Meta → check if all active ad accounts appear in "Connected accounts."
If Google is off by 5%+: usually a missing child account under an MCC. Reconnect at the MCC level if you originally connected only the child.
If both match: you're ready to use Triple Whale dashboards confidently. If not, do not trust ROAS numbers until reconciled.
Step 7
Similar to Meta CAPI, Triple Whale can send server-side conversions back to Google Ads to improve Smart Bidding optimization.
In Triple Whale → Settings → Integrations → Google → "Sonar to Google Ads."
Click "Enable Enhanced Conversions for Google Ads."
Select which Google Ads conversion action Triple Whale should enhance. Pick your primary "Purchase" conversion action.
Triple Whale will send hashed customer data (email, phone) alongside the conversion event to improve Google's match rate.
In Google Ads → Goals → Conversions → click your Purchase action → "Diagnostics" tab. Within 7-14 days, "Enhanced Conversions" score should appear with a match rate (target: 50%+).
Expected impact: 5-15% lift in reported Google Ads conversions over 30 days as Google recovers attribution it would otherwise miss.
Common mistakes
Connecting Meta with a personal Facebook account instead of a Business Manager user
What goes wrong: Triple Whale OAuth succeeds, but it only sees the ad accounts your personal user has direct access to. Business Manager-owned accounts are invisible. You think the integration worked when 60% of your spend is missing.
How to avoid: Always authenticate with a user that has Business Manager Admin OR full Advertiser + Pixels: Manage. Re-authenticate if needed.
Unchecking default Meta permissions during OAuth
What goes wrong: Sonar to Meta CAPI fails silently 2-4 weeks later. You don't notice until pixel-attributed revenue stops improving and Meta's Event Match Quality stays low. Costs 15-30% of attribution lift.
How to avoid: Settings → Integrations → Meta → "Reconnect." On the OAuth screen, keep EVERY default permission checked. Don't reduce scopes thinking you're being security-conscious.
Connecting Google Ads at the child account level when an MCC exists
What goes wrong: You connect one child account, then later add a second child account under the same MCC for a new market. Triple Whale doesn't auto-flow it. New spend appears nowhere in Triple Whale until you manually reconnect.
How to avoid: Always connect at the MCC level if you have one. Settings → Integrations → Google → Disconnect → Reconnect → select the MCC instead of the child.
Not enabling Sonar to Meta CAPI
What goes wrong: Meta loses 20-40% of iOS conversion signal because browser pixel events are blocked by Mail Privacy Protection and ATT. Triple Whale catches them server-side but never tells Meta. Meta's bidding optimizes on incomplete data — you waste 15-25% of Meta spend.
How to avoid: Settings → Integrations → Meta → enable Sonar to Meta CAPI. Validate in Meta Events Manager that "Triple Whale" appears as a connected source.
Ignoring spend mismatch between Triple Whale and platform-native dashboards
What goes wrong: Triple Whale reports $4,800 Meta spend; Meta Ads Manager reports $5,300. You don't reconcile and unknowingly read a ROAS that's 10% too high. Every campaign decision based on it is wrong.
How to avoid: Weekly spend reconciliation. Set a recurring 15-minute calendar block. If TW vs platform diverges by more than 2%, find the missing account and fix the integration.
Skipping Enhanced Conversions for Google Ads
What goes wrong: Google's Smart Bidding optimizes without TW's enhanced conversion data. Match rate stays at 20-30% instead of 50-70%. Smart Bidding makes worse decisions and your ROAS plateaus.
How to avoid: Settings → Integrations → Google → Enable Enhanced Conversions. Validate match rate in Google Ads → Goals → Conversions → Diagnostics.
Recap
Done — what's next
How to set up Triple Whale for your Shopify store
Read the next tutorial
Hand it off
These two integrations are where Triple Whale's value compounds. Done right, your blended ROAS becomes a single number you can act on. Done wrong, you're reading partial truth across three dashboards. A vetted DTC attribution specialist can set both up, validate spend match, and configure Sonar CAPI in 4-6 hours — typically $300-500 for the setup, $200-400/mo for ongoing channel reconciliation.
See specialist rates
Meta Ads Manager uses Meta's own last-click attribution with 7-day click + 1-day view default windows. Triple Whale uses the TW Pixel attribution model — typically more conservative. The gap (often 30-50%) reflects Meta's over-attribution, not Triple Whale being wrong. Reconcile by trusting Triple Whale for blended decisions and Meta-native for in-platform optimization.
Yes, but the agency must grant your user Pixels: Manage permission (and ideally Advertiser+ on ad accounts). Have them add you in business.facebook.com → Business settings → Users. They retain ownership; you get the access Triple Whale needs.
If you spend $500+/month on those channels, yes — Triple Whale's Scale tier includes them. Below $500/mo, the integration is overkill and you're better off optimizing within the platform directly.
Historical spend data stays in Triple Whale for the period it was connected. Future spend stops syncing immediately. Attribution for past orders that touched that ad account is preserved.
Technically yes — both pixels can install. Practically, you should pick one as the source of truth or you'll have two dashboards disagreeing about ROAS and slow team decisions. See our Triple Whale vs Northbeam vs Polar decision guide.
Rare but possible: Triple Whale includes returns/refunds differently, or you have duplicate ad accounts mapped. Check Settings → Integrations → Meta → Connected Accounts. Each ad account should appear once.
Triple Whale
Most founders sign up for Triple Whale, click 'Connect Shopify,' and assume the rest will figure itself out. Three weeks later they're paying $200/mo for a dashboard nobody opens because attribution looks weird. Here's the setup that actually delivers value from day one.
Triple Whale
The TW Pixel is the entire reason you're paying for Triple Whale. If it's not firing on every transaction, you're reading the same numbers your platform-native dashboards already showed you — just with a $300/mo wrapper around them.
Triple Whale
Triple Whale's attribution model picker is buried in Settings and most users never touch it. The default is fine for some stores and dangerously wrong for others. Here's the decision framework that drives 80% of the value you get out of the platform.
Triple Whale
If Triple Whale shows different numbers than Shopify, Meta, or Google, every decision you make on Triple Whale data is questionable. Here's the diagnostic sequence specialists run to reconcile the gap.
Meta Ads
The browser pixel alone loses 20-30% of conversions on iOS. CAPI sends events from your server to Meta, recovering most of it. Three install paths: Shopify-native, server-side GTM, and direct API. We cover all three.
Google Ads
Linking these two correctly is what makes Google's whole stack actually function as a stack. Done wrong, you'll have two systems that disagree about reality for years. Here's the right setup.