Pix on Shopify: why the sale happens and Meta and GA4 never find out

If your store sells with Pix on Shopify, there is a good chance that part of your sales never reaches Meta, GA4 or Google Ads. It is not a campaign bug, and it is not an attribution difference. It is an architecture problem: in the default setup, the purchase event is born in the customer’s […]

Wascer-TeamE-commerce15 Min. Lesezeit
Pix na Shopify: Luiz, da Wascer, com o celular na mão perguntando onde está a venda paga no Pix
Pix on Shopify: Luiz from Wascer holding his phone, asking where the sale paid with Pix went

If your store sells with Pix on Shopify, there is a good chance that part of your sales never reaches Meta, GA4 or Google Ads. It is not a campaign bug, and it is not an attribution difference. It is an architecture problem: in the default setup, the purchase event is born in the customer’s browser, on one specific page, and the Pix payment happens outside of it.

Pix is Brazil’s instant payment system, run by the Central Bank: the customer pays with a QR code or a copy-and-paste code from their banking app. A store that came to Wascer shows the size of the problem. In a single day, it recorded 40 orders. GA4 counted 30 purchases. Meta’s Events Manager also counted 30. Ten paid orders, a quarter of the day’s sales, simply did not exist for the ad platforms. The store runs on Shopify, and most of the gap was in the Pix flow.

With Pix behind almost 80 billion transactions in Brazil in 2025, according to Central Bank data released by the Ministry of Finance, this is no longer an edge case. For anyone selling with Pix on Shopify, it is the payment method that weighs most at checkout, and it is exactly the one that breaks measurement the most.

How Shopify records a purchase in the browser

With Checkout Extensibility, measurement in Shopify’s checkout moved to Web Pixels: pixels installed by apps (such as Meta’s, Google’s and TikTok’s) and custom pixels listen to the standard checkout events. The event that represents the purchase is checkout_completed.

Shopify’s documentation is direct about when it happens: the event is triggered once per checkout, typically on the Thank you page. And it adds: if the page where the event is supposed to be triggered fails to load, checkout_completed isn’t triggered at all.

Read that sentence again with Pix in mind. The purchase event that feeds your Pixel and your GA4 tag depends on one condition: the customer’s browser has to load the thank you page. It does not matter that the money has already arrived. If the page did not load in that browser, the purchase does not exist for the tags running in it.

There is one more detail that tends to confuse whoever audits the account: in stores with a post-purchase offer (upsell), the event fires on the first offer page instead of the thank you page. The logic is the same: a page has to load in the browser.

Where Pix on Shopify breaks the chain

With a credit card, approval takes seconds, inside the checkout itself, and the customer almost always lands on the thank you page. Pix on Shopify works differently.

  1. The customer places the order and gets a QR code or a copy-and-paste code. With Pix apps for Shopify, such as Mercado Pago’s, they are taken to a dedicated screen with the QR code; with gateways such as Asaas, they pay on the gateway’s page and only then are sent to Shopify’s thank you page.
  2. They leave the browser, open their banking app (often on another device) and pay.
  3. The payment is confirmed asynchronously. Shopify’s own payments documentation provides a pending state for payments awaiting an action from the customer or the payment network, resolved later as successful or failed.
  4. For checkout_completed to fire, the customer has to come back to the browser and the thank you page has to load.

Step 4 is the weak link of Pix on Shopify. Whoever paid on their phone and closed the tab, whoever scanned the QR code shown on the computer with their phone and never looked at that screen again, whoever lost the connection on the way back from the gateway: in all of these cases the order is paid, its financial status changes from pending to paid in the Shopify admin, and no purchase event is generated in the browser. No Pixel can work around this, because there is no loaded page for the Pixel to run on.

The exact return behavior varies from gateway to gateway and from setup to setup. What does not vary is Shopify’s rule: no loaded page, no event.

What happens after the order

Pixel in the browser

orders/paid webhook on the server

Card approved at checkout, customer sees the thank you page

Records the purchase

Records the purchase (deduplicated by order id)

Pix paid, customer returns and the thank you page loads

Records the purchase

Records the purchase (deduplicated by order id)

Pix paid in the banking app, customer closes the tab

Does not record

Records the purchase

Pix QR code shown on the computer, paid on the phone, no return

Does not record

Records the purchase

Gateway return fails or the connection drops

Does not record

Records the purchase

Pix generated but not paid

Does not record

Does not record (the order is not paid)

Why this costs more than a wrong report

The gap between 40 and 30 does not stay on the dashboard. It enters your decisions in three ways.

Optimization. Meta and Google Ads conversion campaigns learn from the purchase events they receive. If 25% of purchases never arrive, the algorithm learns from a smaller, skewed sample: the buyers who came back to the thank you page. Whoever paid with Pix on Shopify and did not come back drops out of the learning, and the audience that buys the most with Pix starts to look less valuable than it is.

Cost per acquisition. The CPA you read in the ads manager is spend divided by recorded conversions. With conversions missing, CPA looks inflated, and campaigns that pay for themselves look like they lose money.

Channel reading. In GA4, a purchase that never arrived is attributed to no channel. Store revenue does not match Analytics revenue, and the conversation about which channel works starts with the wrong number.

What changed on Shopify in 2025 and 2026

For years, the workaround was to paste scripts on the order status page, which the customer could reopen from the email link. That path is closed.

According to Shopify’s documentation, checkout.liquid and additional scripts were sunset on the Thank you and Order status pages on August 28, 2025. Script tags on those pages were sunset on the same date for Plus stores and on August 26, 2026 for all other stores. The additional scripts section in checkout settings became view-only.

In practice, all browser measurement after the purchase now goes through Web Pixels, and Web Pixels depend on the page loading. For Pix on Shopify, the workaround is over. What remains is measuring where the sale is actually recorded: the server.

Want to know how many Pix on Shopify sales your store is failing to measure? Talk to Wascer.

The fix for Pix on Shopify: the purchase comes from the server, not from the thank you page

The paid order lives somewhere that does not depend on a browser: Shopify’s backend. And Shopify tells you when it changes state. The orders/paid webhook occurs whenever an order is paid. That signal is what should trigger the purchase event.

The architecture looks like this:

  1. Shopify sends the orders/paid webhook to your endpoint, with the order data: id, total, currency, line items, email, phone, IP and user agent of the browser the order was placed in, plus the order attributes.
  2. A server-side Google Tag Manager container receives the request. In server GTM, what receives a request is a client; the official clients API lets you claim the request, read its body and run the container with that data. That is how a webhook becomes an event inside the container. At Wascer, this is the job of the Wascer Data Client, which receives and processes webhooks in sGTM.
  3. The container tags send the purchase to Meta’s Conversions API, to GA4’s Measurement Protocol and to Google Ads, each in the format the platform requires.
Pix on Shopify: browser-only flow that loses the sale compared with the server-side flow using the orders/paid webhook, sGTM and Meta, GA4 and Google Ads

The customer can close the tab, pay on another device or come back the next day. The purchase is sent when the payment is confirmed.

Meta: what the Conversions API needs

For a website event sent from the server, Meta requires event_name, event_time and user_data, and treats event_source_url and client_user_agent as required. action_source must be website.

The points that decide whether the sale will be put to good use:

  • event_time within 7 days. Meta accepts events up to 7 days late. A Pix paid hours after the order fits easily.
  • event_id equal to the order id. Meta deduplicates Pixel and server events by the event_id + event_name pair, as long as they arrive within 48 hours of each other. If the customer came back to the thank you page and the Pixel fired, the server event with the same id is discarded. If they did not, the server event is the only recorded purchase. No sale is counted twice and none is left out.
  • Hashed customer data. Email and phone are sent as SHA-256, normalized first: email trimmed and lowercase; phone digits only, with the country code (55 for Brazil). IP and user agent are sent unhashed.
  • fbp and fbc. These are the identifiers from the _fbp and _fbc cookies. Without them, Meta has less signal to tie the purchase to the ad click. They have to be captured in the browser and stored in the order (see below).

A purchase event built from the webhook looks like this (example values):

plaintext
POST https://graph.facebook.com/{version}/{PIXEL_ID}/events

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1760906400,
      "event_id": "5550001112223",
      "action_source": "website",
      "event_source_url": "https://yourstore.com/",
      "user_data": {
        "em": ["<SHA-256 of the normalized email>"],
        "ph": ["<SHA-256 of the phone with 55>"],
        "client_ip_address": "203.0.113.10",
        "client_user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 18_0 like Mac OS X) ...",
        "fbp": "fb.1.1760900000000.1234567890",
        "fbc": "fb.1.1760900000000.IwAR..."
      },
      "custom_data": {
        "currency": "BRL",
        "value": 189.90,
        "order_id": "5550001112223"
      }
    }
  ]
}

The event_id is the Shopify order id. IP and user agent come from the order itself, which stores the data of the browser the purchase was made in. fbp and fbc come from the attributes stored in the cart.

Meta recommends using the Conversions API in addition to the Pixel, sharing the same events through both. This is not about turning the Pixel off; it is about no longer depending on it alone.

GA4: Measurement Protocol and the 24-hour limit

The purchase event in the Measurement Protocol requires transaction_id, value, currency and items. The transaction_id must be the order id: GA4 deduplicates purchases with the same transaction ID, so a purchase that arrived from both the browser and the server is counted once.

Here is the detail that separates a good implementation from one that just fills a report: to attribute the purchase to the original session, the request must carry the session_id and be sent no later than 24 hours after the session starts. Without it, the revenue reaches GA4, but the source of the sale is lost. The Measurement Protocol accepts events backdated up to 72 hours.

The same order, sent to GA4 (example values):

plaintext
POST https://www.google-analytics.com/mp/collect?measurement_id=G-XXXXXXXXXX&api_secret={SECRET}

{
  "client_id": "1234567890.1760900000",
  "events": [
    {
      "name": "purchase",
      "params": {
        "session_id": "1760900000",
        "transaction_id": "5550001112223",
        "value": 189.90,
        "currency": "BRL",
        "items": [
          { "item_id": "SKU-123", "item_name": "Product", "price": 189.90, "quantity": 1 }
        ]
      }
    }
  ]
}

The client_id is the value of the _ga cookie without its prefix, and the session_id comes from GA4’s session cookie. Both must have been stored in the order before payment.

To send the conversion to Google Ads from the server, the click identifier has to be in the order. Conversion import uses the gclid (and, when available, gbraid and wbraid), which must be stored with the customer record, with auto-tagging on. Enhanced conversions add email and phone hashed with SHA-256, with the phone in the international E.164 format.

The detail that decides attribution: store the browser inside the order

The webhook knows everything about the order, but not which ad it came from. That information lives in browser cookies. The fix is to capture it before payment and store it in the order:

  • _fbp and _fbc (Meta);
  • the client_id from the _ga cookie and the session_id (GA4);
  • gclid, gbraid or wbraid (Google Ads).

On Shopify, this is done by saving these values as cart attributes, which travel with the order and arrive in the webhook. With them, the server event carries the same level of identification as a browser event, without depending on the thank you page.

Take extra care with Safari and iPhone. WebKit’s Intelligent Tracking Prevention deletes cookies created in JavaScript after 7 days without interaction with the site, and caps cookies created in JavaScript on the landing page to 24 hours when the URL arrives with click parameters. That is why Google recommends serving the server-side container on your own domain: collection happens in your site’s context, not on a third-party domain.

How to test Pix on Shopify tracking

Do not trust the dashboard before forcing the scenario that breaks. The test reproduces exactly the problem:

  1. Place a test order with Pix and pay on your phone. After paying, close the checkout tab without returning to the thank you page.
  2. Shopify: confirm the order changed to paid in the admin.
  3. Meta: in Events Manager, use the test events tab (the server sends the test_event_code during the test) and confirm the Purchase arrived from the server, with event_id equal to the order id.
  4. GA4: before turning on real sending, send the same body to the Measurement Protocol validation endpoint (/debug/mp/collect). It returns validation messages instead of recording the event. Then check the purchase in the report by the order’s transaction_id.
  5. Repeat, this time returning to the thank you page. Now the Pixel and the server send the same purchase. In Meta and GA4 it must appear only once. If it appears twice, event_id or transaction_id do not match across both paths.

How to tell if Pix on Shopify is taking sales out of your reports

Checklist to find out whether Pix on Shopify is taking sales out of Meta and GA4

You do not need any tool to find out. Pick a day with volume and compare:

  1. Shopify admin: paid orders that day, split by payment method.
  2. Meta Events Manager: Purchase events on the same day.
  3. GA4: purchases (purchase) on the same day, in the monetization report.

If the gap between Shopify and the platforms is concentrated in Pix orders, you found the thank you page. If it also shows up for card payments, there are other loss points along the way, such as ad blockers and consent, which server-side tracking also helps with.

How Wascer fixes Pix on Shopify

Wascer launches and monitors a server-side Google Tag Manager container in one click: no DevOps, no Docker and no command line. You paste the container ID and get an active, monitored and scalable tagging server.

For Shopify, the Sourei Wascer app sends store data to the container through webhooks, and the Wascer Data Client processes those webhooks inside sGTM, so the tags can use the order data. In the container, Wascer provides dedicated Meta, GA4 and Google Ads tags to send the purchase the way each platform requires, using the order id to deduplicate. Pix sales are recorded when they are paid, not when the customer remembers to go back to the thank you page.

Learn what Wascer is and how it works, visit wascer.com or create your account.

Frequently asked questions

Is every Pix on Shopify sale lost?

No. If the customer returns and the thank you page loads, checkout_completed fires and the Pixel records the purchase. The loss happens when the page does not load, and with Pix that is much more frequent than with cards, because payment happens outside the browser.

Will sending the purchase from the server duplicate conversions?

No, as long as the order id is used as event_id in Meta and as transaction_id in GA4. Both platforms deduplicate by those fields.

Do I need to remove the Meta Pixel from the store?

No. Meta itself recommends using the Conversions API together with the Pixel. The Pixel keeps capturing what happens in the browser; the server guarantees the purchase.

How long after the order can the purchase still be sent?

In Meta, up to 7 days after event_time. In GA4, to keep session attribution, up to 24 hours after the session starts.

Does this also solve ad blockers?

It helps. Since the purchase event comes from the server, it does not depend on a script loading in the browser. Capturing the click identifiers, however, still happens in the browser, which is why the container’s own domain makes a difference.

Conclusion

With Pix on Shopify, the sale and the purchase event happen in different places. The sale happens in the customer’s bank and is confirmed on Shopify’s server. The purchase event, in the default setup, depends on a page loading in a browser the customer may never reopen. As long as measurement depends on that page, part of your sales will stay invisible to the algorithm that decides where your budget goes.

Moving the purchase to the server is not fine-tuning. It is the difference between optimizing with 30 sales or with 40.

Want to see how many Pix on Shopify sales your store is failing to measure? Talk to Wascer.

Wascer: rastreamento server-side

By Wascer

Wascer launches and monitors your server-side Google Tag Manager container in one click: no DevOps, no Docker and no command line. Technical content on tracking, Meta, GA4 and Google Ads for teams that decide with data. wascer.com

Sources

Wascer-Team · Veröffentlicht am 20.10.2026 · aktualisiert am 06.11.2026

Weiterlesen

Alle Artikel
11 NOVGoogle Data Manager API: O Futuro do Envio de Dados para o Google Ads30 OKTMeta Ads and GA4 don’t match: when the gap is normal and when it’s lost data26 OKTWrong Google Ads conversion value: why it happens and how to fix it