BLIK & Przelewy24 GA4 Tracking: Fix Missing Purchases on Shopify, WooCommerce & Shoper
In Poland, BLIK is the unrivaled king of digital payments, powering over 70% of all online ecommerce transactions. Whether shoppers are buying on Shopify, WooCommerce, PrestaShop, or Shoper, generating a 6-digit BLIK code and confirming the push notification on their banking app (PKO IKO, mBank, Santander, ING, Bank Millennium) is the default national payment behavior.
However, for Polish eCommerce managers, DTC brand owners, and performance marketing agencies in Warsaw, Kraków, and Wrocław, BLIK and payment gateways like Przelewy24 (P24) and PayU create severe attribution nightmares:
- The Mobile Push Drop: Over 25% of shoppers complete their BLIK payment inside their banking app and never return to the web store’s thank-you page. Standard client-side Google Tag Manager (GTM) purchase tags never execute.
- Referral Hijacking: When payment gateways redirect returning shoppers back to the store without proper referral exclusions, GA4 attributes the conversion to
przelewy24.plorpayu.plinstead of the original Google Ads or Meta Ads campaign. - AdBlock Erosion: Poland has one of Europe’s highest AdBlock adoption rates (exceeding 40%), meaning nearly half of your high-intent traffic runs with client-side tracking disabled.
In this guide, I share the exact technical implementation required to capture 100% of BLIK and Przelewy24 orders in Google Analytics 4 (GA4), Google Ads Enhanced Conversions, and Meta Conversions API (CAPI).
Key Takeaways for Polish Merchants & Agencies
- Filter Out Gateway Referrals in GA4: Add
przelewy24.pl,payu.pl,blikmobile.pl, and major banking domains to GA4’s List of Unwanted Referrals to prevent payment redirects from overwriting campaign attribution. - Overcome Browser Abandonment with Server-Side Tracking: Relying exclusively on thank-you page client tags guarantees that 20% to 30% of BLIK orders will be missing from ad reports. Deploying a Server-Side GTM container ensures every completed order is captured via backend webhook.
- Meta Pixel & CAPI Deduplication: Pass identical
transaction_id(order number) parameters across both browser tags and server-side webhooks to prevent duplicate conversion reporting in Meta Ads Manager. - Polish Złoty (PLN - zł) Precision: Ensure accurate net product value, 23% VAT (PTU), and shipping cost handling in PLN to prevent currency conversion discrepancies in Google Ads Smart Bidding.
Why BLIK Payments Break Traditional Analytics
The mechanics of a BLIK transaction reveal why standard client-side tracking fails:
[Google Ads Click] ──► [Shopify / WooCommerce / Shoper Store]
│
▼ [Checkout: BLIK Selected]
│ User enters 6-digit code
▼
[Switch to Banking App: mBank / IKO / ING]
│ User clicks "Confirm with PIN"
▼
[Payment Approved in Banking App]
│
┌────────────────┴────────────────┐
▼ ▼
[Customer closes phone] [Customer returns to store]
❌ NO THANK-YOU PAGE ⚠️ GATEWAY REDIRECT DETECTED
❌ 0% Event Tracking ⚠️ Risk of Referral Hijack
When the customer confirms payment on their phone, the money has changed hands. But if they do not manually switch back to the browser and wait for your thank-you page to load, your client-side tags remain completely dark.
Step 1: Configure Unwanted Referrals in GA4 Admin
To prevent returning shoppers from being categorized as referral traffic from the payment gateway, configure referral exclusions in GA4:
- Open Google Analytics 4 → Admin → Data Streams → Web Stream.
- Under Google tag, click Configure tag settings.
- Click Show more → List unwanted referrals.
- Add the following domains (Condition: Referral domain contains):
przelewy24.plpayu.plblikmobile.plautopay.pldotpay.pltpay.commbank.plpkobp.plsantander.pling.plmillennium.plaliorbank.pl
- Click Save.
This ensures that when a customer returns to your store from Przelewy24 or their bank, GA4 maintains their original session and attributes the purchase to the marketing channel (Google Ads, Meta, SEO) that initiated the visit.
Step 2: Ingesting Webhooks into Server-Side GTM
To capture the 25%+ of customers who never return to the thank-you screen after authorizing BLIK, you must implement Server-Side GTM (sGTM) with order status webhooks.
The Implementation Workflow:
- First-Party Tagging Endpoint: Deploy a Server-Side GTM container on your store’s custom subdomain (e.g.,
data.yourbrand.pl) hosted on Google Cloud in the Warsaw (europe-central2) or Frankfurt (europe-west3) region. - Order Webhook Trigger: Configure your store backend (Shopify Webhook, WooCommerce Action Hook, or Shoper Webhook) to dispatch an
order.paidJSON payload to your sGTM endpoint whenever a BLIK transaction is marked successful. - Server-Side Conversion Fanout:
- Google Analytics 4: Transmits a Measurement Protocol
purchasehit with the visitor’s originalclient_idand session ID. - Google Ads: Fires an Enhanced Conversion with SHA-256 hashed customer email, phone, and original
gclid. - Meta CAPI: Delivers a server purchase event with hashed contact parameters, achieving a 9.0+ Event Match Quality (EMQ) score.
- Google Analytics 4: Transmits a Measurement Protocol
[Store Backend / P24 Webhook] ───► [sGTM Container: data.yourbrand.pl]
│
┌────────────────────────────┼────────────────────────────┐
▼ ▼ ▼
[GA4 Measurement] [Google Ads OCT] [Meta CAPI]
Real-World Case Studies
Discover how server-side tracking, deduplication, and attribution modeling drive measurable revenue growth:
- E-Commerce Purchase Reconciliation: Learn how we eliminated order drop-offs in the Shopify & Google Ads Purchase Reconciliation Case Study.
- Meta Pixel & CAPI Deduplication: Discover how we fixed duplicate transactions in the Meta Pixel & CAPI Deduplication Case Study.
- European Cloud Residency on sGTM: See the technical infrastructure in the Server-Side GTM on Google Cloud EU Case Study.
Frequently Asked Questions
Can this setup work on Polish platforms like Shoper or PrestaShop?
Yes. On Shoper and PrestaShop, we deploy custom modules or webhooks that capture attribution tokens (gclid, _fbp, client_id) in browser storage and deliver them via server-to-server endpoints upon payment authorization.
Will server-side webhook tracking cause duplicate orders in GA4?
No. Because we use the store’s unique order_id as the transaction identifier across both browser and server payloads, GA4 and Meta Ads automatically deduplicate events received within a 48-hour window.
Does this comply with UODO and Polish data protection regulations?
Yes. Under UODO (Urząd Ochrony Danych Osobowych) and the Polish Telecommunications Law, sensitive personal data is protected because all customer telemetry (emails, phone numbers) is cryptographically hashed using one-way SHA-256 before transmission.
Related Tracking Services & Central European Hubs
- Central European Regional Hubs: Review our Poland GA4 services, Germany GA4 services, and Austria GA4 services.
- Diagnostic Utilities: Validate your tracking health with our Tracking Self-Audit or test your campaign tags with the Meta CAPI Validator.
- Book a Technical Audit: Schedule a free tracking consultation to inspect your BLIK, GA4, and Google Ads conversion tracking pipeline.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.
