Funnel export

1. 1
   They scan the box QR (compliance or ebook) A customer scans the QR on the back of the packaging for the compliance documents or the free ebook, or they request the ebook from the site. Both of those first captures live under Leads (Ebook downloads and Packaging QR scans). We store a sequence token (lead_id) on that lead so later emails can recognize them.
2. 2
   Next day: Email 1 → “Pledges from Email 1” About one day later we email them a link to the pledge page, a chance to win a free pair. The link must keep ?lead= with that same sequence token so the form prefills and ties the pledge back to the scan. When they submit the form, they are in the draw, and this row ticks up.
3. 3
   A few days later: Email 2 → “Feedback from Email 2” We write again to confirm shipping details, and in the same email we also ask whether they left a purchase review. Those are two separate asks in one message: address confirmation and review, not one requirement. The link goes to /feedback/?lead= with the same lead token. Completing that form updates their Email 1 pledge row (feedback fields written onto it); only that path counts here. People who open /feedback/ without an Email 1 pledge create a separate row and land under Feedback, not this funnel. We never say a review helps their draw odds; people sometimes assume it anyway and do both.
4. 4
   If they go leave the review → “Amazon review clicks” After Email 2 feedback, they can click through to Amazon. That outbound click is the detail row under Feedback from Email 2, the clearest signal they acted on the review ask. Optional only; it does not change draw eligibility. Amazon clicks from direct /feedback/ submissions are listed separately under Feedback.

The ?lead= / lead_id token is the thread: scan → Email 1 pledge → Email 2 feedback → optional Amazon click. Break the token and attribution (and this funnel’s numbers) fall apart.