Adobe announced it will retire the v1.4 API on August 12, 2026. To prepare for that, we’ll release the new Adobe Analytics data source on June 30, 2026, as the replacement. This uses the newer v2.0 API.
To help you transition your queries away from the legacy data source, here is a mapping guide for the various features and functionality so you can replicate the same data in Adobe Analytics.
Note
The original Adobe Analytics data source has been renamed Adobe Analytics (Legacy), and the newer Adobe Analytics 2.0 has been renamed Adobe Analytics. When we mention “Adobe Analytics” below, we mean the 2.0 replacement version.
Comparing features
The table below lists some of the major differences between the two data sources, some of which will affect how you transition queries.
Feature | Adobe Analytics (Legacy) | Adobe Analytics |
|---|---|---|
Custom fields (such as eVars, custom metrics, and events) | Supported | Supported |
Field naming | May have a different naming than what Legacy had for the same field | May have a different naming than what Legacy had for the same field |
Segments | Supported | Supported |
“Get data matching every selected segment” setting | Supported | Supported |
OAuth 2.0 login | Supported | Supported |
Server-to-Server login | Supported | Supported |
Specific field availability | Check Field mapping guide | Check Field mapping guide |
“Large” query handling | Supported | Not supported. See Known Issues and Quirks for more guidance |
Subscriptions
All paid users of the original Adobe Analytics (Legacy) data source will be granted an automatic subscription for Adobe Analytics as part of the same package. The addition should happen on June 30, 2026, as part of the general release. If you have any questions or problems with your Adobe Analytics subscription after June 30, please contact our support team.
Known issues and quirks
Many common issues and quirks for Adobe Analytics are covered in the Good to know about Adobe Analytics guide, so that’s a good place to start. We’ll also cover some of the main issues that cause queries to fail with new data source.
It’s important to know that Adobe Analytics’ underlying API was designed differently than the Legacy one, so it cannot handle the same kinds of requests you may be used to.
API 2.0 was built for speed. Because of the focus on speed, the new Adobe Analytics API 2.0 really doesn’t like complicated queries with a lot of dimensions, lots of custom fields, or daily breakdowns for a long date range.
Rate limits
The API only allows one dimension per API request, so while Supermetrics is doing some magic to stitch multi-dimensional queries together, this adds to the number of separate requests, which runs into the other major issue of rate limits.
Adobe Analytics has pretty tight rate limits (12 requests every 6 seconds, 120 calls per minute). This means that those multi-dimensional requests are going to eat that quota up quickly, leading to queries that fail and give you a frustrating experience. Especially, Data Studio’s behavior to refresh all queries on a report page at once can trigger this problem.
Shorter timeouts
Also, the API has a 60-second timeout for requests. This means that if it takes a long time to assemble data in the API, such as with custom fields or complex segments, the request will likely time out and fail the query.
Working around the limitations
With those limitations in mind, Supermetrics (and Adobe) recommends the following considerations when recreating your Legacy queries in Adobe Analytics:
Simple is better. Keep the query dimensions limited (5 or fewer). Keep the number of segments used limited. Keep custom fields, especially dimensions, low.
If using daily breakdowns, keep the date range as short as possible. It’s better to merge the new day’s data with the historical data than to do giant long-range pulls. Features like the Combine new results with old setting in Google Sheet or data warehouse solution with daily imports can help.
Avoid multi-year requests. It’s better to pull the historical data in smaller chunks, like weekly or monthly, and merge those together.
If using Data Studio, try to keep the number of chart elements using Adobe Analytics on the same page low to prevent the rapid-fire request effect that can lead to rate limiting. Use tables that combine metrics rather than individual scorecards. Or use a data warehouse to store Adobe Analytics data and pull that data into Data Studio, so rate limits are not a factor.
You’ll almost certainly need to redesign or break apart some queries to work around the differences and limitations of the 2.0 API. Larger queries that the Legacy version could handle before simply won’t work with the tighter rate limits and timeouts in Adobe Analytics.
Make sure to set aside time to redesign your reporting flows to accommodate these limitations before Adobe Analytics (Legacy) sunsets on August 12, 2026.
Transitioning queries
Currently, no migration tool is available. You’ll need to recreate the queries in your chosen destination using Adobe Analytics.
Select the Adobe Analytics data source and go through the Adobe login process for OAuth, or use the OAuth Server-to-Server connection. Adobe Analytics has the same access and permissions requirements as Adobe Analytics (Legacy), so you can use the same login method as before. More details can be found in the connection guide.
Note that the account names (the Report Suites) may appear with slightly different names in the connection/account management lists:
Adobe Analytics tends to show the email account used for login
Adobe Analytics (Legacy) shows the management account name
For data warehouse and data lake users: We have a basic standard table group available for Adobe Analytics that you can use as a starting point.
Field mapping guide
The following set of tables shows the mapping between metrics and dimensions in Adobe Analytics (Legacy) and Adobe Analytics to help you recreate queries. Note that not all fields were ported over or even supported in API v2.0. The new API may also include features not available in the legacy version.
Custom fields
Both versions support various types of custom fields, such as metrics, dimensions, eVars, and events. However, sometimes the display name appears differently in each version. If you notice that you can’t find the same custom field in Adobe Analytics, please contact our support team for further assistance.
Metrics
Adobe Analytics (Legacy) | Adobe Analytics |
|---|---|
Instances | Occurrences |
Page views | Page views |
Total page views | Page views |
Total visits | Visits |
Average time spent on page (min) | Average time spent on site (min) |
Entries | Entries |
Entrance rate | Entry rate |
Exits | Exits |
Exit rate | Exit rate |
Bots | - |
Visits | Visits |
Unique visitors | Visitors |
Return visits | - |
Daily return visits | - |
Hourly visitors | Use Visitors with Hour dimension |
Hourly total visitors | - |
Weekly visitors | Use Visitors with Week dimension |
Weekly total visitors | - |
Monthly visitors | Use Visitors with Month dimension |
Monthly total visitors | - |
Yearly visitors | Use Visitors with Year dimension |
Yearly total visitors | - |
Single page visits | Single page visits |
New visitors | - |
New visitor rate | - |
Average visit depth | Average visit depth |
Bounces | Bounces |
Bounce rate | Bounce rate |
Path views | - |
Total time spent (min) | - |
Total time spent (h:m:s) | Total time spent (h:m:s) |
Average page depth | Average page depth |
Average time spent on site (min) | Average time spent on site (min) |
Average time spent on site (h:m:s) | Average time spent on site (h:m:s) |
Mobile views | Mobile views |
Mobile visitors daily | - |
Mobile visits | - |
Mobile carrier | - |
Revenue | Revenue |
Total revenue | Revenue |
Lifetime revenue | - |
Lifetime total revenue | - |
Participation revenue | - |
Lifetime participation revenue | - |
Orders | Orders |
Total orders | Orders |
Lifetime orders | - |
Lifetime total orders | - |
Participation orders | - |
Lifetime participation orders | - |
Units | Units |
Total units | - |
Lifetime units | - |
Lifetime total units | - |
Participation units | - |
Lifetime participation units | - |
New customers | - |
Returning customers | - |
Loyal customers | - |
Daily customers | - |
Weekly customers | - |
Monthly customers | - |
Quarterly customers | - |
Yearly customers | - |
Checkouts | Checkouts |
Total checkouts | - |
Lifetime checkouts | - |
Lifetime total checkouts | - |
Participation checkouts | - |
Lifetime participation checkouts | - |
Carts | Carts |
Total carts | - |
Total cart view | - |
Lifetime carts | - |
Lifetime total carts | - |
Participation carts | - |
Lifetime participation carts | - |
Cart views | Cart views |
Cart additions | Cart additions |
Cart removals | Cart removals |
Lifetime cart views | - |
Total cart additions | - |
Total cart removals | - |
Lifetime cart additions | - |
Lifetime cart removals | - |
Lifetime total cart views | - |
Lifetime total cart additions | - |
Lifetime total cart removals | - |
Participation cart views | - |
Participation cart additions | - |
Participation cart removals | - |
Lifetime participation cart views | - |
Lifetime participation cart additions | - |
Lifetime participation cart removals | - |
Reloads | Reloads |
Video views | - |
Video visits | - |
Video visitors daily | - |
Video time | Content time spent |
Video start | Media starts |
Video complete | Content completes |
Video segment views | - |
Video ad start | - |
Video ad complete | Ad completes |
Social mentions | - |
Social reach | - |
Social total sentiment | - |
Social like adds | - |
Social page views | - |
Social post views | - |
Social Facebook storytellers | - |
Social Facebook stories | - |
Social recommends | - |
Social comments | - |
Social subscribers | - |
Social posts | - |
Dimensions
Adobe Analytics (Legacy) | Adobe Analytics |
|---|---|
Year | Year |
Year of week (Sun-Sat) | Year of week (Sun-Sat) |
Year of week (Mon-Sun) | Year of week (Mon-Sun) |
Year & Month | Year & Month |
Year & week (Sun-Sat) | Year & week (Sun-Sat) |
Year & week (Mon-Sun) | Year & week (Mon-Sun) |
Week (Sun-Sat) | Week (Sun-Sat) |
Week (Mon-Sun) | Week (Mon-Sun) |
Day of week | Day of week (Sun-Sat) |
Day of week (Sun-Sat) | Day of week (Sun-Sat) |
Day of week (Mon-Sun) | Day of week (Mon-Sun) |
Date | Date |
Day of month | Day of Month |
Hour | Hour |
Report suite ID | Account ID |
Report suite name | Account |
Account | Account |
Account ID | Account ID |
Segment | Segment |
Segment ID | Segment ID |
Referrer | Referrer |
Referrer Type | Referrer Type |
Referrer domain | Referring domain |
Referring domain (original) | Original referring domain |
Visit length | - |
Time prior to event | Time prior to event |
Return frequency | Return frequency |
Visit number | Visit number |
Browser | Browser |
Browser type | Browser type |
Browser width | - |
Browser height | - |
Operating system | Operating system |
Connection type | Connection type |
Cookies enabled | - |
Java enabled | - |
Javascript enabled | - |
JavaScript version | - |
Monitor color depth | - |
Monitor resolution | - |
Mobile audio support | - |
Mobile carrier | - |
Mobile color depth | - |
Mobile cookie support | - |
Mobile device name | Mobile device name |
Mobile device number transmit | - |
Mobile device type | Mobile device type |
mobile DRM | - |
Mobile image support | - |
Mobile information services | - |
Mobile Java version | - |
Mobile mail decoration | - |
Mobile manufacturer | - |
Mobile max bookmark URL length | - |
Mobile max mail URL length | - |
Mobile net protocols | - |
Mobile OS | Operating system |
Mobile push to talk | - |
Mobile screen height | - |
Mobile screen size | - |
Mobile screen width | - |
Mobile video support | - |
Domain | Domain |
Top level domain | - |
Server | Server |
Site section | Site section |
Entry page | Entry page |
Entry page (original) | Entry page (original) |
Page | Page |
Pages not found | - |
Page depth | - |
Path length | - |
Custom link | Custom link |
Download link | Download link |
Exit link | Exit link |
Video | - |
Video ad | - |
Video segment | - |
Video content type | - |
Videos | - |
Video players | - |
City | Cities |
Country | Countries |
Geographical region | Region |
Designated market area | US DMA |
State/region | US States |
ZIP/postal code | - |
Timezone | - |
Search engine | Search engine |
Search Engine - paid | Search engine (paid) |
Search engine - natural | Search engine (natural) |
Search keyword | Search engine keyword |
Search keyword - paid | - |
Search keyword - natural | Search engine keyword (natural) |
All search page rank | - |
Social term | - |
Social content provider | - |
Social author | - |
Social link | - |
Social terms list | - |
Social average sentiment | - |
Social property | - |
Social asset tracking code | - |
Account summary | - |
Customer loyalty | Customer loyalty |
Product | Product |
Tracking code | Tracking code |
Category | Category |
First touch channel | First touch channel |
First touch channel detail | First touch channel detail |
Last touch channel | Last touch channel |
Last touch channel detail | Last touch channel detail |
Survey base | - |
Test & Target | Test & Target |