Article 30

Shopify, PrestaShop or WooCommerce in Israel: local payment gateways and sales Meta and Google miss

By Dan Elbaz10 min read

Your store records 120 orders this week. Meta sees 70. Ads Manager reports ROAS of 2.1 when reality is closer to 3.6. On that basis, you stop a profitable campaign and keep a weaker one.

Often the culprit is neither Meta nor the agency. It is the buyer’s payment journey. In Israel, that nearly always involves a local gateway, where sales tracking gets lost.

Here is why it is more common in Israel, how to diagnose it in thirty minutes, and how to fix it on Shopify, PrestaShop and WooCommerce.

Why Israeli stores are particularly affected

No Shopify Payments in Israel

Shopify Payments is not available in Israel, which is absent from its official supported-country list. Israeli stores therefore use third parties such as Cardcom, Tranzila, Grow (formerly Meshulam), PayPlus and Allpay.

These providers support local expectations: card instalments, up to twelve payments with some, Bit and Apple Pay. They are essential to conversion. Payment apps are no longer just for person-to-person transfers: an October 2023 survey cited by the Bank of Israel found 42% of transferred sums went to businesses for goods or services. Ignoring these methods loses sales; ignoring their tracking loses data.

Each integration has its own technical flow, which determines whether measurement tools see the purchase.

The critical moment: returning to your site

Typically, buyers leave your site for a hosted payment page or pay within an iframe. After approval, they must return to your confirmation page. Loading that page triggers the Meta pixel, Google Ads tag and GA4 purchase event.

If the buyer does not return, the order exists in your back office but not in advertising tools. Many things can prevent that return:

  • closing the tab once the bank confirms payment,

  • bank authentication opening another window or app,

  • Bit payment switching to the app on mobile, then returning in a different browser,

  • a misconfigured gateway redirect or a destination without tags,

  • an ad blocker or rejected cookies preventing tags from firing

Each lost event is invisible. The combined loss is not.

Symptoms to recognise

Symptom Likely cause Where to check
Fewer purchases in Meta or Google Ads than in the back office Confirmation page not reached, or tags blocked Compare back office / Events Manager / Google Ads
Purchases counted twice Reloaded confirmation page or missing pixel/CAPI deduplication Meta Events Manager, deduplication diagnostics
GA4 sales attributed to the payment gateway Payment domain not excluded from referrals GA4 traffic acquisition report
Inconsistent purchase value One instalment sent instead of the total, or incorrect VAT/currency Purchase-event details
Purchases attributed to direct traffic Gateway interrupts the session or loses campaign parameters GA4 conversion paths

One symptom can distort decisions. Two or three make ad reports tell a different story from your bank account.

A thirty-minute diagnosis

You do not need a full audit to identify the issue. This test is enough.

  1. Export the last seven days’ orders from the back office: count and revenue, excluding cancelled orders

  2. Record tracked purchases for the same period in Meta Events Manager, Google Ads by conversion date, and GA4

  3. Calculate a capture rate for each tool: recorded purchases divided by actual orders

  4. Place a real test order using each payment method — card, instalments, Bit and Apple Pay — on mobile and desktop, watching for events in real time

  5. Open GA4’s acquisition report and look for payment-provider domains among traffic sources

Here is what an illustrative result might look like:

Source Recorded purchases Capture rate
Back office (reference) 120 100 %
GA4 95 79 %
Google Ads 88 73 %
Meta (pixel only) 70 58 %

A small percentage gap is normal: cookie rejection, blockers and attribution windows. Capture below 80% suggests a structural issue. Large week-to-week variation suggests fragile configuration.

Shopify: what changed in August 2026

Shopify set 26 August 2026 as the upgrade deadline for Thank you and Order status pages, then automatically upgraded remaining stores. Legacy Additional scripts no longer run on those pages. If purchase tracking depended on them, it may have stopped silently.

What to do:

  • Check purchases since late August 2026. A sharp drop in tracked Meta or Google Ads purchases without falling sales indicates broken tracking

  • Use Shopify customer events through custom pixels and apps, replacing Additional scripts

  • Enable server-side data sharing in Shopify’s Facebook and Instagram app. Enhanced and Maximum levels use Conversions API, sending purchases server to server without relying on the buyer’s browser

  • Use the official Google app for Google Ads and GA4 rather than manually added tags

With an Israeli gateway integrated as a Shopify payment app, buyers normally return to Shopify’s confirmation page. Risks mainly arise from old setups, manual scripts and integrations linking to external pages.

WooCommerce and PrestaShop: secure the return, then stop relying on it

Each gateway is installed as a plugin or module. Integration quality varies widely by provider and version.

Step 1: make the return reliable

  • Check that successful-payment redirects reach your order confirmation page with the order ID

  • Test cards, instalments and Bit separately: behaviour can differ

  • Ensure the confirmation page records the purchase only once, even after a reload

Step 2: send the purchase from the server

The strongest solution does not depend on the buyer returning. When the gateway confirms payment through a server notification, the order becomes paid. Your server should then send the purchase to Meta through Conversions API and to Google.

Options include the official Meta WooCommerce extension with CAPI, dedicated PrestaShop modules, or server-side Google Tag Manager centralising platform delivery.

Step 3: deduplicate

If both browser and server send the purchase, prevent double counting. Meta deduplicates matching event names and IDs from pixel and CAPI within 48 hours, generally keeping the first received. Use the unique order number, available on both sides.

Send a transaction ID with every Google Ads purchase conversion. Google uses it to remove duplicates.

Improve matching with enhanced conversions

Sending the purchase is not enough: the platform must connect it to the person who saw or clicked the ad. More identifying signals improve matching.

Google enhanced conversions supplement purchase tags with buyer-provided data such as email or phone, hashed before sending and matched to signed-in Google accounts. Meta CAPI accepts the same hashed data to improve event matching.

For Israeli stores, phone formatting matters: use international format, 972 followed by the number without its initial zero. Otherwise many matches fail.

Sales that never go through your website

Some Israeli sales happen outside checkout: WhatsApp orders paid via a link, phone sales or Bit transfers after a conversation. They are real sales, often generated by ads, yet appear in no measurement tool.

To bring them back into measurement:

  • Record them in your back office or CRM, with customer details and the declared source

  • Send them to Meta through CAPI as offline events linked to hashed customer details

  • Import them into Google Ads as offline conversions, or enhanced conversions for leads if the customer first completed a form

A retailer generating 20% of revenue through WhatsApp without reporting it understates campaign profitability by that amount.

GA4: stop gateways taking credit for sales

On return from payment, GA4 may see the gateway as a new referral source. Sales are then credited to “cardcom.co.il / referral” or a similar domain, removing credit from campaigns.

The fix takes a few minutes. In GA4: Admin › Data streams › your web stream › Configure tag settings › List unwanted referrals. Add payment-provider and bank-authentication domains appearing in your reports.

Google notes that this is not retrospective. Attribution may temporarily continue crediting the domain for previous visitors. Assess the effect over several weeks.

Instalments, currency and VAT: send the right value

A tracked purchase with the wrong value distorts ROAS as much as a missed purchase.

  • Instalments. Send the total order value, not the first instalment. Check where the integration gets that amount

  • Currency. Always send the currency code, ILS for shekels. Orders in euros or dollars must carry their own currency

  • VAT and delivery. Decide whether values include 18% VAT and delivery, then apply that rule everywhere. Otherwise Meta and Google ROAS cannot be compared

  • Cancellations and refunds. Cancelled orders remain counted. Google Ads supports conversion adjustments or retractions; at minimum include cancellation rates in your calculations

French customers: the consent question

If your Israeli store sells in France, some visitors fall under European law. Advertising tags require consent for them. Google also requires EEA user-consent signals through Consent Mode to preserve measurement and ad personalisation.

Some French purchases will remain unobservable, which is normal and why platforms model conversions. Separate capture rates by country: a larger French gap does not necessarily mean a fault.

Who should do what

Tracking problems usually span several responsibilities:

  • The payment provider configures return URLs and payment notifications

  • The developer or integrator installs store plugins, confirmation pages and server-side delivery

  • The agency defines events, checks deduplication and capture rates, and uses the data in campaigns

  • You make decisions and retain control of the accounts

The common trap is everyone blaming someone else. Appoint one tracking owner with a target capture rate and weekly checks.

How the fix changes your decisions

Fixing tracking does not instantly increase sales. It improves every decision you make.

  • Algorithms learn better. Meta ad sets generally leave learning after around 50 optimisation events in seven days. Sending only 58% makes learning take almost twice as long

  • More bidding strategies become available. Google target ROAS requires at least 15 conversions over 30 days for Search and Shopping. Missed conversions can keep you below that threshold

  • Budget decisions become more accurate. An unprofitable campaign may only look that way in the report. Check capture rates before cutting campaigns or creatives because of low ROAS

If reports and back-office figures differ, the back office is the reference. Ad reports are estimates. Our attribution article examines this gap.

The checklist

  • Every payment method returns buyers to the confirmation page

  • Confirmed payment triggers server-side purchase delivery to Meta and Google

  • Pixel and server share the order number as event ID

  • Google Ads receives the transaction ID

  • Payment domains are listed as unwanted referrals in GA4

  • Send the total order value with currency and one consistent VAT/delivery rule

  • No Shopify tracking relies on legacy Additional scripts

  • Check capture rates weekly for each tool

Frequently asked questions

Should you change payment gateway?

Rarely. Most issues are configuration-related. Start with diagnosis and server-side delivery. Change provider only if its integration cannot provide reliable returns or usable payment notifications.

Is server-side delivery enough without a pixel?

Combining both is better. Meta recommends pixel plus CAPI with deduplication. The browser provides useful browsing signals; the server ensures the purchase is sent.

In summary

  • Shopify Payments is unavailable in Israel : stores use local gateways with varying integration quality

  • Sales tracking is mainly lost on the return to the confirmation page

  • Diagnosis takes thirty minutes : compare back office and platforms, place a test order and inspect GA4

  • The lasting fix is server-side delivery, with deduplication using the order number

  • Reliable tracking does not itself sell more, but it stops you cutting your best campaigns

Further reading

Sources

CONTACT

Ready to take
your advertising to new heights?

Let us discuss your project and how we can help.