Prebid analytics adapters receive auction events from the page. They are how a vendor records bids, timeouts, and wins inside Prebid.js.
pbjs.enableAnalytics turns an adapter on. The adapter has to be compiled into your Prebid build. Each vendor defines its own options. Prebid's example includes a sampling rate for adapters built the standard way. Some vendors sample on their side instead. includeEvents and excludeEvents filter what that adapter is told.
An analytics adapter sees the auction. It does not decide the auction. Floors, timeouts, and refresh still behave the same if you remove the adapter. What you lose is the record.
bidtune's measurement is not this API. The tag records rendered Prebid impressions and the settings that applied on that auction. You can keep the analytics adapter you already run.
Call this once the library is loaded, with the provider code from that adapter's Prebid doc. analyticsA below is Prebid's placeholder, not a real vendor.
pbjs.enableAnalytics([{
provider: "analyticsA",
options: {
sampling: 0.25
}
}]);A sampled stream of bid events is how you see who timed out, who responded under the floor, and which auction a rendered ad came from. Sampling keeps a busy page from sending every event.
An adapter that is not in the build silently does nothing. Sampling that is too low hides a bidder who only fails sometimes. Two collectors that define an impression differently will not match, and averaging them does not fix the definition. Debug logging is not a substitute for a sampled production feed.
enableAnalytics.