feat: add unified mobile measurement api - #114
Closed
KingDoxik wants to merge 1 commit into
Closed
Conversation
|
Thank you for following the naming conventions for pull request titles! 🙏 |
Contributor
Author
|
Superseded by #115 after the branch rename. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Mobile attribution and lifecycle evidence need one policy-aware API and a durable delivery contract that remains correct across offline use, retries, process death, and self-hosted deployments.
Impact
Applications gain namespaced measurement capabilities, signed invite and deferred-link flows, protected identifiers and purchase evidence, native push/link collection, endpoint overrides, and auditable diagnostics. Existing analytics and purchase behavior remains supported through the unified runtime.
Validation