Click Mismatch in Solo Ads: Why Counts Differ and What to Do

A click mismatch means the vendor's reported clicks do not match the clicks or visits your own tracker or analytics recorded. Some gap is normal, because the two systems count different things at different moments. A large or growing gap is a reason to investigate, and the right order is to check your setup first, then the counting rules, and only then the traffic itself.

This guide shows you how to do that without accusing a vendor too early and without accepting a bad number either.

TL;DR

• A vendor counts clicks on its own link. Your tracker or analytics counts visits or users that load your page. Those are different events, so small gaps are expected.
• Rule out causes in this order: your tracking setup, redirects and URL errors, counting differences, then invalid traffic.
• Judge a campaign by opt-ins and conversions, not by the click total on either report.
• Run a small test order with independent tracking before you spend real money with any vendor.
• If the gap stays large after you fix your setup, ask the vendor for click logs and request a refund or credit.

Table of Contents

• What a click mismatch actually is
• Why vendor and tracker counts differ
• What size of gap is normal
• How to diagnose a mismatch, step by step
• Reading the pattern: setup problem, counting difference or bad traffic
• Does a click mismatch mean solo ads are a scam?
• Prevent mismatches before you place the order
• What to do when the numbers still do not match
• Perspective: why we treat click counts as a starting point
• Get the vetting framework before you buy
• FAQ
• Sources

What a click mismatch actually is

In a solo ad, a vendor sends one email to its list with one call to action. When a subscriber taps the link, the request usually goes to the vendor's or a tracking system's server first. That server records a click and then redirects the person to your page.

This is how ad servers in general work. Google's documentation explains that an ad server counts a click when it receives the browser request and then redirects to the destination URL. It also says independent advertiser or publisher systems normally show small discrepancies because they count differently.

So the vendor's number is a count of requests received. Your number is a count of visitors whose browsers made it all the way to your page and ran your tracking code. Anything that interrupts the trip between those two points shows up as a mismatch.

A simple example: a vendor reports 200 clicks and your tracker shows 150 unique visitors. That is a 25% gap. It might be a broken script, a slow page, or people clicking twice. It might also be low-quality traffic. The number alone cannot tell you which.

Why vendor and tracker counts differ

Most mismatches have ordinary explanations. Here are the common ones, with what each looks like in your data.

Clicks are not users or sessions

Google's troubleshooting guidance separates the two ideas: a click is an ad interaction, while a session is a group of website interactions. One person can click several times and produce only one session. A click can also produce no session at all if the person leaves before the analytics code loads.

An agency write-up on vendor reports makes the same point about analytics: vendors count clicks, while Analytics counts users, and repeat clicks from one browser may collapse into a single user. If your solo ad email gets opened on a phone and tapped twice, the vendor sees two clicks and you may see one user.

Your page loads too slowly for the tag to fire

A tracking tag only counts a visit if it runs. If the visitor taps the link, sees a blank screen on a weak mobile connection, and backs out, the vendor has a click and you have nothing. Heavy landing pages, large images and scripts that load late all widen this gap. Mobile traffic makes it worse.

Redirects and stripped data

Google lists several reasons a platform can report more clicks than your own records: redirects, disabled JavaScript, browser limitations, stripped referrer data and repeat clicks can all stop a third-party tracker from recording a click the platform counted. If your link passes through a vendor redirect, then your tracker's redirect, then your page, each hop is a chance to lose a visitor or a parameter.

Your tracker can count more than the vendor

The mismatch can run the other way. Google notes that website logs can show more visits than the platform's click count when people reload the page or return through a bookmark. The platform may also filter out clicks it classifies as invalid, so the vendor's own number can be lower than the raw requests. If your count is higher than the vendor's, check whether the same people are coming back.

Invalid click filtering on the vendor side

Ad servers discard some clicks by design. For example, Google Ad Manager may discard rapid duplicate clicks and clicks it cannot match to a corresponding ad request. A solo ad vendor may or may not apply similar filtering. It is fair to ask which clicks are included in the number you were sent.

What size of gap is normal

No official body publishes a universal acceptable percentage for solo ads, and we will not invent one. What the sources agree on is the shape of the answer: small gaps are routine, while large or growing gaps deserve attention.

A practical way to use that:

1. Track your own gap on every campaign, from the first one, so you have a baseline.
2. Compare the same metric both ways. Compare vendor clicks to your tracker's clicks, not to analytics users.
3. Watch the trend. A steady 10% gap across five orders from different vendors points to your setup. A single order with a gap far above your baseline points to that order.
4. Look at behavior after the click, not just the count: time on page, opt-in rate and downstream conversions.

How to diagnose a mismatch, step by step

The research here is consistent: troubleshoot your tracking configuration before assuming fraud, make sure all tracking codes are correctly implemented, and keep redirect chains short. Follow this order.

Step 1: Confirm your tracking fires

Open your landing page yourself in a fresh browser, click through a tracked link, and confirm the click appears in your tracker and the visit in your analytics. Test on a phone over mobile data, not just on your desktop. Test the opt-in page and the thank-you page too, so conversion events are verified.

Step 2: Check the exact URL the vendor used

Vendors paste links into emails by hand or by template. A missing parameter, a typo in a subdomain, or an old link that points to a previous version of your page will send clicks where your tracker never sees them. Ask the vendor to send you the final link as it appeared in the email, or to send a test copy of the email.

Step 3: Shorten the redirect path

Count the hops from the email link to your page. Each redirect adds delay and a failure point, and some strip the parameters you rely on. Where you can, point the tracked link straight at the landing page. Our guide on how to track solo ad traffic covers setting up a clean link path.

Step 4: Label every order with UTM parameters

Give each vendor and each order its own labels so the traffic is separable in your analytics. Consistent naming also keeps your data from drifting between campaigns. A walkthrough on labeling traffic with UTM parameters shows how inconsistent tokens and renamed campaigns cause reporting errors, and the same discipline applies to solo ad orders. Use one naming pattern, such as vendor, date and offer, and never change it midstream.

Step 5: Compare like with like

If you read results in Google Analytics, remember it reports users and sessions. A guide to checking traffic sources in GA4 is a good refresher on how sources are grouped and why direct or unassigned traffic appears. Then compare vendor clicks to your tracker's click count, and use analytics users for engagement questions. For a deeper look at misattributed visits, see our piece on how to track direct website traffic.

Step 6: Only now look at traffic quality

If your setup is clean, your URL is right and the gap is still large, look at what the visitors did. Fraud testing on the advertiser side works in two ways. You can test for modern browser functionality such as JavaScript support and you can scrutinize engagement, such as dwell time on the landing page. Academic work on advertiser-side detection argues that advertisers have the strongest incentive to challenge visitors and verify they are real browsers rather than scripts.

In practice that means checking for a pile of visits with near-zero time on page, no scrolling, identical device and browser signatures, and clusters of the same IP ranges. Our guides to device fingerprinting clicks and IP filtering for solo ads go through each check.

Reading the pattern: setup problem, counting difference or bad traffic

Use this table as a starting point for interpretation. These are patterns to investigate, not proof.

Does a click mismatch mean solo ads are a scam?

No. A mismatch alone proves very little. Counting differences, repeat clicks, tracking setup and redirects all create gaps in legitimate campaigns. If results come in under expectations, the right response is to investigate further, including possible vendor inflation or fraud, after you have ruled out the simple causes.

It also cuts the other way. Click counts are weak evidence, even of fraud. Google's own report on third-party click auditing says some auditing firms struggled with engineering and accounting errors that caused severe click inflation, which made some of their fraud estimates invalid. If professional auditors can get click counts wrong, a single dashboard comparison should not be your verdict on a vendor.

The same report points to what is more reliable: ROI and the number of conversions, not the number of clicks. For a solo ad buyer, that means opt-ins, sales and the quality of those subscribers over the following weeks.

That said, solo ads do attract bad actors, and click counts are exactly where they hide. Our guides on click fraud prevention for solo ads and what click fraud means in digital ads explain the common tactics.

Prevent mismatches before you place the order

Most disputes are easier to avoid than to win. Build these habits in before the first dollar goes out.

Vet the vendor with specific questions

Google's traffic provider checklist for ad buyers is written for another channel, but the questions transfer well. It suggests asking where traffic comes from, requesting example URLs or real-time placements, asking whether detailed source reports and identifiable logs exist, and asking how delivery and conversions are measured. If a seller cannot give specifics, start with a small test and proceed cautiously.

For solo ads, add these:

• Will you send click logs with timestamps, IPs and user agents after delivery?
• Which clicks do you filter out of the number you report?
• How is delivery spread over time?
• What is your policy if a campaign under-delivers or my tracked clicks fall well short?

Our 21-question vendor vetting framework goes through the full list, and our article on solo ad click logs explains what to ask for and how to read them.

Start with a small test order

A small first order limits the cost of a bad vendor and gives you a clean baseline. Our guide to a 100 to 200 click test shows how to run it. Send the whole test to a dedicated landing page with its own tracker link so no other source muddies the data.

Use independent tracking, always

A dedicated tracker lets you compare vendor traffic and conversions with your own records. Advice for buyers consistently says to use your own click tracking and third-party tracking software to analyze traffic and spot bot or automated clicks. The IAB's traffic fraud guidance also recommends measuring campaign traffic against an independent vendor benchmark to help spot anomalies. That is exactly what your own tracker is: a second set of books.

If you want to go further, server-to-server postbacks record conversions without relying on the visitor's browser, which helps when scripts get blocked. Our S2S postback guide covers the setup, and solo ad click tracking explained is the best starting point if you are new to trackers.

What to do when the numbers still do not match

Say you have fixed your setup, tested on mobile, and one order still shows a big shortfall. Work through this sequence.

1. Save your evidence. Export your tracker's click report, your analytics source report and the email's send time.
2. Verify the link with the vendor. Ask for the exact URL used and a copy of the email.
3. Request the click logs. Compare timestamps with your own records. A vendor with real subscribers should be able to produce them.
4. Compare engagement, not just count. Show time on page, opt-in rate and conversions for that order against your baseline.
5. Ask for a credit or refund in writing. Stick to the data: what you ordered, what you tracked, what you checked on your side.
6. Use the platform's dispute process if you bought through a marketplace. Check the marketplace's terms for how under-delivered orders are handled before you buy.
7. Record the outcome. Note it so your next vendor decision uses what you learned.

Keep the tone factual. A vendor who responds with logs and a fair offer is worth a second small test. A vendor who dodges every question has told you what you need to know.

Perspective: why we treat click counts as a starting point

We run this site from the buyer's side of the table, and we have been on the vendor side too. Our view is that a click count is a claim, not a result. It tells you how many requests a server logged. It does not tell you who those people were, whether they read the email, or whether they will ever open another one from you.

The buyers we see burned are rarely the ones who noticed a mismatch. They are the ones who had no tracker, so they had nothing to compare. They took a vendor's dashboard on trust, spent more on a second order, and found out weeks later that the list never converted.

So our advice has three parts. Install your own tracking before you order. Learn your normal gap so you can recognize an abnormal one. And judge every vendor on opt-ins and downstream results, with the click count as a clue. We make no promises about what any campaign will earn, and neither should any vendor you trust.

— Philip Coble

Get the vetting framework before you buy

SoloAdsGuide.com is built for exactly this situation: buyers who want to verify before they spend. Our guides walk through click tracking, click logs, fraud red flags and the 21-question vendor vetting framework, so you can ask the right questions and check the answers with your own data.

Start on the SoloAdsGuide.com home page to get the buyer's checklist and the full set of guides.

FAQ

What is a normal click discrepancy in solo ads?

There is no official percentage. Small differences are routine because vendor platforms and trackers count differently, and large or growing gaps warrant attention. Measure your own baseline across several orders and investigate orders that sit far outside it.

Why does my tracker show fewer clicks than the vendor reported?

The most common reasons are redirects, slow page loads, blocked scripts and repeat clicks. Google lists these as reasons a third-party tracker can miss clicks that the platform counted. Check your tags, the URL the vendor used and the length of your redirect chain first.

Why does Google Analytics show fewer visitors than my tracker?

Analytics counts users and sessions, and a click that leaves before the tag loads produces neither. Google explains that one person can create multiple clicks but only one session. Compare clicks with clicks, and use Analytics for engagement and conversions.

Can I get a refund for a click mismatch?

Sometimes, but it depends on the vendor's or marketplace's terms and on your evidence. Save your tracker export, request the click logs and write to the vendor with the facts. Check the refund policy before you place the order, not after.

Should I stop buying solo ads if I see a mismatch?

Not automatically. First rule out your own setup, then compare opt-ins and conversions against your baseline. If the shortfall repeats with a vendor and the vendor cannot produce logs, stop buying from that vendor and test another with a small order.

Sources

• How Campaign Manager 360 counts impressions and clicks
• Counting impressions and clicks, Google Ad Manager Help
• Clicks and sessions discrepancy for Google Ads and Google Analytics
• Differences between Google Ads and third-party data
• Why Doesn't My Vendor's Report Match Google Analytics?
• How to Verify Solo Ads Clicks With Independent Tracking
• How Fictitious Clicks Occur in Third-Party Click Fraud Auditing
• Click Fraud Detection on the Advertiser Side
• Traffic provider checklist, Google Ad Manager Help
• Solo Ad Stats: What to Check Before You Buy Traffic
• IAB Best Practices for Traffic Fraud
• Fix Facebook UTM token errors and rename drift
• Track traffic sources in Google Analytics 4

Recommended

• Offer-to-List Mismatch: Why Great Traffic Won't Convert
• Stop Losing Solo Ad Conversions: S2S Postback Setup and 21 Questions
• Why Solo Ad Vendors Inflate Click Counts: 2026 Guide
• Marketers: Verify Solo Ad Traffic With a 100 to 200 Click Test