feat: Support consent mapping #47
Merged
Conversation
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
nickolas-dimitrakas
requested review from
BrandonStalnaker,
denischilik and
rmi22186
Co-Authored-By: denischilik <225006499+denischilik@users.noreply.github.com>
denischilik
approved these changes
Sep 11, 2025
- Created mocks - exposed methods and properties to swift Co-Authored-By: denischilik <225006499+denischilik@users.noreply.github.com>
BrandonStalnaker
approved these changes
Sep 17, 2025
nickolas-dimitrakas
deleted the
feat/SDKE-124-i-os-appsflyer-kit-support-consent-mapping
branch
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
This update adds support for passing consent to AppsFlyer through consentMapping, enabling DMA-compliant consent handling. The integration maps mParticle consent states to AppsFlyer’s consent API, ensuring user preferences for ad storage, personalization, and data usage are properly respected. This brings the AppsFlyer kit in line with the latest compliance requirements.
Testing Plan
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)