Skip to content
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

PulsePoint Adapter GDPR support #2471

Merged
merged 26 commits into from
May 1, 2018
Merged

PulsePoint Adapter GDPR support #2471

merged 26 commits into from
May 1, 2018

Conversation

anand-venkatraman
Copy link
Contributor

Type of change

  • Feature

Description of change

GDPR support to PulsePoint Bid adapter.

Anand Venkatraman (avenkatraman@pulsepoint.com)

* ET-1691: Adding pulsepoint analytics and tests for pulsepoint adapter

* ET-1691: Adding pulsepoint analytics and tests for pulsepoint adapter

* ET-1691: cleanup

* ET-1691: minor

* ET-1691: revert package.json change
@anand-venkatraman anand-venkatraman changed the title Pulsepoint gdpr PulsePoint Adapter GDPR support Apr 30, 2018
@jsnellbaker jsnellbaker self-assigned this Apr 30, 2018
@jsnellbaker jsnellbaker self-requested a review April 30, 2018 14:27
Copy link
Collaborator

@jsnellbaker jsnellbaker left a comment

Choose a reason for hiding this comment

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

Hi @anand-venkatraman, Thanks for submitting this update. There is a change needed, please see the details in-line below.

Also, can you please submit a PR to the docs repo to add a gdpr_supported: true variable to your respective page in the bidders directory? This will flag your adapter as GDPR compliant in the prebid docs. Thanks

@@ -42,6 +42,7 @@ export const spec = {
app: app(bidRequests),
device: device(),
};
applyGdpr(bidRequests, request);
Copy link
Collaborator

Choose a reason for hiding this comment

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

The GDPR consent data does not exist in the bidRequests object, but rather in the bidderRequest object (which is the second argument).

In this case, you'll need to modify the buildRequests function call like so:

  buildRequests: (bidRequests, bidderRequest) => {

Then you can pass in the bidderRequest value into the applyGdpr function (note - this will be a single object, not an array of objects). You'll still access the consent data with bidderRequest.gdprConsent.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated.

@anand-venkatraman
Copy link
Contributor Author

Submitted a PR to docs repo - prebid/prebid.github.io#735

Copy link
Collaborator

@jsnellbaker jsnellbaker left a comment

Choose a reason for hiding this comment

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

LGTM

@jsnellbaker jsnellbaker merged commit a0fee37 into prebid:master May 1, 2018
dluxemburg pushed a commit to Genius/Prebid.js that referenced this pull request Jul 17, 2018
* ET-1691: Pulsepoint Analytics adapter for Prebid. (#1)

* ET-1691: Adding pulsepoint analytics and tests for pulsepoint adapter

* ET-1691: Adding pulsepoint analytics and tests for pulsepoint adapter

* ET-1691: cleanup

* ET-1691: minor

* ET-1691: revert package.json change

* Adding bidRequest to bidFactory.createBid method as per prebid#509

* ET-1765: Adding support for additional params in PulsePoint adapter (#2)

* ET-1850: Fixing prebid#866

* Minor fix

* Adding mandatory parameters to Bid

* Pulsepoint Bid Adapter - GDPR support

* minor update

* minor update

* Fixing review comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants