Hi Team,
Would like to know if Adobe Analytics calls get triggered on pages which are tagged during external search engine for example Google Search crawl/indexing.
Background is we were getting huge number of 5XX errors for product detail pages in Google Search console during indexing, but the number does not match with 5XX errors in Adobe Analytics reports.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Technically yes, but these are generally excluded via Bot Rules.
If you have IAB rules enabled, or added custom Bot rules, all of those will be excluded from your reporting... You can access very limited information about these pages.
In the old Reports and Analytics, you could access "Page" and "Bot" (which bot) was hitting pages, all other dimensions were unavailable.
It looks like the integration with Workspace works much the same... there are a few metrics: Bot Page Views, Bot Occurrences, Bot Page View Ratio, and a "Bot Name" dimension. I can correlate these metrics with my standard "Page" dimension, but not with anything else (like my URL eVar).
If you have a Raw Data Feed set up and already being processed, you should be able to access all the data there, by looking at the "excluded" hits (rather than normally only looking at the hits not flagged as exclusion)
Technically yes, but these are generally excluded via Bot Rules.
If you have IAB rules enabled, or added custom Bot rules, all of those will be excluded from your reporting... You can access very limited information about these pages.
In the old Reports and Analytics, you could access "Page" and "Bot" (which bot) was hitting pages, all other dimensions were unavailable.
It looks like the integration with Workspace works much the same... there are a few metrics: Bot Page Views, Bot Occurrences, Bot Page View Ratio, and a "Bot Name" dimension. I can correlate these metrics with my standard "Page" dimension, but not with anything else (like my URL eVar).
If you have a Raw Data Feed set up and already being processed, you should be able to access all the data there, by looking at the "excluded" hits (rather than normally only looking at the hits not flagged as exclusion)