Running two analytics tools? You're counting conversions twice
The screen glows pale blue at 6am in a Manchester flat. Three browser tabs open—Google Analytics, Plausible, and a custom event dashboard—each showing a different conversion count for yesterday’s campaign. One operator, three numbers, and a sinking feeling that none of them are right.
Analytics event deduplication: when two tools count the same click twice
Running multiple analytics tools creates phantom conversions that inflate your metrics and break your attribution math.
Install Google Analytics and Plausible on the same page, fire a newsletter sign-up event, and watch both tools log it independently. You meant to collect two views of the same conversion. What you built is a system that counts one user action twice—then reports it as two separate conversions when you’re trying to calculate cost per acquisition.
The problem isn’t the tools. It’s that most operators bind the same event trigger to multiple analytics calls without a deduplication layer. A click fires. Your tag manager sends the event to GA4. Your custom script sends it to Plausible. Your WordPress plugin sends it to your internal dashboard. Three tools, three entries, one human being. When you sum conversions across platforms—or worse, when an attribution model tries to reconcile them—you’re measuring phantom growth that evaporates the moment you audit the raw logs.
The fix isn’t ripping out your stack. It’s understanding which tool should own which event, how to route triggers so each action fires once per platform, and when to treat secondary tools as read-only observers instead of parallel recorders. Most operators discover this after a month of inflated reports and a spreadsheet that refuses to reconcile.
RELATED TACTIC
When your analytics platform records the wrong timestamp
Most analytics tools log the moment the conversion event fired in their system—not the moment the customer clicked, subscribed, or bought. That gap can be seconds or hours, depending on network latency, tag manager delays, and server-side processing queues. When you’re comparing campaigns or building attribution models, that timestamp drift quietly scrambles your sequence of touch-points. You think the social post converted first; the user actually clicked your email link two hours earlier. The tool just logged it last.
READER QUESTION
Why UTM parameters vanish before your analytics sees them
You append ?utm_source and ?utm_campaign to every link. Your click-through rate looks healthy. Your analytics dashboard shows zero attributed traffic. The reason: social platforms, email clients, and link shorteners strip query parameters mid-click to protect user privacy or simplify redirects. By the time the visitor lands on your page, the UTM tags are gone—and your attribution model has nothing to match. This isn’t a misconfiguration. It’s the default behaviour of most platforms operators rely on for distribution.
FROM THE ARCHIVE
When paid ads attribution windows collapse to one day
Meta and Google now default to one-day click attribution windows. If a user clicks your ad on Monday and converts on Wednesday, most dashboards won’t connect the two. That’s not a bug—it’s a privacy-driven policy change that silently rewrites your ROI math. Longer consideration cycles, B2B funnels, and higher-ticket products all break when your attribution model assumes every conversion happens within 24 hours of the click. You can extend the window manually, but most operators don’t know the setting exists until months of campaign data no longer reconcile with revenue.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.