Skip to main content
Snapchat · EcommerceSnapchat × Ecommerce

Snapchat Ads conversion tracking for ecommerce brands

An ecommerce brand has one unambiguous source of truth — the orders in its store — and almost every measurement problem is a discrepancy against it. What Snapchat Ads adds on top of that is a mechanical requirement: the ScCid click identifier has to reach the record that holds the money, because Snapchat can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in ecommerce brands, and what Snapchat specifically needs to accept it.

Free30 minutesNo obligation

Specific to Snapchat × Ecommerce

Snapchat for ecommerce: PURCHASE from the order for Gen Z shoppers

For an ecommerce brand selling to under-30s, send Snapchat's PURCHASE event through the Snapchat Conversions API from the order record, with the order ID as the shared event identifier, the ScCid persisted server-side at landing, and hashed email and phone from the order. Treat the pixel as secondary, since Snapchat's in-app browser often drops it.

Snapchat fits ecommerce brands whose buyers are teens and young adults: streetwear, beauty, fragrance, phone accessories, gaming gear, beverages. If your typical customer is 45, the channel is the wrong test. For the right brand, the purchase happens fast and on mobile, usually through Apple Pay, Shop Pay or PayPal inside the in-app browser.

Those wallet flows are where Snapchat loses purchases. The wallet sheet completes the payment, the in-app browser may never load the confirmation page, and the pixel does not fire. Sending PURCHASE from the order webhook catches those orders, and the ScCid stored server-side at landing is what lets them match back to the ad instead of arriving as unattributed server events.

Age matters for policy as well as fit. Snapchat restricts ads for some product categories by age and region, alcohol and certain supplements among them, so beverage and wellness brands should confirm what is allowed before building measurement around a campaign that may be limited. Young shoppers also check out with a parent's card and email, so some orders carry contact details that will never match the Snapchat user.

Snapchat · Ecommerce · what breaks

Why Snapchat under-reports for ecommerce brands

  1. 01

    Four dashboards, four revenue figures

    Summing to more than was banked, with nobody able to say which to use.

  2. 02

    Reported ROAS better than the bank statement

    Which is how the problem usually gets noticed.

  3. 03

    Refunds never reversed

    So the reported number drifts further from reality with your return rate.

  4. 04

    The ScCid click identifier never reaches the record

    Snapchat appends its click identifier to your landing page URL, and matches additionally on hashed email, phone and mobile advertising IDs. The environment is what makes this hard: traffic arrives inside Snapchat's in-app browser, whose storage behavior is inconsistent, so an identifier captured into a cookie rather than persisted server-side frequently is not there when the conversion happens.

Snapchat · Ecommerce · the fix

What working looks like — Snapchat · Ecommerce

  • One order, one conversion

    Deduplicated on the order ID at every destination.

  • Revenue that reconciles to the store

    Per order, over a closed window.

  • Refunds and cancellations reversed

    So the number can go down as well as up.

Snapchat · Ecommerce · architecture

How Snapchat and ecommerce brands actually connect

  1. 1

    The conversion in ecommerce brands

    Purchase is the money event, but the funnel above it matters for optimization: product view, add to cart, checkout started, payment info submitted. Each gets a definition and a firing rule before anything is built.

  2. 2

    Snapchat Ads needs a click to match

    An event name Snapchat recognizes, a shared event identifier if you are also running the pixel, a timestamp, hashed customer information, and the click identifier where you have it.

  3. 3

    The identifier: the ScCid click identifier

    Snapchat appends its click identifier to your landing page URL, and matches additionally on hashed email, phone and mobile advertising IDs. The environment is what makes this hard: traffic arrives inside Snapchat's in-app browser, whose storage behavior is inconsistent, so an identifier captured into a cookie rather than persisted server-side frequently is not there when the conversion happens.

  4. 4

    Where it gets sent from

    your store's order records, web orders only.

  5. 5

    Deduplication and window

    Same shape as Meta: the browser pixel and the server event must carry the same identifier for the same conversion. Given how much Snapchat traffic never runs the pixel successfully, some advertisers here send server-side only — which is a defensible choice on this audience and removes the deduplication problem entirely. Snapchat's attribution windows are configurable and its defaults differ from Meta's. Confirm what your account is set to before reconciling anything, and verify the accepted event-freshness limit for server events against current documentation.

Snapchat · Ecommerce · events

The conversion map for ecommerce brands

Five events, one of which decides the money. The others exist so bidding has enough volume to learn from.

Product viewHigh volume, browser-side is fine. Feeds retargeting and catalog matching.
Add to cartBrowser-side. The first real intent signal and useful for audience building.
Checkout startedBrowser-side. Where the drop-off analysis lives.
PurchaseServer-side, from the order record. This is the one that has to be right.
RefundServer-side, from the refund webhook. Almost never implemented, and it's why revenue only climbs.

Snapchat · Ecommerce · diagnose

Diagnostic order — Snapchat · Ecommerce

  1. 01

    Count records carrying the ScCid click identifier

  2. 02

    Wallet payments skipping the confirmation page

    Shop Pay and PayPal can be abandoned after payment. The order exists and no platform hears about it.

  3. 03

    Two apps both sending purchase

    A channel integration plus a container is two conversions for one sale.

  4. 04

    Non-web orders in the comparison

    POS, draft and phone orders belong in your total and not in a platform reconciliation.

  5. 05

    Read the events received and matched in Snapchat Ads Manager, reconciled against your own records

    Snapchat skews young and almost entirely mobile. If your buyer is not in that profile, no measurement work makes the channel viable — and that is a media planning conversation rather than a tracking one, worth having before anyone builds.

Snapchat · Ecommerce · prove

How it gets proven — Snapchat · Ecommerce

Source of truth

your store's order records, web orders only

  • Order ID present in every destination's event log.
  • Purchase count within a few percent of web orders for a closed week.
  • No order ID appearing twice anywhere.
  • A real refund tested and confirmed reversing.

Snapchat · Ecommerce · free audit

What we check in the free audit

  • Count records carrying the ScCid click identifier
  • Wallet payments skipping the confirmation page
  • Two apps both sending purchase
  • Non-web orders in the comparison
  • Read the events received and matched in Snapchat Ads Manager, reconciled against your own records

Checked against

your store's order records, web orders only

Get my free conversion tracking audit

Free30 minutesNo obligation

Snapchat · Ecommerce · when not to buy

When you don't need this — Snapchat · Ecommerce

  • If Snapchat already reports conversions that reconcile against your store's order records within a few percent, this is working and there is nothing to buy.
  • Measure identifier coverage yourself first — pull your last hundred records and count how many carry the ScCid click identifier.
  • If your customers are not in Snapchat's age profile, the channel is the wrong question. We would rather say that than build measurement for a campaign that cannot work.

Snapchat · Ecommerce · what we deliver

What gets built — Snapchat · Ecommerce

  • Purchase from the order webhook

    Not from a thank-you page a customer can skip or refresh.

  • Order ID as the deduplication key

    Stable and identical on every path without coordination.

  • Customer parameters hashed from the order

    Normalized before hashing, which is where match quality is usually lost.

  • Refund webhook wired as a reversal

    At every destination that accepts one.

  • Dispatch via the Snapchat Conversions API

    Server events posted to Snapchat's Conversions API carrying the click identifier and hashed customer information. Verify the current endpoint and required field names against Snapchat's own documentation before building rather than trusting an older integration guide.

Written guarantee

95%+ tracking accuracy

Measured against your store's order records, web orders only. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Snapchat · Ecommerce questions, answered

For products bought by teens and young adults, yes; for older buyers it rarely works. Check your customer age data before committing budget.

Free · 30 min

Get Snapchat reporting what ecommerce brands actually earn

Free30 minutesNo obligation