Why can't I just do this myself?

You can — if you have 80–120 hours to learn server-side GTM, debug iOS dedup edge cases, and stress-test EMQ across every conversion event. We do it in 7–10 days because we've done it 300+ times.

What if it doesn't work?

Two protections: (1) 95% tracking accuracy guarantee — we keep working free until your Meta Match Quality hits 8+. (2) You own the entire stack — server, container, runbook — on your accounts from day one.

Will Apple / Google break this in the future?

1st-party server-side tracking is what survives Apple, Mozilla, and Chrome cookie deprecation. The CAPI / Events API endpoints we use are how Meta, Google, and TikTok publicly committed to keeping the channel open.

ShoplazzaFor Shoplazza cross-border DTC stores

Get your Shoplazza tracking to 95%+ accuracy guaranteed in writing.

Shoplazza brands run aggressive paid acquisition on Meta, Google, TikTok, and increasingly Pinterest and Snap. Default integrations cover the basics, but EMQ stays low, dedup is broken across regions, and modeled conversions never light up. We build a Shoplazza-aware server-side stack that scales with your channel mix.

Get my free conversion tracking audit See what we check

Free30 minutesNo obligation

By Ariful IslamHow Shoplazza works ↓

Shoplazza · what breaks

Where Shoplazza tracking lags

01
Native integrations cover basics only
Low EMQ across channels.
02
TikTok / Pinterest under-served
Native plugins miss critical match params.
03
Multi-region complexity
EU + US + LATAM + APAC each need their own routing.

Shoplazza · the fix

Outcomes — Shoplazza

Multi-channel server-side CAPI
Meta + Google + TikTok + Pinterest.
Region-aware routing
Per-region ad-account dispatch.
EMQ 8+
Across all channels.

Shoplazza · architecture

How a Shoplazza order should reach the ad platforms

Shoplazza is built for cross-border selling, which means multi-currency and multi-region handling are not edge cases here — they are the default condition.

1
Click identifiers captured at first touch
Click IDs are captured in the theme at landing and written to a first-party cookie, surviving the region and currency redirects that a cross-border store performs routinely.
2
The browser sends the fast, fragile copy
Theme code and Shoplazza's app layer fire browsing and cart events. The checkout is hosted, so browser-side purchase tracking is limited.
3
The order itself is the source of truth
The Shoplazza order webhook is the truth, and it is the only place where the order's true settlement currency is unambiguous.
4
A server container sends the authoritative event
The order webhook posts to a GTM server container on your own subdomain, keyed on the Shoplazza order number, with currency normalized before it fans out.
5
Customer identity raises match quality
The order carries email, phone and shipping address, hashed server-side.

Shoplazza · events

The event set we build on Shoplazza, and where each one comes from

Currency is the parameter that matters most on a cross-border store, and it is the one most often sent wrong.

Event	Fires when, on Shoplazza	Key parameters	Sent from
view_item	A product page renders	item_id, value, currency, event_id	Browser + server, deduped
add_to_cart	The cart updates	item_id, quantity, value, currency, event_id	Browser + server, deduped
begin_checkout	The hosted checkout is entered	value, currency, num_items, event_id	Browser + server, deduped
purchase	The order webhook fires against a paid order	order_id, value, currency, items[], hashed email/phone/name/address, event_id	Server authoritative
refund	A refund is recorded	order_id, value, currency	Server only

Shoplazza · normal or broken

Cross-border specifics — Shoplazza

Multi-currency is where Shoplazza tracking goes wrong most often.

Normal, not a fault

Displayed currency differing from settlement currency
A cross-border store shows local prices and settles in one currency. Both numbers are real; they answer different questions.
Regional storefront variants reporting separately
Correct behavior for a multi-region store.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.

Actually broken

Conversion value sent in display currency with no currency parameter
Bidding treats every currency as the same unit and optimizes toward whichever market has the largest numbers.
Purchase tracked only from the confirmation page
Orders lost when the buyer leaves after payment.
Region redirects stripping click IDs
Attribution is lost at the moment of landing, before anything else can go wrong.

Shoplazza · prove

How we prove the Shoplazza build is correct

The tag firing proves the tag fires. These prove the numbers are right.

Source of truth

Shoplazza order records

Currency explicitly present and correct on every conversion, verified across at least two markets.
Click IDs confirmed surviving a region redirect.
The order webhook confirmed delivering with the order number present.
Purchase count within a few percent of shoplazza order records for a fully closed week, matched on order ID rather than on totals.
No order ID appearing twice in any platform's event log.
Deduplication confirmed at every destination that supports it.
Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.

Shoplazza · free audit

What we check in the free audit

Native integrations cover basics only
TikTok / Pinterest under-served
Multi-region complexity

Checked against

Shoplazza order records

Get my free conversion tracking audit

Free30 minutesNo obligation

Shoplazza · when not to buy

When a Shoplazza rebuild is not what you need

We would rather say this now than three weeks into an engagement.

You sell in one market and one currency at low volume.
You are testing the platform rather than committed to it.
Your ad spend is small enough that the currency normalization work outweighs the return.

Shoplazza · what we deliver

Deliverables — Shoplazza

Server-side GTM
Multi-region
Multi-channel CAPI
Meta + Google + TikTok + Pinterest
Shoplazza dataLayer
Theme-safe
QA + Notion runbook
Plus 30-day support

Written guarantee

95%+ tracking accuracy

Measured against Shoplazza order records. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Foundation pixel install for your Shoplazza store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.

One-time fee · zero monthly · zero SaaS lock-in
Shoplazza dataLayer (clean spec)
GA4 e-commerce events
Meta Pixel · Google Ads tag
TikTok Pixel · Microsoft UET
Consent Mode v2 banner integration
QA test orders + 7-day support
No CAPI · no iOS recovery

Lock in the one-time price

1st-party server-side

Recommended

$800One-time fee · most popular

The done-for-you package every Shoplazza store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.

One-time fee · save vs SaaS subscriptions over 5 years
Fully recovered + built in 2–4 days · accurate data in 7 days
Everything in browser-side starter
1st-party server-side GTM (your subdomain)
Meta CAPI · full advanced matching · 8+ EMQ
Google Enhanced Conversions (Web + Leads)
TikTok Events API · Microsoft UET server
Deterministic browser ↔ server deduplication
Live EMQ verification + screenshots
Notion runbook + 30-day support · zero recurring

Lock in the one-time price

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel running 1st-party server-side, end-to-end. For Shoplazza brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.

One-time fee · save 6-figure SaaS subscriptions over 5 years
Everything in 1st-party server-side tier
Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
Klaviyo identity stitching (if used)
BigQuery export (server logs + GA4)
Looker Studio attribution dashboard (branded)
Multi-region / multi-currency / EU residency
GDPR-audit-ready Consent Mode v2 wiring
60-day support · optional retainer · no lock-in

Lock in the one-time price

FAQ

Shoplazza questions, answered

Yes. We deploy region-specific gateways (EU + US + APAC) as needed.

Free · 30 min

Free Shoplazza tracking audit

Book a free audit

Free30 minutesNo obligation

Get your Shoplazza tracking to 95%+ accuracy guaranteed in writing.

Where Shoplazza tracking lags

Native integrations cover basics only

TikTok / Pinterest under-served

Multi-region complexity

Outcomes — Shoplazza

Multi-channel server-side CAPI

Region-aware routing

EMQ 8+

How a Shoplazza order should reach the ad platforms

Click identifiers captured at first touch

The browser sends the fast, fragile copy

The order itself is the source of truth

A server container sends the authoritative event

Customer identity raises match quality

The event set we build on Shoplazza, and where each one comes from

Cross-border specifics — Shoplazza

How we prove the Shoplazza build is correct

What we check in the free audit

When a Shoplazza rebuild is not what you need

Deliverables — Shoplazza

Server-side GTM

Multi-channel CAPI

Shoplazza dataLayer

QA + Notion runbook

Pick the package that fits your ad spend

Browser-side starter

1st-party server-side

Full 1st-party stack

Shoplazza questions, answered

Cross-border data residency?−

More on Shoplazza

Free Shoplazza tracking audit