Background Hits and Legacy Processing Settings
Adjust settings in Virtual Report Suites or in the Analytics Admin Console to prevent hits being include in reporting.
Description description
Environment
- Customer Journey Analytics
- Analytics
Issue/Symptoms
Background hits are sent when an app is in a background state. Customers can use Virtual Report Suites to discard these hits from reporting. However, there is a setting in Analytics Admin Console where these hits can be disabled permanently. This article talks about how these hits can be disabled and how the processing gets affected by this setting.
Resolution resolution
Few years back, Analytics started processing background hits in reporting. Which would in turn result in the processing affecting the visits and visitors data. In order to prevent background hits from reporting, one can use the Virtual Report Suites. Visit here for more information.
There is a separate setting for disabling background hits in the report suite. Background hits processing can be disabled/enabled by going to Analytics › Admin › Report Suites › Edit Settings › App Management › App Reporting. By default, the setting is enabled.
Background hits in the data feed can be identified by using customer_perpective
column where the value of a background hit will be 1. In the url query string, the value is cp=1.
If the background hits are disabled, visit_num
and visit_page_num
will be set as 0, which tells the processing servers, not to include the hits in reporting. On the reporting side, a look up is done once per 24 hours, if those background hits needs to be ignored. So, the changes will affect in reporting only after 24 hours past the setting is changed.