What a deep link is allowed to claim
A deep link is a promise: this tap should open a specific surface, with enough context to continue a story. Performance tracking asks whether that promise survived the store, the OS, the carrier, and the user’s impatience. If you only count “opens,” you are counting weather.
We separate three claims that dashboards love to merge: the link was tapped, the app was opened, and the session belonged to that tap. Signal Path spends a full module on the third claim. Most arguments with finance live there.
Deferred arrivals
When the app is not installed, the store hop destroys most of the original URL. Deferred deep linking tries to reconstruct intent after first open. In Thailand that reconstruction collides with Play referrer quirks, dual-SIM routing, and users who start on LINE and finish on Chrome.
Our Deferred Arrival workshop treats fingerprint expiry as a first-class failure, not an edge case. If your campaign cannot survive a two-minute subway ride, it is not a campaign — it is a demo.
Windows are product decisions
A seven-day click window copied from a US brand video playbook will flatter Bangkok LINE bursts and insult search. Attribution windows are not a setting you “turn on.” They are a sentence you must be willing to say in a QBR: we will credit this tap for this long, and here is why.
Read the field note on windows and Bangkok media before you accept a partner default.
Telemetry that stays quiet
SDK payloads accumulate vanity fields until privacy review and performance traces both become unreadable. Quiet SDK Telemetry is the studio block where we delete. If a parameter cannot change a decision, it does not travel.
This is also where teams discover they were sending the same click ID twice under two names — the most common double-count we still see in 2026.
