Description
Currently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:
Fetch and update eVars, props, events, and classifications.
Retrieve configured processing rules for a given report suite.
Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.
For many enterprise-scale implementations, this functionality is not just convenient — it is essential.
Proposed idea
Extend Adobe Analytics 2.0 API to include endpoints for:
Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.
Processing Rules: Fetch and (if possible) update processing rules for a given report suite.
Cross-Suite Comparison: Provide efficient ways to compare variable configurations between report suites via API.
This would ensure continuity for projects currently relying on 1.4, while aligning with the modernized API framework.
Benefits / Use Cases
Scalability: Easily update or configure variables across multiple report suites in bulk instead of relying solely on the UI.
Transparency: Retrieve all processing rules in one call, making it much easier to audit mapping when there are 100+ rules.
Consistency: Compare variable configurations across report suites to ensure alignment in enterprise environments.
Efficiency: Save time and reduce manual effort by automating repetitive admin tasks.
Call to Action
Please consider adding these configuration endpoints to the 2.0 API roadmap to avoid losing critical functionality when 1.4 is deprecated. This would greatly benefit customers managing multiple report suites and complex implementations.
