Audigent Segmentation Real-time Data Provider

[antlauzon]

Type of change

• Bugfix
• Feature
• New bidder adapter
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Does this change affect user-facing APIs or examples documented on http://prebid.org?
• Other

Description of change

This changeset adds a real time data module for retrieving Audigent user segmentation data for unified ids. Using this real time data module, rtb adapters can supply rich segmentation data at request time in order to better target audiences.

Audigent is a next-generation data management platform and a first-of-a-kind "data agency" containing some of the most exclusive content-consuming audiences across desktop, mobile and social platforms.

• ant@audigent.com
• official adapter submission

[bretg]

@anthonylauzon - sorry, we're backed up. But just skimming this in a few seconds, I notice that you haven't provided unit tests. Please add them. We require 80% coverage.https://github.com/prebid/Prebid.js/tree/master/test/spec/modules

More importantly though, I don't understand what your module is actually doing. Note that I'm semi-technical, but don't have a lot of time to dig into this. Please explain how it's supposed to make the user segments available to bid adapters and why it needs a

.

[antlauzon]

@brettg can you point me at a RTD module that has a unit test example?

This real-time data module provides first-party Audigent segments that can be attached to bid request objects destined for different SSPs in order to optimize targeting. Audigent maintains a large database of first-party Tradedesk Unified ID to third party segment mappings that can now be queried at bid-time.

[bretg]

You can add tests to https://github.com/prebid/Prebid.js/blob/master/test/spec/modules/realTimeModule_spec.js

[antlauzon]

Not sure why CircleCI is failing but 'gulp lint' is working on my machine

[antlauzon]

@bretg can you kick off another CircleCI build? I am not sure what these failures are resulting from. gulp test passes locally.

[pm-harshad-mane]

Hello @anthonylauzon ,

I have triggered the CI job again, let's see.

[pm-harshad-mane]

Hello @anthonylauzon
Could you please add documentation in "audigentRtdProvider.md" file about

• how this sub-module is useful?
• what data will be shared by the module? the format
• how bidders can use the shared data?
  You might also want to add a usage example in https://github.com/prebid/Prebid.js/blob/master/modules/rtdModule/realTimeData.md

[antlauzon]

@pm-harshad-mane i've made the changes requested. it's not clear to me why CircleCI is failing. Are there non-deterministic tests in master?

[pm-harshad-mane]

@anthonylauzon the CI job is failing due to reasons unrelated to the changes you have made, I have restarted the CI job.

[antlauzon]

I think that the PR is ready for merge. Are there any other modifications you would like made?

[pm-harshad-mane]

@anthonylauzon can you provide test credentials to try-out Audigent module?
I just wanted to see it in a working example.

[antlauzon]

@pm-harshad-mane no credentials needed. just run gulp serve --modules=userId,unifiedIdSystem,rtdModule,audigentRtdProvider,rubiconBidAdapter and look at http://localhost:9999/integrationExamples/gpt/audigentSegments_example.html

[pm-harshad-mane]

LGTM @anthonylauzon
Thank you for providing a test-page, can you please add link to the test-page in the audigentRtdProvider.md ?

[antlauzon]

Integration example added to the readme.

[jsnellbaker]

Hi @anthonylauzon

I tried to load the test page you mentioned above with the noted modules, but it seems like I'm hitting a CORS error against the endpoint:

Access to XMLHttpRequest at 'https://seg.ad.gt/api/v1/rtb_segments?tdid=null' from origin 'http://localhost:9999' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I noticed the tdid was null in this case. Is there something extra I should do here?

[antlauzon]

@jsnellbaker you will need to use a localhost CORS allowing extension to allow the request to load or disable CORS for localhost in the browser.