BlueConic Experiences now supports multiple independent instances of the same integration — giving teams separate credentials, mappings, and settings for every use case.

If your organization operates across regions, business units, or distinct data flows, you've likely run into the limitation of managing everything under a single integration instance. Different teams need different credentials. Different regions need different mappings. A change for one shouldn't break another.

Multiple integration instances in BlueConic Experiences solves this cleanly. You can now configure more than one instance of the same integration within a workspace — each independently named, credentialed, and mapped. An instance for your EU region and another for North America. One for your retail brand, another for your enterprise line. Each can be activated, paused, or edited without affecting the others.

This makes it significantly easier to scale data activation across complex organizational structures without workarounds or data routing conflicts.

Benefits:

• Supports independent credentials, mappings, and data handling settings per instance
• Enables regional and business-unit-level data routing without overlap or conflict
• Instances can be disabled without deletion, preserving configuration for future use
• Available across all supported integrations in BlueConic Experiences

To learn more, read our documentation.