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.