There aren’t any open sourced analytics adapters for Prebid Server, but there is an internal interface that host companies can use to integrate their own modules.
Below is an outline of how it’s done for both versions of the server.
Analytics adapters are subject to a number of specific technical rules. Please become familiar with the module rules that apply globally and to analytics adapters in particular.
Analytics modules are enabled through Viper configuration. You’ll need to define any properties in config/config.go which are required for your module.
Implement your module
Your new module belongs in the analytics/{moduleName} package. It should implement the PBSAnalyticsModule interface from analytics/core.go
Connect your Config to the Implementation
The NewPBSAnalytics() function inside analytics/config/config.go instantiates Analytics modules using the app config. You’ll need to update this to recognize your new module.
A simple filesystem analytics module is provided as an example. This module will log dummy messages to a file.
It can be configured with:
analytics:
file:
filename: "path/to/file.log
Prebid Server will then write sample log messages to the file you provided.
Define config params Analytics modules are enabled through the Configuration.
Implement your module Your new module org.prebid.server.analytics.{module}AnalyticsReporter needs to implement the org.prebid.server.analytics.AnalyticsReporter interface.
Add your implementation to Spring Context In order to make Prebid Server aware of the new analytics module it needs to be added to the Spring Context in org.prebid.server.spring.config.AnalyticsConfiguration as a bean.
The log module is provided as an example. This module will write dummy messages to a log.
It can be configured with:
analytics:
log:
enabled: true
Prebid Server will then write sample log messages to the log.