Ecommerce

How to Fix iDEAL & Wero Payment Tracking Drops in GA4 and Google Ads

In the Netherlands, iDEAL is the undisputed backbone of digital commerce, accounting for over 70% of all online transactions. As iDEAL transitions into Wero (the pan-European digital wallet initiative backed by the European Payments Initiative), payment authentication is becoming even more app-driven and mobile-centric.

Yet for Dutch and Belgian online stores—whether running on Shopify, WooCommerce, Lightspeed, or Magento—iDEAL is notorious for destroying digital marketing attribution in Google Analytics 4 (GA4), Google Ads, and Meta Ads:

  • Campaigns driving high-ticket sales appear in GA4 with zero attributed revenue, while (direct) / (none) or banking domains claim the credit.
  • When customers authorize payments inside their banking apps (ING, ABN AMRO, Rabobank) and fail to click “Terug naar de webwinkel” (Return to webshop), the browser purchase tag never fires.
  • Google Ads Performance Max and Search campaigns receive incomplete conversion signals, causing Smart Bidding algorithms to bid aggressively on low-intent keywords or stall completely.

In this guide, I break down the exact technical causes behind iDEAL and Wero attribution drops and provide the battle-tested engineering fix used by top Dutch eCommerce brands.


Key Takeaways for Dutch & Belgian Online Retailers

  • Eliminate Unwanted Referral Splits: Bank redirect domains (ideal.nl, abnamro.nl, rabobank.nl, ing.nl) must be systematically added to GA4’s List of Unwanted Referrals to prevent new sessions from overwriting your Google Ads or Meta Ads campaign parameters.
  • Overcome the “Mobile Banking Drop”: When shoppers authenticate via QR codes or banking apps, up to 25% never return to your checkout success page. Relying solely on client-side thank-you tags guarantees underreported revenue.
  • Deploy Server-Side Webhook Fallbacks: Ingest payment status updates directly from your payment service provider (Mollie, Adyen, Stripe, Buckaroo). When a webhook confirms an order, dispatch the purchase event server-to-server to GA4 Measurement Protocol, Meta CAPI, and Google Ads Enhanced Conversions.
  • Consistent Net/Gross Revenue Handling (21% BTW): Standardize dataLayer values in Euro (€) excluding Dutch/Belgian VAT and shipping to maintain identical revenue targets across GA4 and Google Ads value-based bidding.

Why iDEAL & Wero Payments Break Marketing Attribution

To understand why your reports disagree, consider the typical consumer journey during an iDEAL checkout:

[Google Ad Click (gclid)] → [Store Session: Campaign X] 
   → [Checkout: iDEAL Selected] 
   → [REDIRECT: abnamro.nl or banking app] 
   → [REDIRECT BACK: store.nl/order-received] 
   → [GA4 creates NEW session attributed to abnamro.nl]

The Two Core Failure Points

1. The Referral Hijack

When the customer returns from the bank portal to your order confirmation page, the browser’s HTTP document.referrer points to the bank’s domain (e.g., https://bankieren.rabobank.nl/). If GA4 is not configured with referral exclusions, it terminates the marketing session and starts a new session attributed to the bank. The original paid campaign receives zero credit for the sale.

2. The Browser Abandonment Drop

Many consumers confirm their payment via face-ID on their mobile banking app and simply lock their phone or close the browser tab. Because your store’s thank-you page is never rendered in an active browser tab, client-side GTM tags never execute. Your store backend collects the money, but your ad platforms remain blind to the conversion.


Step 1: Configure Unwanted Referrals in GA4

The first essential fix is preventing returning bank visitors from initiating new sessions.

In Google Analytics 4:

  1. Navigate to Admin → Data Streams → Select your Web Stream.
  2. Under Google tag, click Configure tag settings.
  3. Under Settings, click Show more → List unwanted referrals.
  4. Add the following match rules (Condition: Referral domain contains):
    • ideal.nl
    • rabobank.nl
    • ing.nl
    • abnamro.nl
    • asnbank.nl
    • regiobank.nl
    • triodos.nl
    • bunq.com
    • knab.nl
    • mollie.com
    • adyen.com
    • buckaroo.nl
    • multisafepay.com
    • wero.eu
  5. Click Save.

Note: Adding these domains to unwanted referrals does not delete transactions. Instead, it instructs GA4 to ignore the banking referrer and credit the transaction to the previous non-direct marketing source that originally introduced the visitor.


Step 2: The Bulletproof Solution — Server-Side Webhook Purchase Ingestion

Configuring referral exclusions fixes session continuity, but it does not fix customers who never return to your thank-you page. To achieve 100% order capture, you must deploy Server-Side Tracking (sGTM) with payment gateway webhooks.

How the Architecture Operates:

  1. Client-Side Session Capture: When a shopper enters checkout, GTM captures persistent attribution tokens (gclid, _fbp, _fbc, client_id, and UTMs) and stores them as custom metadata inside the order record.
  2. Payment Gateway Webhook: When Mollie, Adyen, or Stripe confirms the iDEAL/Wero payment, your store triggers a backend webhook to your Server-Side GTM container (hosted on your first-party subdomain, e.g., data.yourbrand.nl).
  3. Server-Side Fanout: The sGTM container validates that the transaction has not already been tracked by the browser. If missing, it immediately dispatches:
    • Google Analytics 4: via Measurement Protocol with original client_id and session ID.
    • Google Ads: Enhanced Conversions with SHA-256 hashed customer details and gclid.
    • Meta Conversions API (CAPI): Complete purchase hit with high Event Match Quality (EMQ 9.0+).
[Payment Gateway Webhook] ───► [sGTM Container: data.yourbrand.nl]
                                      │
                 ┌────────────────────┼────────────────────┐
                 ▼                    ▼                    ▼
          [GA4 Measurement]    [Google Ads OCT]      [Meta CAPI]

Real-World Case Studies

Explore how server-side tracking, deduplication, and attribution modeling drive measurable revenue growth:


Frequently Asked Questions

Does transitioning to Wero change how we track payments?

Wero builds upon the European Payments Initiative architecture. While the user experience will feel faster and more mobile-native, the underlying redirect/deep-linking mechanism remains similar to iDEAL. Setting up server-side webhook fallbacks now future-proofs your store for the complete transition to Wero across the Netherlands, Belgium, France, and Germany.

Will server-side webhook tracking cause duplicate purchases?

No, provided you implement strict transaction deduplication. By passing a unique transaction_id (your store’s order number) across both client and server events, GA4 and Meta automatically discard duplicate hits that share the same ID within a 48-hour window.

Does this require modifying our payment contract with Mollie or Adyen?

No. All major payment gateways support webhooks out of the box. Whether you use standard plugins or custom APIs, order status notifications can be configured without altering your merchant agreement or banking setup.


Direct Implementation White-Label for Agencies

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.

✓ 24–48h Emergency SLA ✓ Strict Non-Solicitation & NDA ✓ 8.5+ Event Match Quality
Jobair Mahmud

Jobair Mahmud

AI-Driven Performance Marketing & Web Analytics Consultant

Helping eCommerce brands and marketing agencies trust their ads data, scale Smart Bidding, and eliminate wasted ad spend through bulletproof server-side tracking and PPC management.