Enter the admin password for this deployment.
Every store sending value events through this deployment.
| Store | Health | Mode | myshopify 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. Internal duplicate-guards and counters expire on their own.
Custom event names that land alongside Elevar. Re-anchor the values quarterly.
Purchase count.
Fires when someone completes the email step of the Klaviyo popup.
Fires on the SMS step of the Klaviyo popup.
Two tiers: a small value on the form submission, the real value once your team approves the account.
Comma separated.
Uploads the same sign-up as an offline conversion. Its own value and its own conversion action — nothing is shared with Meta.
Pick one, or enter an ID manually.
Separate from the Meta value above.
Fires when you approve the account in Shopify (the customer gets linked to a B2B company).
TradeApproved still fires as normal; this additionally sends a real Purchase at approval, so approvals feed your max-value Purchase campaigns too. A deliberate, low-volume addition to your Purchase count. Uses the value below.The approval is the signal worth bidding on. In Google Ads, make this action Primary and the sign-up one Secondary — otherwise Smart Bidding chases the far more numerous sign-ups.
Pick one, or enter an ID manually.
Separate from the Meta value above.
Purchase count — but Elevar's Purchase already reports the same revenue, so the two overlap if you total value across events. That's usually what you want here (you're chasing real trade revenue); switch to Bonus only if you'd rather not restate it.Fires on an order whose subtotal falls inside the band below — your proxy for “someone bought a sample”.
Purchase already carries the order value and its order-to-order variance, so Bonus only adds just the strategic uplift on top — no double-counting. With a flat value, optimise the sample campaign on cost-per-result / volume. The subtotal modes give value variance for Highest Value bidding, but restate revenue Purchase already reported.Uses the order subtotalAfter discounts, before shipping and tax. A $40 item with $8 shipping counts as $40. — the same figure the value modes above use.
Mirrors the events you pick into one custom event, each carrying its own value. Superseded by the roll-up value event below, which does the same thing and can also include real purchases.
Optional. One event fired by every value action — purchase, sample, SMS, email, trade approval — so a single value-optimised campaign can chase your whole ladder.
Two roll-up events are enabled. The legacy Consolidated value event above overlaps this one — every lead, sample, and approval will fire both. Switch the legacy one off once your campaign points at this event.
Keep this high in your Aggregated Event MeasurementYour 8 prioritised web events in Events Manager. Put this one just below Purchase. priority list.
The dataset these events are sent to, and the token that sends them.
A second destination for the two trade events, independent of Meta. If one fails the other still sends. Only needed if you switched Google on under Events & values.
1. Developer token — Google Ads → Tools → API Center, on your manager account. Basic Access is enough. Approval can take a few days.
2. OAuth client ID + secret — Google Cloud Console → APIs & Services → Credentials → Create OAuth client ID → Desktop app. Enable both the Google Ads API and the Data Manager API on the project (APIs & Services → Library).
3. Refresh token — authorise that client once, signed in as an account that can see the Google Ads account, with the scope https://www.googleapis.com/auth/adwords. The token inherits that account's permissions, so if it can't reach the Ads account the credentials verify and then fail on the first upload.
Then check Audience. Internal (everyone is in your Google Workspace organisation) is the better setting and needs nothing further — no publishing, no verification, no expiry — but only org accounts can authorise, so a personal @gmail.com will be refused. External must be moved from “Testing” to In production, or refresh tokens expire after 7 days and the destination silently stops a week after go-live.
4. Customer ID — top right in Google Ads (123-456-7890; dashes are fine). Set Login customer ID only if the credential belongs to a manager account.
With either one off, Google accepts every upload and then discards it — success responses, no conversions. You confirm these in Verify & go live.
Only needed for the trade and sample events — they're triggered by Shopify orders and customers. If you're only running the email/SMS opt-in events, you can skip this section entirely.
Shopify discontinued admin-created custom apps on 2026-01-01, so the app must be created in the Dev Dashboard with the permissions read_orders and read_customers. You only need the Client secret — it also confirms that order and customer messages genuinely came from Shopify, so there's no separate secret to set.
Add this exact redirect URL to the app's Allowed redirection URL(s):
A development store inside the app's own Dev Dashboard organisation authorises automatically — no Connect step needed. A live merchant store must use Connect.
You can go live without this. Adding a key does one useful thing: it makes the “new emails / new numbers only” filters actually work, so repeat popup opens don't get counted as fresh leads.
Your storefront needs the capture snippet — it's what notices the Klaviyo popup, remembers which ad the visitor clicked, and tags the trade form. One line installs all of it. Only needed for the email and SMS opt-in events.
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 code.
Your storefront address must be listed in Basics, or these events are rejected. Removing the snippet stops capture; so does switching the store off here.
If this store previously used a bundled theme snippet (its own meta-sidecar.js), that still works — use the one-liner or the bundle, never both.
Going live clears the test event code and switches the store on, all at once. From that moment events count.
One of each enabled event through the real pipeline, tagged with your test event code. With Google switched on, both destinations need a passing run.
Run the pre-launch check first — it proves what it honestly can and ticks those boxes for you. The last two are judgement calls only you can make; the evidence it found sits under each one.
Go-live re-checks every gate on the server and hard-blocks a detected name collision — that one can't be waved through, it would double-count.