Hybrid desk
A measurement strategy that admits both runtimes exist.
This page is the studio’s working method — the same spine we teach in Hybrid App Measurement Strategy. It is not a vendor comparison chart.
Start with ownership, not with tools
Every meaningful user action in a hybrid app happens in native, in a WebView, or in both. The first artefact we ask for is an ownership table: event name, runtime, who may fire it, and what must never fire it. Until that table exists, installing another SDK only multiplies the argument.
Teams often discover that “purchase” is owned by nobody. Native fires it on receipt, the WebView fires it on thank-you, and a server pixel fires it on webhook. Finance then picks a number. The desk’s job is to pick an owner and demote the rest to diagnostics.
Identity
The bridge is not a user id
A JS bridge that passes a session token into HTML is convenient. It is also how duplicate funnels are born. We teach a narrow bridge: consent state, a signed runtime flag, and nothing that looks like a durable identifier unless legal has already agreed.
IDFA, GAID, and first-party user ids are treated as separate planes. Mixing them inside a WebView cookie jar is how attribution windows silently widen.
Consent before init
For products serving people in Thailand, PDPA timing is part of measurement strategy, not an appendix. SDKs that initialise on splash will collect before consent. We keep a simple rule: no advertising or analytics SDK init until the consent artefact is stored, including inside the WebView that loads later.
Attribution as a written window
Lookbacks copied from a media partner’s default are not a strategy. The desk writes the window into the measurement contract, notes what happens when the WebView drops the referrer, and lists which campaigns you will refuse to score until identity is reliable.
Where to go next
If you want to practise this method on a sandbox, start with the flagship. If your production taxonomy is already on fire, ask about a Measurement Residence.