Closed NidhiDixit09 closed 7 months ago
Attention: 6 lines
in your changes are missing coverage. Please review.
Comparison is base (
bf6e9ee
) 50.73% compared to head (6a61813
) 50.98%. Report is 2 commits behind head on master.:exclamation: Current head 6a61813 differs from pull request most recent head ecb5e3b. Consider uploading reports for the commit ecb5e3b to get more accurate results
Files | Patch % | Lines |
---|---|---|
BranchSDK/BNCPreferenceHelper.m | 86.95% | 0 Missing and 6 partials :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Reference
SDK-2223 -- Design and implement key/values to represent consent param
Summary
+ (void) setDMAParamsForEEA:(BOOL) eeaRegion AdPersonalizationConsent:(BOOL) adPersonalizationConsent AdUserDataUsageConsent:(BOOL) adUserDataUsageConsent;
Motivation
Support new params added in Google Conversion API for DMA Compliance.
Type Of Change
Testing Instructions
eeaRegion
, with every/v1/install
,/v1/open
,/v2/event
,v1/pageview
request. -- SDKis sending value ofadPersonalizationConsent
/adUserDataUsageConsent
with every/v1/install
,/v1/open
,/v2/event
,v1/pageview
request only if -eeaRegion
istrue
OReeaRegion
isfalse
andadPersonalizationConsent
/adUserDataUsageConsent
is also set tofalse
Ref : https://www.notion.so/brancheng/Google-DMA-Compliance-c19ed28d2ea74b2b9fa4d2d77f8cdcbecc @BranchMetrics/saas-sdk-devs for visibility.