Why GA4 data in Thailand is usually wrong
Most GA4 properties we open have the same handful of problems. None of them are exotic; they come from setting GA4 up the way a global template says to, without accounting for how Thai customers actually browse and pay.
- LINE in-app browser traffic shows up as "direct". Links shared in LINE chats and LINE Official Account broadcasts open inside LINE's own browser, often without a referrer. Unless your links carry UTM parameters, a large part of your LINE-driven traffic is invisible as a channel.
- Purchases that happen off-site never come back. PromptPay QR payments, mobile-banking app deep links and payment-gateway redirects frequently lose the GA4 session or never return the customer to a thank-you page. Revenue in GA4 then undercounts revenue in your back office.
- Thai-language campaign names break reports. UTMs written in Thai are percent-encoded in URLs and are easy to mistype; one campaign ends up split across several rows. We standardize on lowercase ASCII naming conventions and keep the Thai label in a lookup table.
- Marketplace sales sit outside GA4. Shopee, Lazada and TikTok Shop orders do not reach your GA4 property at all. That is fine — as long as everyone understands that GA4 measures your own site only, and the "total sales" dashboard joins marketplace data elsewhere.
- Consent is either missing or blocking everything. Under Thailand's PDPA, analytics cookies generally need opt-in consent. We see sites with no consent banner at all, and sites whose banner silently blocks GA4 for everyone. Both are fixable.
What a GA4 engagement includes
1. Audit (fixed scope)
We review your GA4 property, Google Tag Manager container, consent setup and the key conversion paths on your site, then hand you a ranked list of issues: what is broken, what it costs you in decision quality, and how long each fix takes. You keep the document whether or not you hire us for the fixes.
- Property and data-stream settings, data retention, internal-traffic and referral exclusions
- Event and parameter design versus what the business actually needs to know
- Ecommerce or lead tracking validated end to end with real test transactions
- Cross-domain and payment-gateway return flows
- Google Ads and Search Console links, key events (conversions) and attribution settings
- Consent mode behaviour before and after a visitor accepts or declines
2. Implementation
We rebuild tracking through Google Tag Manager (client-side, or server-side when it is worth the extra cost), write a measurement plan in plain English and Thai, and document every event so your next developer or agency can maintain it.
3. BigQuery and reporting
For businesses that need more than the GA4 interface, we enable the BigQuery export and build a small set of modelled tables: sessions with clean channel grouping, orders reconciled against your back office, and lead-to-sale joins. Dashboards are built in Looker Studio with Thai and English labels so both sides of the team read the same numbers. If attribution is the question, see our Markov attribution walkthrough.
Thailand-specific tracking patterns we use
| Situation | What usually happens | What we do |
|---|---|---|
| Customer pays by PromptPay QR | Customer leaves to banking app; purchase event never fires | Fire purchase server-side from the payment webhook (Measurement Protocol) with the original client ID |
| Lead chats on LINE instead of submitting a form | Lead is invisible in GA4 and Google Ads | Track the "add friend / open chat" click as a key event, tag LINE links, import qualified leads back as offline conversions |
| Thai and English versions of the site | Two properties, or one property with mixed page titles | One property, a language parameter, and content grouping by template |
| Phone calls from mobile | Tap-to-call is untracked | tel: click events, plus call tracking where volume justifies it |
How we work
- Scoping call — what decisions does your team need data for? We scope the measurement plan around those, not around "track everything".
- Access — you grant us access to your GA4, GTM and Ads accounts. We never create accounts you do not own.
- Audit or build — delivered in a staging GTM workspace, tested, then published with a change log.
- Handover — documentation, a walkthrough recording, and optional monthly maintenance.
We run the same stack on our own portfolio of Thailand websites, so the patterns above are ones we maintain ourselves, not slideware.