After the doorstep, follow the story.
Your route tells you where you went. QR tracking and website attribution help you understand what happened next, and which campaigns deserve another round.
- One funnel per campaign, from doors to revenue
- Results by territory and by crew member
- Revenue when your site reports a value
Private beta. Attribution depends on the integration on your website.
Sample campaign. Bar lengths are not to scale.
One campaign, six lines, start to finish.
The app assembles a proof receipt for each campaign, a plain summary you can share as text. Every line has one source. A line with nothing behind it stays blank, because a blank is more honest than a zero that looks like a result.
| Line on the receipt | Sample value | Where the number comes from | Stays blank or zero when |
|---|---|---|---|
| Flyersprinted and walked | 500 | The smart-flyer batches ordered for this campaign, added together. | No batch was ordered for the campaign. |
| Doors coveredfrom the trail | 412 | Door counts from every shift walked on the campaign. These are estimates. | No shift has been recorded yet. |
| Scans | 84 | Scans logged by the redirect for any QR code that belongs to the campaign. | Nobody has scanned yet. |
| Quote requestsleads | 12 | Lead events your website reported through the pixel. | The pixel is not part of your plan, so leads cannot be traced. |
| Contracts | 4 | Conversions of the kind booking or purchase that trace back to a campaign code. | Your site has not reported a booking or purchase. |
| Revenuetraced | CA$640.00 | The values your site attached to those conversions, added together. | Conversions were reported without a value. |
Sample values for a fictional campaign called Maple Ward. They are not customer results. The campaign view also reports the number of shifts, the distance walked and the share of scans that became bookings.
Different numbers. Different questions.
Your route tells you where you went. A useful campaign report connects the funnel without treating activity as an outcome.
1 Coverage
Did we work the area?
Routes, distance, shifts and estimated doors describe the fieldwork and help you assess the campaign’s physical reach.
It does not tell you how many people read the flyer.
2 Scans
Did the flyer prompt a response?
A tracked redirect records a scan before sending the visitor to your website. The code’s scope connects that response to a campaign, territory, crew member or individual smart flyer when configured.
A scan is interest. It is not a sale.
3 Conversions
What did the visitor do?
The pixel or conversion API reports supported actions such as a lead, booking, purchase or call event.
An event only means what your website integration is configured to report.
4 Revenue
What value was attributed?
Value-bearing conversions can report revenue to the campaign.
Revenue is not profit or return on ad spend. Printing, labor, shipping and other campaign costs still belong in the decision.
More flyers? Or a smarter next move?
A busy route and a strong campaign are different things. The app rolls a campaign into one score so the headline number means something on day one. Load a sample campaign or type your own figures to see how the score is built.
| Input | Value | Rule | Points | Share of score |
|---|---|---|---|---|
| Scans | 84 | × 2 | 168 | |
| Bookings | 4 | × 20 | 80 | |
| Revenue | 640 | ÷ 10 | 64 | |
| Campaign score | 312 | 5% of scans became bookings | ||
Maple Ward, 72% of the area covered, 12 reported leads. More recorded bookings here. Before expanding the drop, review the offer, the costs and the ground still uncovered.
How the counting works.
These rules decide what lands in a campaign’s totals. They are the reason two scans can show as one, and the reason a booking can show up days after the scan.
- Repeat scans
- 3 minThe same visitor hitting the same code again inside three minutes is counted as one scan. A later scan is counted again.
- Duplicate events
- onceEach website event carries an id. The same id arriving twice, from the browser and from your server, is stored once.
- Bookings
- booking + purchaseBoth kinds count as a booking in the campaign totals. A lead or a call does not.
- Reported value
- 0 to 1,000,000A single event’s value has to fall in this range. Anything outside it is rejected.
- Coming back later
- 365 daysThe scan is remembered in a first-party cookie and local storage, so someone who scans today and books next week from a direct visit still traces to the flyer.
- No scan on record
- kept, unattributedAn event that cannot be tied to a scan or a code is still recorded. It does not count toward any campaign.
- By crew member
- doors beside scansThe crew board ranks members by estimated doors and shows scans next to them, because the most doors is not always the most scans.
A little more detail.
Four questions people ask before they trust a results page.
- No Will every customer be attributed?
- Attribution depends on scans, integration setup, browser behavior, consent, and the customer journey. A direct phone call or untracked purchase may not connect back to a flyer.
- No Do I need a new website?
- Keep your existing website and checkout. DoorDroppr sends QR traffic to your destination and receives supported events through your integration.
- No Are the numbers shown customer results?
- The figures on this page are illustrative data that explain the workflow. They are not a revenue claim or a customer case study.
- Not today Is anything matched without a scan?
- Matching by coupon redemption or by booking address is not built, and a full multi-touch model is not either. Today a result traces through a scan or a code.
Send your next drop where the last one worked.
See scans, leads and bookings street by street.
- Join the list
- Get your invite by email
- Walk your first street