Open jdwieland8282 opened 8 months ago
I think with documentation we can completely solve:
if crypto.getRandom.... or Math.random() > .5 then set a else set b
if a setconfig(one way)
if b setconfig(other way)
googletag.setTargeting(test=[a or b])
and/or the generic analytics adapter could be aware of the test
There seems to be a bit of a gap expressing tests to analytics adapters, but if we form a convention, we should be good.
how about
pbjs.mergeConfig {
analyticsLabels: {
test1 : a,
test2 : d }
}
Then we could have genericAnalytics pick up analyticsLabels
by adding analyticsLabels
to each event and making sure it went over the wire. Other analytics modules could be Pr'd to do the same by their maintainers.
@jdwieland8282 tentatively marking ready for dev but we'd love your feedback before getting started
cc @3link
@patmmccann Very nice initiative! Thanks for tagging. LGTM.
So long as the requirements are met I express my support for this implementation approach.
This is marked in progress - is it in progress?
Problem
Publishers are unable to test and run experiments natively in Prebid and must rely on partners to help set up tests & control groups when they want to test various
setConfig()
objects.example
A publisher may wish to test CPM change for 2 different
setConfig()
s1
2
UseCase
Requirements
setConfig()
should support a sample rate int for the test cohort. Where n percent of the time thesetConfig()
loads one way, and n of the time it loads a different way.