Hivenue
All modules

Conversion Tracking

One snippet makes every visit first-party, a server-side outbox keeps Meta fed with purchases, checkouts and refunds, and an attribution table shows what actually sold. With an honest N/A for what it cannot prove.

AttributionCampaignsAdsetsAdsAura Skincare · same 30 days
Aura | Prospecting BroadSessions4,812Purchases96Conv. value€7,430CVR2.0%
Browser pixel alone
ROAS
2.1
Conv. value
€10.4k
Purchase · €89.90
Purchase · €54.00not tracked
Begin checkoutnot tracked
Purchase · €39.90
First-party pixel + Conversions API
ROAS
3.41.3
Conv. value
€16,840
browser pixel+ server-side
Purchase · €89.90sent to Meta
Purchase · €54.00sent to Meta
Begin checkoutsent to Meta
Refund · €39.90sent to Meta
More signal to Meta, better optimization
More reliable than the browser pixel alone
sent server-side · every 5 min
First-party pixel

One paste, and the data is yours

The snippet is generated for your store and pasted once into Shopify Customer events. No theme code, no tag manager, no re-installing after a redesign.

  • Paste once, track everythingA Custom Web Pixel covers your storefront and the checkout, where theme scripts cannot go. Authenticated with a store secret.
  • Private by constructionFirst-party, no third-party cookies. Visitor IPs are hashed with a daily-rotating salt and emails stored only as SHA-256.
  • Health at a glanceStatus and Last fired on every pixel, with Recent events and an Event trend chart to prove it is alive.
app.hivenue.co/tracking/install
Install the pixelStep 7 of 7

One snippet, generated for your store and signed with its secret.

// Hivenue pixel · generated for Aura Skincare
analytics.subscribe("all_events", (event) => {
hv.track(event, {
store: "aura-skincare",
secret: "whsec_····",
});
});
Copy snippetShopify → Settings → Customer events
Meta CAPI

Purchases, checkouts and refunds, straight from the server

An outbox collects commerce events and a cron drains it to Meta's Conversions API every 5 minutes. More reliable than the browser pixel alone, and it closes the loop with refunds.

  • An outbox, not fire-and-forgetEvents queue server-side and ship on schedule. A closed tab cannot lose a purchase.
  • PII hashed before it leavesIdentifiers are hashed before events go to Meta. Raw personal data stays out of the pipeline.
  • Verified in seconds, not daysCAPI Ingest charts your server-side events in real time, while Meta's own stats can lag 24 to 48 hours.
app.hivenue.co/tracking/capi
Meta · Conversions APICron · every 5 min
Server-side events

Send purchases, checkouts and refunds to Meta from the server. More reliable than the browser pixel alone.

Purchase €89.90#10249 · event_id ord_10249Queued
Begin checkout #10252 · event_id chk_10252Queued
Refund -€29.90#10214 · event_id rfd_10214Queued
PII hashed · SHA-256graph.facebook.com
Attribution

Drill from campaign to the ad that sold

Which campaign, ad set and ad drive sessions and sales (UTM). Select a row and the next tab filters to it, from Campaigns down to the single ad, with sessions, purchases and conversion value on every line.

  • Three levels, one selectionCampaigns, Adsets, Ads. Pick a row and the next tab shows only what is inside it.
  • Money columns by defaultSessions, adds to cart, checkouts, purchases and their conversion value, with CVR% and a Totals footer.
  • The honest N/A rowSessions without UTMs are never assigned to a winner. They sit in their own row, in plain sight.
app.hivenue.co/analytics/ads
AttributionWhich campaign, ad set and ad drive sessions and sales (UTM)MetaAll sources
CampaignsAdsetsAds
ValueSessionsTotal purchasesTotal purchases conversion valueCVR%

Works with

ShopifyMeta

Questions, answered

Paste one snippet into Shopify Admin under Settings → Customer events. It runs as a Custom Web Pixel, so there is no theme code to maintain: it survives theme changes and covers the checkout, where theme scripts cannot go. The snippet is generated for your store, authenticated with a secret, and the setup wizard walks you through the paste.

See Conversion Tracking on your store.

Fifteen minutes, your data, the whole suite around it.