v0.0.5

Mobile attribution and deferred deep linking for Android.

What's new in 0.0.5

• Navigation is never gated by consent. Fixed a bug where a deep link could fail to resolve its
  destination without consent — the user now always reaches the right screen, whether or not
  attribution is recorded.
• Install held until a consent decision. The install call now waits for the user to actually
  decide (grant or deny) instead of racing ahead — preventing an unattributed request from firing
  before the consent prompt is answered.
• Fixed deterministic clickId matching. The Play Install Referrer token was sometimes sent with
  its lt_click= prefix intact instead of the bare 32-hex token, which the backend match requires
  exactly — this was silently breaking install attribution for some devices.
• Diagnostics. The raw Play Install Referrer is now logged at INFO (tag LinkTrail), so a
  missing or unexpected clickId is diagnosable from adb logcat -s LinkTrail instead of a silent
  null. See TROUBLESHOOTING.md for the full debugging playbook (App Links
  verification, stale Play Store/referrer caches, pm clear, etc).

Install

implementation("io.linktrail:sdk:0.0.5")

Published on Maven Central · Min SDK 26.

Changelog

• 0.0.5 — Navigation never gated by consent; install held until consent decision; clickId token-extraction fix; raw referrer diagnostics logging.
• 0.0.4 — Consent gating: attribution gated behind setConsent (deny-by-default); links still route pre-consent.
• 0.0.3 — Deferred deep linking fixes: read the lt_click token from the Play Install Referrer, send clickId as a string token, and parse the { install, deepLink } install response.
• 0.0.2 — Fix: omit null optional fields from request bodies (the backend rejects an explicit null clickId).
• 0.0.1 — Initial release.