Permutive RTD Module: merge external submodule params

[AntonioGargaro]

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

Cohort activation within Permutive's RTD module is failing to be applied with option 1, which let publishers set acBidders through Permutive's platform. We require this fix where the RTD module attempts to retrieve this config from LS or our Permutive SDK. This lets publishers modify their Permutive <-> Prebid integration without code changes.

We read from LS on initialisation in the event that the Permutive SDK has not initialised before the config is required. Every call to retrieve our config will attempt to interact with Permutive's prebid addon which will have this config available in memory, otherwise fallback to cache.

Config Priority

1. customModuleConfig <- set by publisher with pbjs.setConfig
2. permutiveRtdConfig <- set by the publisher using the Permutive platform
3. defaultConfig

The configuration module is deeply merged in reverse priority order. This means that the highest priority config (customModuleConfig) defined by .setConfig within Prebid will be merged last and overwrite other configurations.

Other information

N/A

[patmmccann]

j

[patmmccann]

you want the configuration coming from window.permutive to override how the publisher configures the module in prebid?

[AntonioGargaro]

The name is misleading here, the configs are merged in reverse priority order as configs are merged left to right. The priority is,

1. customModuleConfig <- set by publisher with pbjs.setConfig
2. permutiveRtdConfig <- set by the publisher using Permutive.
3. defaultConfig

Therefore, anything set by the publisher will take priority over what is set within Permutive. I'll add some comments explaining this.

• add docs

[patmmccann]

thanks!

[ChrisHuie]

@AntonioGargaro the integration tests don't appear to have ran on this pr. This is usually because the submitter is following a fork of prebid inside of CircleCI instead of the main Prebid project. You should be able to unfollow your fork in CircleCI and that should kick off testing.

[AntonioGargaro]

@ChrisHuie Should be running now 👍