Platform setup
Where the Lapis pixel goes and how the click ID survives on each website platform, plus how to verify the install.
The Lapis integration is the same everywhere: put the pixel on every page, preserve the click ID all the way to the conversion, and send a server event from your backend. What changes per platform is where the code goes. Pick yours:
| Platform | Pixel install | Click ID persistence | Typical conversion source |
|---|---|---|---|
| Shopify | theme.liquid |
Cart attribute → order | orders/create webhook |
| Framer | Site Settings → Custom Code | Link decoration to app domain | Your app backend |
| Webflow | Site Settings → Custom Code | Hidden form field or link decoration | Form webhook / backend |
| WordPress / WooCommerce | Theme footer or plugin | Session → order meta | woocommerce_order_status_completed hook |
| Google Tag Manager | Custom HTML tag | Depends on site | Depends on site |
| Next.js / custom code | Root layout | First-party, your call | Your backend |
| Squarespace / Wix | Code injection | Hidden form field | Form email/webhook |
Two rules hold on every platform:
- The pixel goes on every page, not just the ad landing page. Visitors browse before they convert, so the pixel must be present wherever the conversion flow starts.
- Never invent a click ID. If the
lapis_sidcookie is absent, the visitor did not come from a tracked ad. Skip the decoration or hidden field and send the conversion unattributed (or not at all).
Verify your install
After you install, run this standard test:
- Open
https://YOURSITE/?utm_source=chatgpt&lapis_campaign=lapis_test&lapis_adgroup=setup_check&lapis_ad=test_ad_01. - Confirm the
lapis_sidcookie exists in DevTools. - Confirm a request to
api.trylapis.com/api/v1/pixel/ereturned204.