As we prepare to release Adobe Analytics 2.0 to general availability, we’ll take the opportunity to make several changes to polish the data source and resolve issues. Between now and June 30, 2026, we’ll be releasing the following updates.
Special note for data warehouse users
Standard table groups will not be updated at this time, which means that the deprecated fields will return empty values after June 30, 2026. Backfilling data after the sunset date will also overwrite data with empty values and should be avoided.
Keep in mind that removing fields from your custom tables can lead to that field being removed from your tables in the data warehouse, in particular, if you're using our BigQuery, Snowflake, Azure Synapse, Azure SQL DB, or AlloyDB integrations listed in your storage destinations on the Supermetrics Hub.
For other destinations, such as our direct BigQuery integration on Google Cloud, AWS S3, Google Cloud Storage, Azure Storage, and SFTP, only shards and files are overwritten for the dates you're backfilling and transferring daily within your refresh window.
If you want to preserve the historical data of those fields in your destination, you have two options:
Keep the affected fields in the custom table, and they will start returning empty values after June 30, 2026. If there are replacement fields available, you can add them to the custom table and continue using your custom table as before in your reports.Note that if you run a backfill after June 30 for such custom tables to fetch historical data, such as for year 2024, this might also overwrite your historical data for the affected fields with empty values.
Rename your custom tables in the Table Manager, and make the necessary changes to the custom table according to the information in this article in case your custom table contains combinations of fields that will lead to transfer failures after June 30, 2026. Renaming custom tables in the Table Manager will lead to new tables or files being generated in your destination.
If any of your reporting is dependent on the affected custom tables, you'll either need to point the reports to the new tables, or combine the data of the new tables with the tables that contain your historical data (using SQL, ETL tool, or by combining the data inside a BI tool), so that your reports contain both the historical and the latest data.
Note that you need to rename the custom tables, not the table group. Renaming the table group won't have any impact on the transfer, and this scenario would lead to you losing data for the fields you removed or replaced in your custom tables.
Data source renaming
As Adobe Analytics 2.0 will be the main version of the data source going forward, we’ll rename both it and the original Adobe Analytics to make this clear:
Adobe Analytics will be renamed Adobe Analytics (Legacy)
Adobe Analytics 2.0 will be renamed Adobe Analytics.
Field additions
We’ll add a new version of the “Occurrences” metric with the correct field ID, since it isn’t actually instances and it’s confusing.
The old version of the metric will be renamed “Occurrences (deprecated)” and sunset.
Field deprecations
The following fields will be deprecated as of June 30, 2026, and no longer provide data.
Field ID | Field display name |
| Day of week |
| Visitor ID |
| Experience Cloud visitor ID |
| IP address |
| Single page visit |
| Visit page number |
| Browser width (bucketed) |
| Browser height (bucketed) |
| Plugin support |
| Mobile OS (legacy) |
| Path length |
| State (legacy) |
| Timezone |
| Purchase ID |
| ClickMap page |
| ClickMap region |
| ClickMap link |
| ClickMap link by region |
| Analytics for Target |
| Occurances (deprecated) |
| Video ad start |
| ClickMap pages |
| ClickMap regions |
| ClickMap links |
| ClickMap link regions |
| Mobile views |
| Single access visits |
| Average time spent on page (min) |
| Hourly visitors |
| Daily visitors |
| Weekly visitors |
| Monthly visitors |
| Quarterly visitors |
| Yearly visitors |
| Activity conversion |
Field renames
The following fields will be renamed for clarity and to better align with their UI names in report suites.
Field ID | Original Field Display Name | NEW Field Display Name |
| Referrer domain | Referring domain |
| Referrer domain (original) | Original referring domain |
| Geographic city | Cities |
| Geographic country | Countries |
| Geographic region | Regions |
| Geographic designated market area | US DMA |
| State/region | US state |
| Video name | Content name (variable) |
| Marketing channels | Marketing channel instances |
| Video starts | Content starts |
| Video started | Media starts |
| Video progress 10% | Progress marker 10% |
| Video progress 25% | Progress marker 25% |
| Video progress 50% | Progress marker 50% |
| Video progress 75% | Progress marker 75% |
| Video progress 95% | Progress marker 95% |
| Video completed | Content completes |
| Video time | Content time spent |
| Video total time | Media time spent |
| Video ad time | Ad time spent |
| Video ad complete | Ad completes |
| Total page views | Page views |
| Total time spent (seconds) | Total seconds spent |
| Seconds per visit | Time spent per visit (seconds) |
| Seconds per visitor | Time spent per visitor (seconds) |
| Entrance rate | Entry rate |
| Total time spent | Total time spent (h:m:s) |
| Total visits | Visits |
| Total visitors | Visitors |
| Avg visit depth | Average visit depth |
| Avg page depth | Average page depth |
| Avg minutes on site | Average time spent on site (min) |
| Avg time on site | Average time spent on site (h:m:s) |
| Total orders | Orders |
Field removals
Any field that has not been actively used in the last 180 days or was marked deprecated prior to that, will be removed from the data source field list completely. This is to streamline the field selection experience and make the list easier to navigate.
Upon request, we can provide a full list of all fields that were removed. Please also let us know if you need something added back!
Other improvements
We’ll be updating and adding descriptions to all fields.
Filtering, especially with custom fields or when using regular expressions, has been improved!
We’re here for you
If you have any questions or concerns about this change, contact our support team.