API 2.0 Missing Feature Parity with 1.4 – Report Suite Configuration & eVar Metadata (Migration Blocker)

🧾 Description

We are currently migrating from Adobe Analytics API 1.4 to 2.0 and have identified critical gaps that prevent us from fully deprecating API 1.4.

API 2.0 does not provide feature parity with 1.4 in terms of report suite configuration and variable metadata, which creates a blocker for automation, governance, and documentation use cases.

🚨 Key Gaps

1. Missing eVar Metadata

The API 2.0 /dimensions endpoint does not return essential configuration fields such as:

• expiration_type

• expiration_custom_days

• merchandising_syntax

• allocation_type

These fields were available in API 1.4 and are critical for:

• Automated documentation

• Data governance

• Attribution validation

• Migration verification

2. Missing Admin / Configuration Endpoints

API 2.0 does not support:

• Creating or updating eVars, props, events

• Managing Marketing Channel rules

• Accessing or modifying Processing Rules

Equivalent functionality existed in API 1.4 via ReportSuite.* endpoints.

🎯 Impact

This is not a minor limitation — it is a migration blocker.

We currently:

• Cannot fully migrate to API 2.0

• Must continue using API 1.4 in parallel

• Lose visibility into critical configuration logic

✅ Requested Solution

Option A (Preferred)

Extend existing endpoints to include missing metadata fields.

Option B

Provide new endpoints for full report suite configuration management (parity with 1.4).

💬 Additional Context

This is not a request for new functionality, but for feature parity with API 1.4, which is still required for enterprise use cases.