How to Set Up Triple Whale for Meta Ads
I see Triple Whale setups that are completely missing Meta attribution data in about 30% of the e-commerce accounts I audit. The most common issue? The Triple Whale pixel is firing, but it’s not capturing the Meta click IDs properly, so all your Meta traffic shows up as “Direct” in Triple Whale’s attribution reports.
What You’ll Have Working By The End
- Triple Whale pixel properly installed and capturing Meta click IDs (fbclid)
- Meta Ads integration connected and pulling campaign data
- URL parameter passthrough configured for UTM tracking
- Attribution comparison between Triple Whale and Meta Ads Manager with expected variance ranges
- Custom attribution windows set up to match your business model
Prerequisites
- Triple Whale account with admin access
- Meta Ads Manager account with advertiser-level permissions
- Shopify admin access (or developer access to your e-commerce platform)
- Facebook Business Manager admin access
- Google Analytics 4 connected to Triple Whale (recommended for cross-validation)
Step 1: Install the Triple Whale Pixel
Triple Whale’s pixel needs to be on every page to capture the full customer journey. If you’re on Shopify, this is straightforward. For other platforms, you’ll need to manually install the script.
Shopify Installation
- In Triple Whale, go to Settings → Integrations → Shopify
- Click Connect Shopify Store
- Enter your Shopify domain and authorize the connection
- Triple Whale automatically installs their pixel via the Shopify Scripts API
Manual Installation (Non-Shopify)
Add this script to your site’s <head> tag on every page:
<!-- Triple Whale Pixel -->
<script>
!function(t,r,i,p,l,e,W,h,a,l,e){
t[e]=t[e]||function(){(t[e].q=t[e].q||[]).push(arguments)},
t[e].l=1*new Date();W=r.createElement(i),h=r.getElementsByTagName(i)[0];
W.async=1;W.src=p;h.parentNode.insertBefore(W,h)
}(window,document,'script','https://pixel.triplewhale.com/pixel/YOUR_PIXEL_ID/tw.js','tw');
tw('init', 'YOUR_PIXEL_ID');
tw('track', 'PageView');
</script>
Replace YOUR_PIXEL_ID with your actual pixel ID from Triple Whale’s Settings → Pixel section.
For e-commerce events, add these to your relevant pages:
// Purchase Event (Thank You Page)
tw('track', 'Purchase', {
'content_ids': ['product_id_1', 'product_id_2'],
'content_type': 'product',
'currency': 'USD',
'value': 99.99,
'order_id': 'ORDER_12345'
});
// Add to Cart Event
tw('track', 'AddToCart', {
'content_ids': ['product_id'],
'content_type': 'product',
'currency': 'USD',
'value': 29.99
});
Step 2: Connect Meta Ads Integration
This is where most setups break. Triple Whale needs direct access to your Meta Ads account to pull campaign data and match it with pixel data.
- In Triple Whale, go to Settings → Integrations → Facebook Ads
- Click Connect Facebook Ads Account
- Log in with the Facebook account that has admin access to your ad account
- Select the correct ad account (not your personal account)
- Grant all permissions — Triple Whale needs read access to campaigns, ad sets, ads, and insights
Critical: Make sure you’re connecting the same ad account that’s running your ads. I’ve seen setups where they connected a testing account or the wrong business manager account.
In the integration settings, configure:
- Attribution Window: Set to 7-day click, 1-day view (matches Meta’s default)
- Currency: Match your store currency
- Time Zone: Match your ad account time zone
Step 3: Configure URL Parameter Passthrough
Triple Whale needs to capture Meta’s click ID (fbclid) and your UTM parameters to properly attribute traffic. This happens automatically with their pixel, but you need to verify it’s working.
UTM Parameter Setup
Make sure all your Meta ads include these UTM parameters:
?utm_source=facebook
&utm_medium=paid-social
&utm_campaign={{campaign.name}}
&utm_content={{adset.name}}
&utm_term={{ad.name}}
Meta Click ID Capture
Triple Whale automatically captures the fbclid parameter that Meta appends to your URLs. You can verify this is happening by checking the Attribution → Traffic Sources report in Triple Whale.
If you’re running ads to landing pages that redirect to your main domain, make sure the redirect preserves the fbclid parameter:
// Example redirect that preserves fbclid
function preserveClickId() {
const urlParams = new URLSearchParams(window.location.search);
const fbclid = urlParams.get('fbclid');
if (fbclid) {
const redirectUrl = 'https://yourdomain.com/target-page?fbclid=' + fbclid;
window.location.href = redirectUrl;
}
}
Step 4: Set Up Custom Attribution Windows
Triple Whale’s default attribution doesn’t always match your customer journey. I typically see e-commerce brands need longer attribution windows.
- Go to Settings → Attribution
- Set your attribution windows:
- First Touch: 30 days (captures early research phase)
- Last Touch: 7 days (captures final decision)
- Multi-Touch: Linear 14 days (spreads credit across touchpoints)
For most e-commerce brands, I recommend:
- High AOV products (>$200): 30-day click, 7-day view
- Low AOV products (<$50): 7-day click, 1-day view
- Fashion/Seasonal: 14-day click, 3-day view
Step 5: Configure Cross-Platform Attribution
Triple Whale’s strength is combining data from multiple sources. Set up these additional integrations for complete attribution:
Google Analytics 4 Connection
- Settings → Integrations → Google Analytics 4
- Connect using your GA4 measurement ID
- Enable Enhanced E-commerce data import
Email Platform Integration
Connect your email platform (Klaviyo, Mailchimp, etc.) to capture email attribution:
- Settings → Integrations → [Your Email Platform]
- Enable Campaign Attribution to see email assist on Meta-attributed conversions
Testing & Verification
Here’s how to verify everything is working correctly:
1. Pixel Firing Test
- Visit your website with Meta ads preview tool or Facebook Pixel Helper
- Verify the Triple Whale pixel fires on page load
- Check that purchase events fire on your thank you page
- Look for the
fbclidparameter in the pixel data
2. Attribution Data Check
In Triple Whale’s Attribution dashboard:
- Meta traffic should appear as “Facebook” not “Direct”
- Campaign names should match your Meta Ads Manager exactly
- Purchase attribution should show within 24-48 hours of test purchases
3. Revenue Cross-Check
Compare Triple Whale attribution to Meta Ads Manager:
- 7-day period comparison (avoid daily due to attribution delays)
- Conversion value should be within 15-25% variance
- Meta will typically report higher due to view-through attribution
- Triple Whale may report higher if capturing organic assists
Acceptable variance ranges:
- Purchase count: 5-15% difference
- Revenue: 10-25% difference
- ROAS: 15-30% difference (due to different attribution models)
4. UTM Parameter Verification
Check that UTM parameters are captured:
- Run a test ad with UTM parameters
- Click through to your site
- Complete a purchase
- Verify the purchase shows correct campaign attribution in Triple Whale
Troubleshooting
Problem: Meta traffic showing as “Direct” in Triple Whale Check if the fbclid parameter is being stripped by:
- Ad blockers (affects 15-25% of users)
- Redirect scripts that don’t preserve parameters
- HTTPS/HTTP protocol mismatches Solution: Implement server-side click ID preservation and ensure redirects maintain URL parameters.
Problem: Purchase events not attributing to Meta campaigns This happens when the pixel fires but can’t match the fbclid to the original click:
- Check if users are clearing cookies between click and purchase
- Verify the attribution window isn’t too short for your customer journey
- Make sure the pixel is on the thank you page, not just order confirmation emails Solution: Extend attribution windows and implement server-side conversion tracking via Meta Conversions API.
Problem: Revenue numbers don’t match between Triple Whale and Meta Expected discrepancies:
- Meta counts view-through conversions (Triple Whale defaults to click-only)
- Different attribution windows (Meta: 7-day click/1-day view vs. Triple Whale custom windows)
- Triple Whale includes organic assists that Meta doesn’t see Solution: Align attribution windows and understand that 15-25% variance is normal.
Problem: Campaign data not importing from Meta Usually an API permissions issue:
- Reconnect the Facebook Ads integration with full permissions
- Make sure you’re using a Facebook account with admin access to the ad account
- Check if your ad account was recently restructured (breaks API connections) Solution: Revoke and reconnect the integration with proper admin permissions.
Problem: Attribution delays longer than 48 hours Triple Whale processes attribution data in batches, but delays beyond 48 hours indicate:
- API rate limiting from Meta
- Data pipeline issues on Triple Whale’s side
- Time zone mismatches between platforms Solution: Check integration status and contact Triple Whale support if delays persist beyond 72 hours.
Problem: Duplicate conversion counting This happens when both Meta Pixel and Triple Whale pixel fire purchase events:
- Meta receives conversions from both its pixel and Triple Whale’s data
- Results in inflated conversion counts in Meta Ads Manager
- Most common with Shopify apps that auto-install multiple pixels Solution: Use Meta’s Conversions API via Triple Whale and turn off redundant direct Meta Pixel events.
What To Do Next
Triple Whale works best as part of a complete attribution stack. Here are the logical next steps:
- Set up server-side tracking to capture blocked traffic that Triple Whale’s client-side pixel misses
- Configure Google Ads attribution to see cross-platform customer journeys
- Implement enhanced e-commerce tracking for product-level attribution insights
- Get a free tracking audit — I’ll review your Triple Whale setup and identify attribution gaps you’re missing
This guide is part of the Attribution Setup Hub — complete guides for connecting every attribution tool with every major ad platform.