A member in BLAZE, for retail and delivery alike.
Point of sale, ecommerce, and delivery platform for dispensaries. Every consented visitor arrives as one record, with its receipt.
The scan shows whether your site already runs BLAZE.

How it works
Inside BLAZE, where you already work.
As a member in your BLAZE customer database, tagged by source and consent, visible to retail and delivery alike, ready for the loyalty and marketing tools BLAZE connects to.
BLAZE partner API where enabled for your account; CSV import otherwise.
- 1A visitor says yes on your site.
- 2GreenLeadSource verifies the record and writes the receipt.
- 3The record lands in a member in your BLAZE customer database, tagged.
What we send, and how.
Consent receipts travel as a tag, property, or field. No destination has a receipt object of its own, and every field is one the visitor agreed to.
- What it is
- Point of sale, ecommerce, and delivery platform for dispensaries.
- Website
- blaze.me
- How it connects
- API or File · A member in your BLAZE customer database, tagged
- What we send
- Enriched Customer Contact, with its consent receipt

Late bulletin
Every day you wait, visitors leave as strangers. Scan your site today.
Ten seconds. Your Customer Reach Score, what fires before anyone says yes, whether your age gate is the only question you ask, and what your privacy policy leaves out. Nothing installed, nobody contacted.
- A real browser load of your homepage, screenshot included
- Every tag that fires before a visitor can answer
- Your privacy policy, lined up against what the site does
- Modeled traffic and what an ask-first step would return