PBJS: document new genericAnalyticsAdapter module
#4092
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
| @@ -0,0 +1,13 @@ | |||
| --- | |||
| layout: analytics | |||
| title: Generic | |||
There was a problem hiding this comment.
I'm worried generic might be confusing and lead to a vendorless module being used by a vendor. The name change won't prevent this from happening, but perhaps we want to be more clear this is meant to send events to the pub controlled cdn.
There was a problem hiding this comment.
I actually planned to accept a gvlid configuration parameter, to allow this to be truly generic, but cut it once I realized that a) GDPR enforcement is turned off by default for purpose 7; and b) the current enforcement mechanism would need more refactoring than I hoped.
Would that be preferable than trying to restrict this to pub-controlled endpoints only? I'm thinking that especially for those analytics backends that just expect to get data dumped into a globally defined function, it's a bit silly to require an adapter that just provides that function's name. Examples:
- https://github.com/prebid/Prebid.js/blob/master/modules/pubstackAnalyticsAdapter.js
- https://github.com/prebid/Prebid.js/blob/master/modules/optimonAnalyticsAdapter.js
- (I'm sure there's others)
if we add a way to specify the gvlid, those could easily be fronted by this module.
* PBJS: document new `genericAnalyticsAdapter` module * Try using "N/A" as gvlid for generic analytics * Move generic analytics docs to its own page * softVendorExceptions, generic analytics note on gdpr enforcement * add min version Co-authored-by: Chris Huie <phoenixtechnerd@gmail.com>
🏷 Type of documentation
📋 Checklist