Skip to content

Conversation

@gpsamson
Copy link
Contributor

@gpsamson gpsamson commented Jul 14, 2020

NOTE This is a copy of #486! I had to open this PR so that the private CI contexts would resolve.

What does this PR do?
This PR will make a dataProcessingOptions call before init to opt-in to Limited Data Use. It will do this by default.

Are there breaking changes in this PR?
No.

Any background context you want to provide?
Facebook has announced a new Limited Data Use feature that is designed to assist with compliance with the California Consumer Privacy Act (CCPA). Data tagged as Limited Data Use will only be processed by Facebook in ways that allow Facebook to fit within the definition of Service Provider under the CCPA, thus avoiding the possibility that website operators using Facebook Pixel could be considered to be "selling" data to Facebook.

During the month of July Facebook will automatically tag events coming from California as Limited Data Use. But starting in August, clients must opt-in to this behavior by making a dataProcessingOptions call before init.

Is there parity with the server-side/android/iOS integration components (if applicable)?
Facebook Pixel is only a Device - Web integration.

There are similar options in the Facebook App Events and Facebook Offline Conversions APIs, which may be of interest to those using those integrations.

Does this require a new integration setting? If so, please explain how the new setting works
This adds the limitedDataUse setting, a boolean which defaults to true. If this setting is true, a dataProcessingOptions call will be made instructing Facebook to apply Limited Data Use if Facebook's geolocation determines the client is in the state of California.

Links to helpful docs and other external resources

Test Plan

  • Testing completed successfully stage

Rollback Plan
Revert this PR

);
});

it('should call dataProcessingOptions if limitedDataUse is enabled', function() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe overkill -- but also add test for when it is disabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call. I'll add one!

@gpsamson gpsamson merged commit a5f905a into master Jul 16, 2020
@gpsamson gpsamson deleted the gps/ldu branch July 16, 2020 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants