Skip to content

Latest commit

 

History

History
97 lines (74 loc) · 2.89 KB

azerionedgeRtdProvider.md

File metadata and controls

97 lines (74 loc) · 2.89 KB
layout title display_name description page_type module_type module_code enable_download vendor_specific sidebarType
page_v2
Azerion Edge RTD Provider
Azerion Edge RTD Provider
Client-side contextual cookieless audiences.
module
rtd
azerionedgeRtdProvider
true
true
1

Azerion Edge RTD Provider

Client-side contextual cookieless audiences.

Azerion Edge RTD module helps publishers to capture users' interest audiences on their site, and attach these into the bid request.

Please contact [email protected] for more information.

Maintainer: azerion.com

{:.no_toc}

  • TOC {:toc}

Integration

Compile the Azerion Edge RTD module (azerionedgeRtdProvider) into your Prebid build, along with the parent RTD Module (rtdModule):

gulp build --modules=rtdModule,azerionedgeRtdProvider

Set configuration via pbjs.setConfig.

pbjs.setConfig(
    ...
    realTimeData: {
        auctionDelay: 1000,
        dataProviders: [
            {
                name: 'azerionedge',
                waitForIt: true,
                params: {
                    key: '',
                    bidders: ['improvedigital'],
                    process: {}
                }
            }
        ]
    }
    ...
}

Parameter Description

{: .table .table-bordered .table-striped }

Name Type Description Notes
name String RTD sub module name Always "azerionedge"
waitForIt Boolean Required to ensure that the auction is delayed for the module to respond. Optional. Defaults to false but recommended to true.
params.key String Publisher partner specific key Mandatory. The key is required for the module to work. If you haven't received one, please reach [email protected]
params.bidders Array Bidders with which to share segment information Optional. Defaults to "improvedigital".
params.process Object Configuration for the Azerion Edge script. Optional. Defaults to {}.

Context

As all data collection is on behalf of the publisher and based on the consent the publisher has received from the user, this module does not require a TCF vendor configuration. Consent is provided to the module when the user gives the relevant permissions on the publisher website.

As Prebid.js utilizes TCF vendor consent for the RTD module to load, the module needs to be labeled within the Vendor Exceptions.

Testing

To view an example:

gulp serve-fast --modules=rtdModule,azerionedgeRtdProvider

Access http://localhost:9999/integrationExamples/gpt/azerionedgeRtdProvider_example.html in your browser.

Run the unit tests:

npm test -- --file "test/spec/modules/azerionedgeRtdProvider_spec.js"