Sytrics
Solutions/E-commerce
πŸ›’ E-commerce Microconversions

Your purchase data is the tip of the iceberg. Most of the signal is invisible.

The moment a user adds to cart, compares variants, or opens your size guide β€” they are signaling buying intent your ad platforms never see. Sytrics maps the full picture.

73%
of stores track only purchase as a conversion signal
Missing the entire consideration funnel
18
average microconversion events Sytrics identifies per e-commerce site
vs. 3–5 in a typical manual setup
35%
of add_to_cart events result in purchases (industry average)
The other 65% are retargeting opportunities

Figures are illustrative industry benchmarks, not Sytrics customer data.

Why your current tracking misses most of the buying signal

Standard analytics setups track the beginning and the end of the funnel: pageview and purchase. Everything in between β€” the consideration, the hesitation, the comparison β€” is invisible. In e-commerce, that middle is where most of the decision-making happens.

πŸ‘
You see page visits, not product intent

A user who views your product page 3 times in 2 days is behaving completely differently from one who viewed it once. Standard tracking treats them identically.

🧩
Checkout friction is invisible

You see order completions and order abandonment, but not where in the checkout flow users are dropping. Is it at shipping? Payment? A promo code field? You don't know.

πŸ”
Retargeting signals are shallow

If you only send purchase events to Meta, your Advantage+ audiences are trained on your existing buyers β€” not the 65% who added to cart and left. You are optimizing for the wrong audience.

The e-commerce microconversion funnel

Each stage represents a distinct intent level. Events within a stage are not equal β€” some are far stronger predictors of purchase than others.

DiscoveryIntent: Low
view_item_listsearch_queryfilter_applycategory_browse
ConsiderationIntent: Medium
view_itemimage_zoomsize_guide_openvariant_selectreview_read
Purchase IntentIntent: High
wishlist_addadd_to_cartcart_viewcheckout_start
ConversionIntent: Highest
shipping_info_addpayment_info_addpurchase
Post-PurchaseIntent: Loyalty
order_trackreview_submitreorder_intentloyalty_signup

Events shown are illustrative examples. Sytrics detects the specific events relevant to your store.

Five events most stores get wrong

These events are either untracked, misconfigured, or not connected to ad platform audiences in most e-commerce setups.

variant_select

User actively comparing product options

Why it matters

Variant selection indicates deeper product engagement than a standard page view. Users comparing sizes, colors, or configurations are evaluating β€” not just browsing.

⚠ Common mistake

Ignored entirely in most GA4 setups. Often not mapped to Meta or Google at all, despite being one of the strongest consideration signals.

Platform relevance
  • Β·Meta (ViewContent variant)
  • Β·GA4 (select_item)
  • Β·TikTok (ViewContent)
size_guide_open

Hesitation signal β€” considering purchase but unsure of fit

Why it matters

Opening a size guide predicts cart addition far better than a standard product view. This is a buyer who wants to purchase but needs one more piece of information.

⚠ Common mistake

Almost universally untracked. Most teams assume this is a UX interaction, not a conversion signal.

Platform relevance
  • Β·Meta custom event
  • Β·GA4 (custom)
  • Β·Not in TikTok standard schema β€” use custom
add_to_cart

Explicit purchase intent β€” highest pre-purchase signal

Why it matters

Add to cart is the single most predictive pre-purchase microconversion. Even users who abandon carts after this have shown commercial intent your ads can re-engage.

⚠ Common mistake

Frequently double-fired in SPAs. If your cart uses async state updates, you may be sending duplicate events to Meta, inflating retargeting costs.

Platform relevance
  • Β·Meta (AddToCart β€” standard)
  • Β·Google (add_to_cart)
  • Β·TikTok (AddToCart)
  • Β·Pinterest (AddToCart)
checkout_step

Funnel stage progression β€” each step reduces churn

Why it matters

Treating checkout as a single event loses the ability to identify where users drop off. Step 1 (shipping) to Step 2 (payment) drop-off often reveals UX friction, not low intent.

⚠ Common mistake

Only firing `begin_checkout` and `purchase` with nothing in between. You cannot optimize what you cannot see.

Platform relevance
  • Β·GA4 (begin_checkout, add_shipping_info, add_payment_info)
  • Β·Meta (InitiateCheckout)
wishlist_add

Future-purchase intent β€” high lifetime value signal

Why it matters

Wishlist additions are underused retargeting gold. These users have explicitly said 'I want this, just not now.' Remarketing to them with pricing or stock alerts is high-ROI.

⚠ Common mistake

Not connected to any retargeting audience in most setups. Sitting in GA4 as a custom event nobody acts on.

Platform relevance
  • Β·Meta (custom audience seed)
  • Β·Google (custom event)
  • Β·Klaviyo / email automation trigger

What Sytrics generates for your store

Enter your store URL. Sytrics analyzes your product pages, checkout flow, and site structure β€” then generates a complete, weighted event system.

15–25 detected events
Prioritized by conversion proximity for your specific funnel structure.
GTM container JSON
Import-ready file with all triggers, tags, and dataLayer variables pre-configured.
Platform-mapped outputs
Meta pixel + CAPI, Google GA4 enhanced e-commerce, TikTok, LinkedIn, and 4 more.
Event weight model
Each event gets a 0–100 importance score based on its conversion proximity in your funnel.
Implementation notes
Specific warnings about duplicate event risks, SPA considerations, and checkout-specific triggers.
Example output β€” illustrative
add_to_cart
MetaGoogleTikTok87
variant_select
MetaGA462
checkout_start
MetaGoogleTikTokPinterest91
add_payment_info
MetaGoogle95
wishlist_add
MetaKlaviyo44
// GTM Tag β€” add_to_cart dataLayer.push({ event: 'add_to_cart', ecommerce: { items: [{ item_id, item_name, price }] } })

Implementation pitfalls specific to e-commerce

These are the most common tracking mistakes we see in e-commerce setups β€” mistakes that corrupt your data and distort your ad optimization.

⚠
Firing purchase on confirmation page load

If your order confirmation page reloads on refresh, you will double-count purchases. Always deduplicate using order ID. Use Meta's deduplication_id parameter.

⚠
Treating all add_to_cart events equally

A user who adds a Β£400 item has different value than one who adds a Β£9 item. Pass value in your add_to_cart event. Most implementations don't.

⚠
Ignoring product list click data

view_item_list is mostly meaningless. select_item (clicking into a product from a list) is far more predictive. Most teams track the impression, not the click.

⚠
Single-page checkout with no step events

Modern checkout flows often happen in a single URL. If you only have pageview-based checkout tracking, you see nothing of what happens inside the modal or component.

⚠
No server-side purchase deduplication

Meta's CAPI and browser pixel both fire on purchase. Without deduplication logic, your reported conversions could be 50–100% inflated, destroying your bidding model.

⚠
Treating search as pure UX data

Search queries are intent goldmines. Users who search for specific product names, SKUs, or "in stock" queries are buyers. Almost no e-commerce stores pass this signal to their ad platforms.

FAQ

What's the difference between a microconversion and a macro conversion in e-commerce?

A macro conversion is your end goal β€” the purchase. Microconversions are the intent signals that predict it: add_to_cart, checkout_start, variant_select. Optimizing for microconversions gives your ad platform the signal volume to learn faster, especially in low-traffic situations where purchase data alone is sparse.

Should I pass all microconversions to Meta and Google, or just purchase?

In high-volume stores (1000+ purchases/month), purchases alone can be enough signal. Below that threshold, passing add_to_cart, begin_checkout, and add_payment_info to Meta improves optimization quality significantly. Google recommends passing all funnel events via enhanced e-commerce.

How does Sytrics handle custom checkout flows (headless, Shopify, custom SPA)?

Sytrics generates the event schema based on your site's structure. For single-page applications and headless checkouts, we detect the DOM and state change patterns and recommend the correct trigger approach β€” typically Custom Event triggers in GTM rather than pageview-based.

What's the right event weighting model for e-commerce?

A simple starting model: purchase (100), begin_checkout (60), add_payment_info (70), add_to_cart (40), wishlist_add (25), view_item (10). Adjust based on your conversion rates at each stage.

Is server-side tracking (CAPI) necessary for an e-commerce store?

For stores dependent on Meta advertising, yes. With iOS14+ limitations, browser-only tracking typically underreports conversions by 20–40%. CAPI with deduplication recovers most of this. Sytrics generates the server-side event schema alongside the browser snippet.

See every buying signal from your store

Enter your store URL. Sytrics maps the full microconversion funnel β€” 15–25 events, weighted, platform-mapped, GTM-ready.

Scan your store free