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.

v0.0.4

Mobile attribution and deferred deep linking for Android.

What's new in 0.0.4

Consent gating (GDPR / ePrivacy). Attribution is now gated behind user consent by default
(requireConsent = true), following the "links work, tracking waits" model:

• Before consent, deep links still route — deferred and re-engagement links reach their
  destination via onLink — but the install is sent unattributed (consent = false): the
  backend resolves the link for routing yet records nothing, exposes no attribution, and drops events.
• Grant with LinkTrail.setConsent(true) to send the real attributed install and flush queued
  events, without re-routing a user already sent to their screen. setConsent(false) revokes and
  clears the queue.
• Deny-by-default — an unset flag counts as no consent. Opt out with
  LinkTrailOptions(requireConsent = false) to attribute at init.

See the Consent gating section, and the KickFlip
example for a working consent prompt wired to setConsent.

Install

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

Published on Maven Central · Min SDK 26.

Changelog

• 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.

v0.0.3

Mobile attribution and deferred deep linking for Android — distributed as a binary AAR, entry point LinkTrail.

Install

Published on Maven Central — no custom repository needed:

dependencies {
    implementation("io.linktrail:sdk:0.0.3")
}

Min SDK: 26. See the README for setup, and the troubleshooting guide for App Links verification.

Changelog

• 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), which previously made every install/open fail with HTTP 400.
• 0.0.1 — Initial release.