| Piece | Scans | Call taps | Leads | Response rate |
|---|---|---|---|---|
| magazine | 6 | 0 | 0 | 0.0% |
| (not tagged) | 3 | 0 | 0 | 0.0% |
| All pieces | 9 | 0 | 0 | 0.0% |
How to read these numbers
- Scans
- Landing page views, counted per page load, not per person. Someone who scans a door hanger twice is two scans. That is fine for comparing one piece against another, which is the question being asked, but it is not a headcount.
- Call taps
- Taps on a phone-number link. This is a proxy for calls, not proof of one. A tap does not mean the call connected or lasted, and someone may tap twice or hang up. Provable call attribution needs a dedicated tracking number.
- Leads
- Quote form submissions, counted whether or not the notification email sent. The email is the record of what the lead said; this is the count.
- Response rate
- Call taps plus leads, divided by scans. A proxy, not proof, because it inherits the call tap caveat above. Useful for ranking pieces against each other, not as an absolute conversion rate.
Confirmation page loads 0 Not the lead count. Every load of the thank-you page,
so a refresh or a revisit counts again, and it is campaign-wide rather
than per piece. Expect it to run at or above Leads. Useful only as a
rough cross-check against the mailbox.
Other page views 0
Views on any other path, e.g. the privacy page. Not scans.