Recently, I have been working on a project where we integrate ODP Audiences with Feature Experimentation and I noticed one limitation that makes testing and environment setup harder than expected.

In ODP, we have separate environments, for example int/preprod/prod, each of them has its own URL and public/private keys.

In Feature Experimentation, we usually work with one project that contains multiple environments (added in settings), Feature flags are then configured and evaluated separately per environment inside the same project.

The problem is that the ODP Audiences integration is configured only once for the whole Feature Experimentation project. That means I can provide only one ODP URL and one set of keys.

Because of that, I cannot map FE environments to matching ODP environments, for example:

FE int & other test env → ODP int
FE preprod → ODP preprod
FE prod → ODP prod

The only workaround seems to be creating separate Feature Experimentation projects for each ODP environment, but that is not very convenient and adds extra maintenance. For large projects, this involves a huge amount of work and the additional task of maintaining feature flags with the appropriate states across multiple projects.

It would be useful if ODP Audiences configuration could be done per Feature Experimentation environment, instead of only per project.

Expected behavior:

each FE environment can have its own ODP Audiences Integration settings page

This would make the integration easier to test.