Dakio already sends the server side of Purchase, InitiateCheckout and the checkout's contact step (Lead from SDK sites, AddShippingInfo from Dakio's own storefronts) (Meta's Conversions API) for every store with a Pixel set up in Dakio. Send the browser side with the same event id and Meta counts each event once, with better matching than either side alone.
Purchase, deduplicated
Make the id before checkout, pass it as eventId, and fire the browser event with it once the order is placed:
Dakio's server event for that order carries the same eventId, so Meta merges the two.
| Export | What it does |
|---|---|
| loadPixel(id) | Adds Meta's pixel script once and fires PageView |
| trackPixel(event, params, eventId?) | fbq('track', …) with eventID; a no-op on the server |
| newEventId(prefix?) | A unique id like pur_k3p9… |
| productParams(product, qty?) | { content_ids, content_name, content_type, value, currency, num_items } |
| purchaseParams(quote) | The same, for a whole priced bag |
Google Tag Manager: store.tracking.gtmContainerId holds the store's container id if it has one, and every trackPixel call also pushes dakio_<Event> (with the same params and eventId) to dataLayer.
Dakio's own storefronts (Store Studio, the classic theme, funnels) already do all of this for you: see Storefront dataLayer & GTM.

