API 2.0 needs to handle creation/modification of variables (props, eVars, events)

The Adobe Analytics API 1.4 is scheduled for decommissioning this summer, yet critical endpoints from this legacy API have not been integrated into API 2.0. This creates a significant gap in functionality that will impact many organizations relying on programmatic management of Adobe Analytics configurations.

Missing Critical Functionality:

The most important missing feature is the ability to programmatically:

• Create new Adobe Analytics variables (props, eVars, events)
• Modify existing variable configurations
• Delete variables when no longer needed

Currently, API 2.0 forces users to manually manage these variables through the Adobe Analytics interface, which is:

• Time-consuming for bulk operations
• Error-prone for complex configurations
• Incompatible with automated deployment workflows
• Difficult to integrate with CI/CD pipelines

Business Impact:

Without this functionality in API 2.0, organizations will lose the ability to:

• Automate variable management across multiple report suites
• Maintain consistent configurations through code
• Integrate Analytics setup into their development workflows
• Scale variable management efficiently

Requested Solution:

Please add endpoints to API 2.0 that provide full CRUD (Create, Read, Update, Delete) operations for Adobe Analytics variables, matching or exceeding the functionality currently available in API 1.4.

This is essential for maintaining operational efficiency and preventing workflow disruptions when API 1.4 is discontinued.

En savoir plus :

1image.png