Email lead
Fires when someone completes the email step of the Klaviyo popup.
Enter the admin password for this deployment.
Every store sending value events through this deployment.
| Store | Health | Mode | Shopify domain | Events | Last checked |
|---|
Open a saved store to load its status.
Every value event this store sends to Meta, newest first — the last hour. Updates automatically while this screen is open.
—
Counted by this service, in US Central days.
—
How this store is identified, which storefronts may send it browser events, and how consent is handled.
Removes its configuration and credentials. Dedupe markers and counters expire on their own.
All four names are custom, so every event lands in Meta alongside what Elevar already sends. Nothing collides and Elevar needs no changes. Re-anchor the values here quarterly.
Fires when someone completes the email step of the Klaviyo popup.
Fires on the SMS step of the Klaviyo popup.
Two tiers. A form submission is the most gameable event in the stack, so it carries a small value; the real value is gated on your team approving the account.
Comma separated.
Fires on native B2B company approval, when a customer is linked to a company. It runs server-side days later with no browser context, so it replays the fbp/fbc captured at submission.
Fires on an order whose net total falls inside the band. Sent value is the order net plus the bonus.
The dataset these events are sent to, and the token that sends them.
Admin access for the order and customer webhooks that fire trade and sample events.
Optional, but it sharpens two things: event IDs and the new-emails-only gate.
The storefront needs the capture layer: the Klaviyo popup listener, _fbp/_fbc cart stamping, and the trade-form identity hint. One line installs all of it.
In the store's admin, go to Online Store → Themes → ⋯ → Edit code → layout/theme.liquid and paste this just before </body>. No files, no theme settings, no per-store JS.
assets/meta-sidecar.js and snippet still work. Use the one-liner or the bundle — never both.
Going live clears the test event code and enables the store in one atomic step. From that moment events count.
One of each enabled event through the real pipeline, tagged with your test event code.
The scan proves what it honestly can and ticks those boxes itself. GTM and the Facebook channel stay manual.
Go-live re-verifies every gate on the server and hard-blocks a detected name collision — that one can't be waved through, it would double-count.