How to Audit Your Current Attribution Setup in 30 Minutes

Most Attribution Setups Are Broken (And Nobody Checks)

Here's a statistic that should worry every media buyer: a 2025 audit by Trackonomics found that 67% of advertisers had at least one significant tracking error -- duplicate conversion events, missing pixels on key pages, misconfigured attribution windows, or broken server-side connections.

These aren't obscure edge cases. These are fundamental errors that inflate or deflate reported conversions by 15-40%, leading to budget decisions based on wrong data.

The fix isn't complicated. It's a systematic 30-minute audit that most media buyers never do because they assume their tracking "just works." It rarely does.

Here's the audit, broken into six checkpoints. Block 30 minutes, open your ad accounts and analytics tools, and work through each one.

Checkpoint 1: Pixel Installation Verification (5 Minutes)

What to Check

Open your website and use platform-specific debugging tools to verify pixel installation on every page that matters.

For Meta:

1. Install the Meta Pixel Helper Chrome extension
2. Visit your homepage, product pages, cart page, checkout page, and thank you page
3. Verify the pixel fires on each page with the correct event

For Google:

1. Use Google Tag Assistant or the Tag Assistant browser extension
2. Visit the same page sequence
3. Verify the Google tag fires correctly on each page

For TikTok:

1. Use TikTok Pixel Helper
2. Same page sequence

Common Issues Found

• Missing pixel on checkout pages: Some checkout platforms (Shopify checkout, headless commerce) don't automatically include tracking pixels. If your pixel isn't on the checkout confirmation page, you're missing conversions.
• Duplicate pixels: Two instances of the same pixel firing on one page doubles your reported conversion events. This is more common than you'd think, especially after website migrations or theme changes.
• Wrong pixel ID: After changing ad accounts or creating new pixels, old pixels sometimes remain on the site alongside new ones, sending data to the wrong account.

Quick Fix

If pixels are missing from key pages, add them immediately through your tag management system (Google Tag Manager, or direct code insertion). If duplicates exist, remove the extra instance. This alone can fix a 10-30% reporting error.

Checkpoint 2: Conversion Event Configuration (5 Minutes)

What to Check

Log into each ad platform and review your configured conversion events.

In Meta Events Manager:

• Navigate to the Events tab
• Check which events are active (PageView, ViewContent, AddToCart, InitiateCheckout, Purchase)
• Verify the Purchase event includes revenue value and currency
• Check for duplicate events (two Purchase events firing on the same page)

In Google Ads:

• Go to Tools & Settings > Conversions
• Review each conversion action
• Check the counting method (One vs. Every -- use "One" for purchases, "Every" for lead forms where multiple submissions matter)
• Verify the conversion value is being passed correctly

Common Issues Found

• Purchase events without value: The conversion fires but doesn't pass the revenue amount. Your conversion count is right but you can't calculate ROAS.
• Currency mismatch: Revenue is passed in one currency but the ad account is set to another, causing ROAS calculations to be wrong by the exchange rate.
• "Every" counting for purchases: If counting is set to "Every," a user refreshing the thank-you page or visiting it multiple times counts multiple conversions for one purchase.

Checkpoint 3: Attribution Window Audit (3 Minutes)

What to Check

Document the attribution window settings for every platform you're running.

Meta Ads Manager: Go to the Columns dropdown > Customize Columns > Attribution Window. Note whether you're viewing 1-day click, 7-day click, or both.

Google Ads: Go to Tools & Settings > Conversions > Settings for each conversion action. Note the click-through conversion window and view-through conversion window.

TikTok: Go to Assets > Events > Event details. Check the attribution window setting.

What You're Looking For

| Platform | Your Click Window | Your View Window | |----------|------------------|-----------------| | Meta | _____ days | _____ day(s) | | Google | _____ days | _____ day(s) | | TikTok | _____ days | _____ day(s) |

If these windows are inconsistent across platforms (e.g., 7-day click on Meta, 30-day click on Google), you're comparing channels on unequal terms. Google will always look better because it has 23 extra days to claim conversions.

Fix: Standardize click windows across all platforms. 7-day click is a reasonable default for most ecommerce brands.

Checkpoint 4: Server-Side Tracking Verification (5 Minutes)

What to Check

If you've implemented Conversions API (CAPI) for Meta or Enhanced Conversions for Google, verify they're working.

For Meta CAPI:

1. Go to Events Manager > Data Sources > Your Pixel
2. Click the "Overview" tab
3. Look for server events appearing alongside browser events
4. Check the Event Match Quality score (should be 6.0 or higher on a 10-point scale)
5. Verify deduplication is working -- server and browser events for the same conversion should be merged, not double-counted

For Google Enhanced Conversions:

1. Go to Tools & Settings > Conversions
2. Click on your primary conversion action
3. Check if Enhanced Conversions is enabled and showing a healthy match rate

Common Issues Found

• CAPI events not deduplicating with pixel events: If event IDs don't match between browser and server events, both count, doubling your conversions. This is the single most common CAPI implementation error.
• Low Event Match Quality: A score below 5.0 means Meta can't match most of your server events to users. Usually caused by not passing enough hashed identifiers (email, phone, name).
• CAPI configured but not sending: The integration was set up but broken by a website update, and nobody noticed because pixel events still appeared to work.

Checkpoint 5: Cross-Platform Conversion Count (5 Minutes)

What to Check

Pull conversion counts from the last 30 days across all platforms and compare against your source of truth.

| Source | Conversions (Last 30 Days) | |--------|---------------------------| | Meta Ads (click + view) | _____ | | Google Ads | _____ | | TikTok Ads | _____ | | Other platforms | _____ | | Platform Total | _____ | | Actual orders (Shopify/CRM) | _____ | | Over-count % | _____ |

Calculate: (Platform Total - Actual Orders) / Actual Orders x 100

If over-count is:

• 0-20%: Reasonable. Some double-counting is expected.
• 20-50%: Moderate inflation. Platform-reported ROAS is significantly overstated.
• 50%+: Severe. Your budget decisions are based on fundamentally wrong data.

Checkpoint 6: UTM Tagging Consistency (7 Minutes)

What to Check

Pull a sample of 10 ad URLs from each platform and check UTM parameters.

Every ad URL should have at minimum:

• utm_source (facebook, google, tiktok)
• utm_medium (cpc, paid-social, display)
• utm_campaign (campaign name, consistent naming convention)
• utm_content (ad creative identifier)

Common Issues Found

• Missing UTMs entirely: Some ads have no UTM tags, making their traffic appear as "direct" or "referral" in analytics.
• Inconsistent naming: "Facebook" vs "facebook" vs "fb" vs "meta" in utm_source creates multiple entries in analytics for the same platform.
• Auto-tagged URLs conflicting with manual UTMs: Google Ads auto-tagging (gclid) can conflict with manual UTM parameters in Google Analytics, causing attribution discrepancies.

Fix: Create a UTM naming convention document. Use lowercase consistently. Use a URL builder tool to prevent typos.

Your Audit Summary

After completing all six checkpoints, you should have:

1. Confirmed pixels are installed correctly on all key pages
2. Verified conversion events are configured with correct values and counting
3. Documented attribution windows and identified inconsistencies
4. Verified server-side tracking is working and deduplicating properly
5. Quantified the gap between platform-reported and actual conversions
6. Identified UTM tagging gaps

Address the issues in order of impact. Deduplication errors and missing conversion values tend to cause the largest reporting distortions. Fix those first, then standardize windows and UTMs.

Frequently Asked Questions

How often should I audit my attribution setup?

At minimum, quarterly. Additionally, run the audit after any website migration, checkout flow change, tag manager update, or new ad platform launch. These events are the most common causes of tracking breaks. Set a calendar reminder for a monthly spot-check of Checkpoint 5 (cross-platform conversion count comparison) -- it takes 5 minutes and catches problems early before they compound into months of bad data.

What's the most common attribution error you see?

CAPI deduplication failures. Advertisers implement Meta's Conversions API alongside the pixel but don't configure matching event IDs, so the same conversion is counted twice -- once by the pixel and once by the server event. This inflates Meta's reported conversions by up to 100% and makes Meta look twice as effective as it actually is. Check your Events Manager for a "deduplicated" indicator on server events. If it's not showing deduplication, your event IDs don't match.

Can I automate attribution auditing?

Partially. You can set up automated alerts for tracking breakages -- tools like Google Tag Manager's built-in debugging, Meta's Diagnostics tab in Events Manager, and Google Analytics real-time reports all provide monitoring capabilities. For the cross-platform conversion comparison (Checkpoint 5), you can build an automated dashboard that pulls platform data and compares against your ecommerce platform data daily. The full audit still requires manual inspection, but automated monitoring catches the most urgent issues between audits.

---

Go Funnel uses server-side tracking and multi-touch attribution to show you which ads actually drive revenue. Book a call to see your real numbers.