Multi-Level Breakdowns with itemId Persistence in Adobe Analytics API 2.0 response.

[#1]

Description:

Enhance the Adobe Analytics API 2.0 to include the itemId value from the parent request in subsequent multi-level breakdown responses. This will facilitate seamless data joining across API responses.

Why is this feature important to you?

• Simplified Data Integration:
  • Currently, multi-level breakdowns require external data management to link parent and child response data due to the absence of the parent itemId in child responses.
  • This feature would enable direct and efficient data joining, reducing complexity and potential errors.
• Improved Data Analysis Efficiency:
  • Many analytical use cases rely on combining data from multiple API responses.
  • The proposed enhancement would streamline this process, enabling faster and more accurate data analysis.
• Enhanced API Usability:
  • The lack of itemId persistence makes multi-level breakdowns cumbersome.
  • This feature would make the API more intuitive and user-friendly.

How would you like the feature to work?

• itemId Inclusion in Child Responses:
  • When a breakdown request is made, the response should include the itemId from the parent request that triggered the breakdown.
  • This itemId should be included as a field within the response payload, allowing for direct linking of data.
• Example Scenario:
  • If a first-level request (Resp1) returns a list of page URLs with itemIds, and a second-level request (Resp2) breaks down a specific page URL by marketing channel, Resp2 should include the itemId from the corresponding row in Resp1.

Current Behavior:

• itemId Absence in Child Responses:
  • Currently, the itemId value from the parent request is not included in the child (breakdown) response, even though it is used in the child request's metricFilters.
  • This necessitates external data mapping and lookup tables to link parent and child data.
• Data Joining Challenges:
  • One has to manually store or track and associate itemIds across multiple API responses, increasing the risk of errors and complicating data integration.
  • As shown in the image, 2nd level response, the marketing channel breakdown does not contain the first level information i.e. evar27, or the itemID that it is related to.
    
    

-