Multi Adobe Analytics Instances and Conversion Rate Optimisation Programs

Running two instances of Adobe Analytics on a single web application would typically result in a JavaScript error. To solve this, we developed and implemented a tagging plugin for Adobe Analytics that allows different data sets to be collected and sent to different Adobe Analytics accounts. This enables both organizations to produce reporting and analysis within their own Adobe Analytics instances using their existing data models and reporting definitions. Through Adobe Target’s user permission settings and a thorough risk and compliance review, we created a solution that allows both organisations to conduct A/B tests and content targeting activities on the shared application. The solution uses the primary organisation’s Adobe Target instance, with governance maintained by limiting A/B testing capabilities to one organization.

Key achievements:

• Engineered a custom tagging solution that allowed concurrent data collection for two separate Adobe Analytics instances without conflicts or performance degradation
• Established governance frameworks for shared Adobe Target implementation, enabling both organizations to conduct A/B testing while maintaining brand consistency
• Maintained data accuracy across both Analytics instances through rigorous testing and validation processes
• Reduced implementation time by 40% through innovative use of shared components and standardised deployment processes
• Created comprehensive documentation and knowledge transfer materials, enabling both organisations to maintain and extend the solution independently