Skip to main content
Level 1
September 16, 2026

Adobe 2.0 API - segments

  • September 16, 2026
  • 2 replies
  • 15 views

Hi all,

I'm currently having trouble integrating traffic data from Adobe into our marketing platform (Datorama) using the 2.0 API.

With the legacy 1.4 API, we were able to apply multiple segments within the Extended Properties section to filter the data. For example, excluding business-related visits, upgrade journeys, and other traffic types. However, in the 2.0 API connector, I appear to be limited to a single segment and cannot add additional segment filters.

Can anyone confirm whether this is a restriction of the 2.0 API, or if there is an alternative approach to apply multiple filters/segments within a single stream?

Any guidance or workarounds would be greatly appreciated.

Thanks,

H

2 replies

Jennifer_Dungan
Adobe Champion and Community Advisor
Adobe Champion and Community Advisor
September 16, 2026

Hi ​@magnetic_Odyssey7011,

 

You can definitely add multiple segments into your API 2.0 calls.

 

Here is a little trick that can help you with building your API calls… Workspaces use the API to pull the data, and if you enable the debugger, you can access those API calls.

 

Now, this will add a new icon onto your freeform tables:

 

 

Clicking on it will allow you to choose the API call for the Sparkline or the Freeform Table:

 

 

The Next choice will allow you to choose the API call by timestamp:

 

 

Note: some tables require multiple API calls, but this will also show the history of the API calls if like me, you built the table after the debugger was enabled…. each of these represents me stacking new segments and all of the changes… so I know that I only need the last timestamp. If you aren’t sure, make sure your table is completely built, then load the workspace fresh to see what APIs were called.

 

When you click on one of the timestamps, it will bring up a new screen showing the API call in multiple formats; XML, cURL, JSON (as well as the response for each of them)

 

 

 

 

You can see that these API requests have 3 segments applied and the formatting of how to add them.

 

 

I hope this helps.

Level 1
September 17, 2026

Thank you for your support. 

The segments can be added in the platform, however, during processing this will fail and the outcome is “invalid”. My other workaround was creating a segment containing all three segments in one which would bypass the new restriction, but this gave me inaccurate data (compared to when the segments are split out in the table). 

Are there any other workarounds to use 3 segments in one data stream? 

Thanks,

H