Conversion tracking for cannabis, starting with what you cannot advertise on

The complaint we hear: the delivery app says it sent a record month, the card clinic's calendar looks full, and the books match neither. A delivery order placed on Eaze happens entirely on Eaze's site and app, so it carries none of your sources. A medical card evaluation booked online is a health appointment, and the patient's qualifying condition is exactly the detail that must never reach an analytics or ad tag. Operators with several stores add a third problem: one menu provider, several locations and no store ID on the conversion. Without completed orders and finished evaluations tied to a source and a store, the business keeps paying for whatever reports best and cuts what brings customers back.

The ten-minute check: for each store or delivery zone, list every place a customer can order or book, and mark which happen on your domain and which on someone else's. Place a test order on each one you control and see whether a purchase event fires with an order ID and a store ID. For an evaluation clinic, fill in your own booking form and read what the browser sends; if a condition, a page title naming one, or the patient's email shows up in a request to Google or Meta, stop there. Then compare a month of marketplace-reported orders with completed orders in BLAZE, Dutchie POS or Cova.

Fixed looks like this: completed orders and finished evaluations sent from the business side as first-party server events with an order or booking ID and a store ID, no product detail or condition attached, every marketplace kept as its own source, and repeat customers from texts reported apart from new ones. If you run AIQ, its pixel goes in once, through tag manager or the page code, because both together double-fire. The free audit maps every ordering and booking path you run and checks what leaves each one.