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

Added 'ceh' config property in Criteo bid adapter #3969

Merged
merged 4 commits into from
Jul 19, 2019

Conversation

leonardlabat
Copy link
Contributor

Type of change

  • Feature

Description of change

We'd like to add the ability for publishers to give to our adapter the hashed email of the current user.
Syntax for this will be the following.

  pbjs.setConfig({
    criteo: {
      ceh: 'hashed mail'
    }
  });

jsfaure and others added 2 commits July 5, 2019 13:46
Added 'ceh' config property and mapped it to CDB request
@jsnellbaker
Copy link
Collaborator

Hi @leonardlabat,

Instead of passing this new value through the setConfig, could you pass it through your bidder params in the adUnit instead? That would be the more ideal location to pass this type of bidder specific information into the auction.

Thanks,
Jason

@leonardlabat
Copy link
Contributor Author

Hi @jsnellbaker,

Yes that was our first thought. But that would require the publisher to repeat the hashed email on each ad unit. However, this is some kind of global parameter about the user (a bit like gdpr), something that we'll send at the root of the http request to our bidder, and not along each bid request.

Do you see what I mean ?

Regards,
Leonard

@jsnellbaker
Copy link
Collaborator

Hi @leonardlabat
I understand your point, but at this time - this type of data should still be handled through the adUnit.

There is discussion about establishing a defined way to pass bidder unique data through the config (#3687) which might be in line with what you wanted to setup here. But until that process is decided and implemented, would you be able to pivot the changes here?

@mafaigna
Copy link

mafaigna commented Jul 12, 2019

Hi @jsnellbaker ,
We are excited indeed to see the standardisation of the way to pass first-party data in Prebid. However, at this stage, adapters have been adopting different ways to achieve this purpose - including the use of setconfig. The latter seems easier from publisher standpoint. What are your concerns with regard to the use of setconfig - waiting for FPD standardization?

@mafaigna
Copy link

ping @jsnellbaker

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 @leonardlabat @mafaigna,

Through further internal discussion on the setConfig topic, it was decided that it would be okay for you to proceed with this implementation.

I have ran some tests with the updates in the adapter and found they appear to be working as expected. There was one suggestion that I would like you to make in the unit tests before we merge this PR. Can you please take a look at the in-line comment below when you have the chance?

Thanks.

},
},
];
config.setConfig({
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you either add a after, afterEach or beforeEach function in this describe section to run the config.resetConfig(); statement? This will ensure that some other tests don't have a setConfig that includes your bidder property when they're all running together.

@leonardlabat
Copy link
Contributor Author

Hi @jsnellbaker,

Thanks for the review. I've just pushed a commit to add this call to config.resetConfig.

Leonard

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.

Thanks for the update; LGTM

@jsnellbaker jsnellbaker merged commit 3740de3 into prebid:master Jul 19, 2019
VideoReach pushed a commit to VideoReach/Prebid.js that referenced this pull request Aug 1, 2019
* Added 'ceh' config property and mapped it to CDB request

Added 'ceh' config property and mapped it to CDB request

* Added config.resetConfig() to ensure that call to setConfig won't have an impact on any other test

* Missed the ';'
leonardlabat added a commit to criteo-forks/Prebid.js that referenced this pull request Aug 6, 2019
* Added 'ceh' config property and mapped it to CDB request

Added 'ceh' config property and mapped it to CDB request

* Added config.resetConfig() to ensure that call to setConfig won't have an impact on any other test

* Missed the ';'
sa1omon pushed a commit to gamoshi/Prebid.js that referenced this pull request Nov 28, 2019
* Added 'ceh' config property and mapped it to CDB request

Added 'ceh' config property and mapped it to CDB request

* Added config.resetConfig() to ensure that call to setConfig won't have an impact on any other test

* Missed the ';'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants