0 Clicks But 63 Claims? What Claims, Clicks, Views and Downloads Actually Mean

You open your swap report the morning after a send, and the numbers don't make sense.

Zero clicks. Sixty-three claims.

That's not a typo, and it isn't broken. But it does look like the platform lied to you, and that feeling — the specific panic of thinking your swap failed when it actually worked — is exactly where this article starts.

Here's the short version: 0 clicks but claims happens because "click" and "claim" are two different measurements, taken by two different systems, at two different points in the chain a reader travels through. Neither number is wrong. They're just not answering the same question.

Let's build the map.

Difference Between a Click, a View, and a Claim

Picture a reader sitting in their inbox. Here's what actually has to happen, in order, before you see a claim show up on your report:

1. Send — your partner's newsletter goes out, or yours does
2. Click — the reader clicks the tracking link inside that email
3. View — the landing page loads in their browser
4. Claim — they enter their email and hit the button to get the book
5. Download — they actually get the file, or open it in their reader app

Each one of those is counted by a different piece of software, and each one only knows about what happened at its own stage.

Nothing forces those numbers to match — a click is a link being followed, a view is a page loading, a claim is a reader typing their email into a form and submitting it. Three different actions, taken by three different people at three different moments, and not every reader does all three the same way.

That's also why your click count can sit at 0 while your view and claim counts climb. A reader can arrive at your landing page without the tracking link ever registering the click that sent them there. More on exactly how in a minute.

Is a Download a Click? (No — Here's Why)

Short answer: no. A download is the last step in the chain, not a substitute for any of the ones before it.

Here's where this trips people up. If you have 320 claims and 192 downloads, it's tempting to read the gap as "128 people clicked but didn't finish." That's not what's happening.

A claim means a reader gave you their email and requested the book. A download means the file actually landed — they hit the download button, or their reading app pulled the file. Some readers claim a book and then never download it. They meant to, got distracted, or decided later they weren't interested.

That gap is normal, not a warning sign.

None of this touches your click count either way. Downloads happen after the claim, on your delivery page, tracked by the delivery system. Clicks happen before the claim, on the tracking link, tracked separately. They're at opposite ends of the chain and neither one is a stand-in for the other.

Why Does It Say 0 Clicks If I Have Claims?

This is the one that actually causes the panic, so it deserves the direct answer.

A tracking link only counts a click when a reader's device actually fires the request through that specific link. If a reader gets to your landing page any other way — forwards, previews, cached versions of the email, or a delay in when the click gets logged — the page view and the claim still happen, but the click that technically got them there was never captured by the tracking link itself.

Add to that: click tracking commonly lags behind claim tracking. Claims and downloads are recorded the instant they happen, because they're direct actions on your own landing page. Click counts on the tracking link can take longer to populate, especially in the hours right after a send, because that data has to be aggregated and reported back before it shows up on your dashboard.

So the sequence you're often looking at isn't "no clicks happened." It's "the clicks haven't been counted yet, but the claims already have been." Check the same report again a few hours later, sometimes the next day, and the click number frequently moves even though nothing about the swap changed.

There's a second layer worth knowing, and it matters if you're trying to understand your star rating and not just your report. The Click Threshold used in star ratings is a pass/fail measurement — it either hits 1.0 or 0 — and it only watches whether your newsletter drove at least ten clicks to your partner's book. That's a completely different number from the raw click count sitting in your tracking-links report, which shows total clicks on both links regardless of who sent the traffic.

A book can carry fifty raw clicks and still score a 0 on Click Threshold, because Click Threshold is measuring your effort to promote them, not their overall traffic. Confusing those two numbers is the single most common mistake in reading a swap report, so it's worth reading that paragraph twice.

Why Your Platform and Your Email Provider Report Different Numbers

Now for the part that makes people feel like they're losing their mind: the same swap, two dashboards, two different sets of numbers.

Your swap platform reports 320 claims and 0% clicks. Your email provider (MailerLite, in one author's case) reports 320 subscribers and 0 clicks. Those numbers look like they're confirming each other, and in a way they are — but they got there independently, and that's the part worth understanding.

Your email provider only sees what happens inside its own tracked link. It knows a subscriber opened the email, and it knows if they clicked a link it wrapped. What it does not know is what that person did on the landing page after they arrived — whether they claimed the book, whether they downloaded it, whether they even reached the page at all versus previewed the email without triggering a click.

Your swap platform only sees the other half. It knows a claim happened on your landing page, because that page is its own. It does not have visibility into your email provider's open and click tracking, because that's a separate system entirely, run by a separate company, with its own separate rules for what counts as a click and when it gets reported.

Neither tool is lying. Neither tool is broken. Each one is telling you the truth about the one thing it can actually observe, and nothing forces two independently-built systems, tracking two different halves of the same reader journey, to land on identical numbers.

That's really the whole lesson.

Once you see the chain — send, click, view, claim, download — a mismatched report stops being scary and starts being informative. Zero clicks with claims already coming in usually just means the click count hasn't caught up yet. A gap between claims and downloads usually just means some readers claimed and didn't finish. And two platforms disagreeing usually just means they're each reporting the slice of the journey they can actually see.

What actually matters after a swap isn't whether every number matches. It's whether claims and downloads are moving in a direction that makes sense for the size of the list your partner sent to. That's the number worth watching. The rest is the map, not the verdict.

So next time your report opens on 0 clicks but claims, you'll know what you're looking at — and what to check back on in a few hours before you assume anything went wrong.