GA4 Analytics vs Matomo Pro for SG E-commerce Sites

Funnel Tracking: GA4 Events vs Matomo Pro Actions

GA4 replaces Universal Analytics’ pageview-based session with a structured event schema: `view_item`, `add_to_cart`, `begin_checkout`, `add_payment_info`, and `purchase`. SG merchants using the Shopify “Google & YouTube” channel get most of these wired in automatically, including the `items` parameter array with SKU-level fields such as `item_category`, `item_variant`, and `price`. You then surface these as Custom Definitions, which are the only way to do something like “revenue per brand drop” or “purchase by stock-keeping unit” inside the GA4 interface.

Matomo Pro’s e-commerce tracking is more traditional: the plugin fires `trackEcommerceOrder` with order ID, revenue, and products, then writes every event into an accessible row-level log. You do not need to wait for an exploration to be sampled or for the schema to settle. For a Singapore store running a periodic inventory drop—say, 40 new SKUs at a fixed release hour—Matomo’s “Visits Log” shows exactly where each cart exited, in real time, without the parametric UI burden GA4 imposes.

The catch in reverse: GA4’s funnel explorer is battle-tested for Google Ads conversion paths, while Matomo’s Goal-based funnels give you a simpler but less flexible view of the same drop-off.

PDPA Consent and Where the Data Resides

Under Singapore’s Personal Data Protection Act, a pseudonymous client ID or IP address collected by an analytics script qualifies as personal data when it can be tied back to an individual. Section 18 and 20 obligations mean your consent collection must be demonstrable, and cross-border transfers must satisfy the conditions in Section 26.

GA4 pushes you toward Google Consent Mode v2: when a user denies `ad_storage` or `analytics_storage`, GA4 fires cookieless pings that trigger a conversion model, but the actual precision of your purchase event drops. Singapore merchants running paid search at SGD 1-2 per click will feel that loss immediately in the “Unidentified” sessions bucket.

Matomo Pro has two advantages here. First, its consent manager is native and first-party: the cookie is written on your SG domain, not on a Google-owned third-party domain. Second, Matomo Pro offers EU and US data residency options at plan setup. The honest warning: neither option is ap-southeast-1, and Matomo Pro does not offer an AWS Singapore region. If an SG retailer requires data to stay inside Singapore—for example, a brand processing health-adjacent or financial-adjacent product data—the only real answer is self-hosted Matomo on an EC2 instance in `ap-southeast-1`, not Matomo Pro.

Google Ads Attribution: The Real SG Advantage

This is where GA4 is not an even fight. GA4 links directly to your Google Ads MCC account and pulls cost, clicks, and conversions every few hours. It also enables Data-Driven Attribution, which uses Google’s search-log signals to credit touchpoints across the path, not just the final click. In Singapore’s paid search market, head retail terms like “wireless earbuds SG” carry broad-intent traffic; without DDA, a last-click model consistently over-credits brand-keyword closers and starves top-of-funnel discovery spend.

Matomo Pro supports first touch, last touch, linear, and position-based attribution models, but it has no machine-learning DDA. You can import Google Ads costs via the Google Ads API into Matomo for blended reporting, but it is a monthly operational chore, not a native pipeline. An SG e-commerce operator whose ROAS depends on aggressive ad group splitting should treat this as the decisive factor.

Reconciliation With Shopify, Stripe, and PayNow

The day-after operational test matters more than dashboard polish. GA4 standard reports in 2025 settle up to 48 hours later, and reattribution due to model changes will retroactively edit yesterday’s revenue numbers. That is corrosive when you are trying to reconcile a week’s payout against Shopify’s actual order ledger or Stripe settlement.

Matomo Pro updates dashboards within seconds and keeps order rows immutable in the e-commerce log. A store owner in Singapore can match a Matomo order row against a PayNow payment reference the same afternoon. GA4’s realtime report has a 30-minute window, and the full BigQuery export streams hourly but requires SQL to interpret.

There is also the client-side tracking gap: scripts blocked by ad blockers and connection-dropped page loads mean GA4 typically under-reports purchases by 5-15% compared with Shopify’s backend. The fix is server-side tagging—either Google Cloud Run in `asia-southeast1` for GA4 or server-side GTM forwarding purchases to Matomo. Both add infrastructure cost and engineering hours, so budget for that work.

Total Annual Cost in SGD, Not Dreams

GA4’s free tier is genuinely free to collect events. The hidden bill lands in BigQuery: storage in the Singapore region runs about USD 0.036 per GB-month and on-demand queries bill at USD 6.50 per TB scanned. A store processing 500,000 events per month produces a tiny storage bill—less than SGD 30 annually—but iterative SQL exploration can quickly consume terabytes of scan if your team builds sloppy custom reports. GA4 360, when you outgrow limits, costs USD 50,000 per year plus overage.

Matomo Pro is sold on a pageview ladder: public entry pricing sits around USD 19 per month for small stores, with a 2-million-pageview month—typical for a mid-tier Singapore DTC site doing 30-50k sessions—landing in the low hundreds per month. That flat rate includes retention and no query penalties. But you lose the Google Signals loop: GA4’s cross-device reporting and machine-learning conversion modeling simply do not exist in Matomo’s self-contained world.