-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add AB test to use propertyId
in CMP sourcepoint config
#1507
Conversation
🦋 Changeset detectedLatest commit: d422d4f The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Tip Once this PR is ready to go, add the This saves us a lot of money by not running the tests before we need them. |
db97eae
to
59437be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from a commercial perspective!
propertyId
instead of propertyHref
in CMP sourcepoint configpropertyId
in CMP sourcepoint config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you.
What are you changing?
Testing the suggested change from sourcepoint documentation, to use
propertyId
rather thanpropertyHref
Most of the world uses a single id, but Australia has their own for some reason.
Why?
When using
propertyHref
sourcepoint uses an extra network request to determine consent, currently there's 2-3 requests depending on if there are any changes on sourcepoint's side i.e. to the vendorlist. After this change it will be reduced to 1-2.This should speed up getting consent by 50-33% as it appears to be mostly network bound, and therefore anything else that waits for consent, e.g. advertising.
Before:
After: