Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure analytics adapters per account #3809

Open
bretg opened this issue Jul 12, 2024 · 3 comments
Open

Configure analytics adapters per account #3809

bretg opened this issue Jul 12, 2024 · 3 comments
Labels

Comments

@bretg
Copy link
Contributor

bretg commented Jul 12, 2024

Analytics adapters don't currently support being configured per account like a proper module.

Since many PBS instances are multi-tenant, it's important that publishers trust that their traffic is not be analyzed by an analytics adapter being used by a different publisher.

Requirements:

  1. The PBS host company must be able to configure an analytics adapter that is invoked by all requests (adhering to privacy rules). This allows the host company to monitor its traffic, implement reporting, and handle fees if relevant. It's assumed that the host company will have a contract with each hosted account that allows them to enable this particular adapter.
  2. It would be nice if an account could opt out of the globally-configured analytics adapter.
  3. Individual accounts within a Prebid Server should be able to turn on any open source analytics adapter.
    1. Configuration of that analytics adapter should support account-specific details such as IDs, separate endpoints, different sampling rates, etc.
  4. Other accounts within that same Prebid Server should not have their traffic be routed through unapproved analytics adapters.
@bretg
Copy link
Contributor Author

bretg commented Jul 17, 2024

Discussed in committee. We agreed that in the long term, it makes sense to migrate analytics adapters to just be modules in a new hook, but that's bigger than needed for this project.

So for now, here's a proposed account-level config, based on what's already supported as described in https://github.com/prebid/prebid-server-java/blob/master/docs/application-settings.md:

  • analytics.modules..* - space for module-name analytics module specific configuration, may be of any shape

So the proposal is to add an enabled flag there. This needs to default to true or we could into a breaking change scenario. This of course can be set to false at the host level.

{
  analytics: {
    modules: {
      greenbids: {
        enabled: true,      // Defaults to true. This is the new thing. PBS-core looks for this and doesn't call the module if
        pbuid: "PUBID_FROM_GREENBIDS", // this should get merged into ext.prebid.analytics.greenbids with the request taking precedence.
        greenbidsSampling: 1.0  // this should get merged into ext.prebid.analytics.greenbids with the request taking precedence.
    }
  }
}

@bretg bretg moved this from Research to Triage in Prebid Server Prioritization Jul 26, 2024
@bretg bretg self-assigned this Jul 26, 2024
@bretg bretg moved this from Triage to Research in Prebid Server Prioritization Jul 26, 2024
@bretg bretg moved this from Research to Community Review in Prebid Server Prioritization Sep 5, 2024
@bretg
Copy link
Contributor Author

bretg commented Sep 6, 2024

Approved.

Global analytics adapters can be enabled at the host level. Vendor-specific analytics would be enabled per account.

@bretg bretg moved this from Community Review to Ready for Dev in Prebid Server Prioritization Sep 6, 2024
@bretg bretg removed their assignment Sep 16, 2024
@bretg
Copy link
Contributor Author

bretg commented Oct 8, 2024

done with PBS-Java 3.13

@bretg bretg added the PBS-Go label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Ready for Dev
Development

No branches or pull requests

1 participant