Your AIQ menu takes the orders. Your ads can't tell which ones they earned.
AIQ credits your texts with revenue and your menu's Google Analytics shows plenty of shoppers, but nobody can say which paid channel filled the pickup queue. AIQ Ecommerce is a single-page menu, so page-load tags miss most of the shopping, and a Basic Menu runs on an AIQ-hosted URL instead of your domain. We fire the menu's own purchase event once, carry the click to the order, check it against the POS sales AIQ imports, and send each ad platform only what its cannabis policy allows.
Free30 minutesNo obligation
Alpine IQ · what breaks
What goes wrong with Alpine IQ tracking
- 01
"GA4 shows shoppers on our menu but hardly any orders"
AIQ Ecommerce is a single-page app, so a page-load tag sees the first screen and nothing after. Carts and checkouts happen without a new page, so the only paid channels you're allowed to run end up optimizing toward menu browsers instead of buyers.
- 02
"The Order Online button loses the ad click"
A Basic Menu lives on an AIQ-hosted URL. When your homepage button sends shoppers there and nothing carries the click ID across, it stays behind on your site, and you pay for visits you can't connect to a single pickup.
- 03
"Our custom menu reports double the revenue"
On a Blueprint API build, AIQ fires the order event itself at checkout. A developer's second purchase tag, or treating the checkout frame's ORDER_COMPLETE message as a sale, counts every order twice, and inflated return keeps weak campaigns funded.
- 04
"AIQ says the texts made the money, and so do the ads"
AIQ ties POS sales to campaign sends inside windows you set, while ad platforms claim the same order from a click. Stacked, every channel looks profitable and budget drifts to the loudest report.
Alpine IQ · the fix
What changes once the AIQ menu reports cleanly — Alpine IQ
Orders traced to the click that started them
The click ID rides from your site through menu checkout, then reaches ad platforms from a first-party container on your subdomain.
One revenue figure per order
Each purchase is keyed on the AIQ order ID wherever the event carries it and checked against its POS transaction, so texts and ads sit side by side, not stacked.
Spend aimed at channels that can actually run
Conversions go to destinations that accept cannabis, such as Surfside through AIQ's integration, and to Google or Meta only for qualifying hemp and CBD lines.
Alpine IQ · architecture
What Alpine IQ actually lets you hook into
Everything below comes from AIQ's own help center. Where AIQ is silent, we treat it as something to test, not a feature.
- 1
AIQ Ecommerce Tag Manager integration
A container ID under Store > Integrations receives view_item, add_to_cart, remove_from_cart, begin_checkout and purchase, named as GA4 names them. AIQ recommends History Change triggers because the menu is a single-page app.
- 2
AIQ Ecommerce Google Analytics integration
Takes a GA4 measurement ID only. AIQ doesn't list the events it sends, so we confirm purchases arrive and don't overlap a Tag Manager GA4 tag.
- 3
The AIQ tracking pixel
A header script, or a Tag Manager load, recording pageviews and aiq() events such as orderCompleted to match visitors to your contacts. AIQ documents it feeding its own audiences, not ad platforms.
- 4
POS transaction sync
AIQ imports transactions, products and customers from POS systems like Treez, Dutchie and Flowhub; Treez says allow up to 24 hours. This is what we match online orders against.
- 5
Audience exports, no native Google Ads or Meta link
AIQ's integrations matrix lists Surfside, MediaJel and email tools as destinations. Google and Meta tags go through your own Tag Manager container, and AIQ documents no server-side conversion feed to either.
Alpine IQ · diagnose
Where Alpine IQ tracking breaks, in diagnostic order
We start with which menu you run, because the Basic Menu, the SEO Menu and a Blueprint build each fail in a different place.
- 01
Identify the menu type
An AIQ-hosted Basic Menu, an SEO Menu on your domain or reverse proxy, or a custom Blueprint front end.
- 02
Count purchase events on one test order
The GA4 integration plus a GA4 tag in Tag Manager is the likeliest pair; on Blueprint, a hand-added purchase tag.
- 03
Check the single-page triggers
Browse the menu and watch whether product and cart events fire without a page reload.
- 04
Follow the click ID from ad to order
Order once from a tagged URL and confirm the identifier survives the hop from your site to the menu.
- 05
Compare online orders with POS transactions
Per order, over a closed week, separating med from rec and flagging pickups that never happened.
Alpine IQ · prove
The QA evidence — Alpine IQ
Run on real test orders through your live AIQ Ecommerce menu, placed from ad-tagged links, never from the admin preview.
Source of truth
AIQ Ecommerce orders and the POS transactions synced into AIQ, by order ID, date, med or rec menu, and fulfillment type
- A test order from an ad-tagged URL, click ID confirmed on the purchase event.
- Exactly one purchase per order in GA4 and each ad platform, sharing AIQ's order ID.
- Cart and checkout events firing on route changes inside the menu.
- Online orders reconciled one by one against POS transactions in AIQ.
- Unclaimed or cancelled orders removed from reported revenue.
- Loyalty redemptions absent from the acquisition conversion.
- Repeated 30 days later and after any menu or POS change.
Alpine IQ · free audit
What we check in the free audit
- Identify the menu type
- Count purchase events on one test order
- Check the single-page triggers
- Follow the click ID from ad to order
- Compare online orders with POS transactions
Checked against
AIQ Ecommerce orders and the POS transactions synced into AIQ, by order ID, date, med or rec menu, and fulfillment type
Free30 minutesNo obligation
Alpine IQ · when not to buy
When you don't need this on Alpine IQ
Plenty of AIQ shops are better off with a short settings check, and we'll say so.
- If you sell THC products and only want Google or Meta ads, both prohibit them. Fix the menu's GA4 events and stop there.
- If orders come from organic search, your Google Business Profile and marketplace listings rather than paid media, AIQ's campaign attribution plus clean GA4 is probably enough.
- If you're on the Basic Menu with no ad budget, moving to an SEO Menu on your own domain matters more than any tag.
- If the only fault is the GA4 integration and a Tag Manager GA4 tag both counting purchases, switch one off yourself.
Alpine IQ · what we deliver
The event map on Alpine IQ
Menu product viewed
view_item from the event AIQ pushes to Tag Manager, labeled med or rec, since AIQ runs those as separate menus.
Added to cart
add_to_cart, caught on AIQ's data layer push inside the menu rather than on a page load.
Checkout started
begin_checkout, split by pickup, curbside or delivery where the menu exposes the order type.
Online order placed
purchase, the main conversion, valued from the order and deduplicated on the AIQ order ID once we confirm the event carries it.
Order picked up and paid
Matched to the POS transaction synced into AIQ; unclaimed and cancelled orders are pulled back out.
Loyalty redemptions and walk-in sales
Logged for retention and kept out of acquisition, along with counter sales that never touched the menu.
Written guarantee
95%+ tracking accuracy
Measured against AIQ Ecommerce orders and the POS transactions synced into AIQ, by order ID, date, med or rec menu, and fulfillment type. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Alpine IQ questions, answered
No. Google bans ads for substances that induce highs, and Meta bans ads offering THC sales. Google allows topical hemp CBD at 0.3% THC or less, with approval, in California, Colorado and Puerto Rico only; Meta allows CBD with written authorization and LegitScript certification.
Not according to AIQ's documentation. Its integrations matrix lists Surfside, MediaJel and email platforms as destinations, so Google and Meta tags run through the Tag Manager container you connect to AIQ Ecommerce.
AIQ Ecommerce is a single-page app, and AIQ itself recommends History Change triggers for that reason. If the purchase tag isn't built on AIQ's own purchase event, orders go missing too.
AIQ says it doesn't support iframe menus on your site. The documented routes are the SEO Menu on your own domain or a reverse proxy, which also keeps the shopper and their click on one domain.
Often, yes. AIQ maps POS transactions to campaign sends inside windows you choose, while ad platforms claim orders from clicks, so we report both against one order ID instead of adding them.
The tracking does. Advertising is narrower: Google bans products that simulate tobacco smoking and Meta bans vaporizer and paraphernalia sales ads, so we check what you sell before recommending any ad build.
More on Alpine IQ
- Deltek GovWin IQGovWin IQ pursuits sit in your CRM beside website leads. Google Ads can't tell t…
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
RELATED GUIDES
Booking tools beside Alpine IQ (AIQ), and what their bookings feed
- Lighthouse 360Lighthouse 360 keeps the schedule full. Your ads still can't tell which patients were new.
- springbigYour springbig texts bring buyers in. GA4 files those sales under "direct."
- Loopy LoyaltyLoopy Loyalty conversion tracking: see which ads bring people back to the counter
- SimpleTextingYour ads fill the SimpleTexting list. Google Ads can't tell which ones did it.
- Square MarketingSquare says your emails made the sale. Your ad account says nothing happened.
- Constant ContactYour ads fill your Constant Contact list. Your ad accounts can't tell which ones paid off.
- RevenueWellPatients request appointments in RevenueWell. Google Ads never hears about it.
- TextedlyTextedly keeps signing people up. Your ad reports still say zero.
Free · 30 min
See which channels really fill your AIQ pickup queue
Free30 minutesNo obligation
