Why is pageviews and clicks different for the same url in diff report suite?

[user70977]

I have the same table set up in 2 diff report suites. One of the report suite is global which has everything and another is a subset of the global. Both should be collecting data for our homepage. When I pull in 1 homepage url in both report suites, I am seeing minor discrepancies (~5%) between # of pageviews and clicks when I use the 2 diff report suites. Is that expected and why?

If not, is there something we need to update in our set up?

[Vinay_Chauhan]

Hi @user70977 

A slight difference in pageviews and clicks across two report suites (especially if one is global and the other is a subset) can happen for a few reasons -

• Even though both suites are meant to track the same pages, there could be slight differences in how tracking is deployed. For example, if one report suite is included conditionally or initialized later in the page load, it may miss some events.
  
  

• The subset suite may have virtual report suite filters, bot rules, or segment logic applied that the global suite doesn’t.
  
  

• If there's any processing rule difference (like how hits are included/excluded), it can impact counts.
  
  

• If link tracking is custom-configured, it's possible that click calls aren't consistently sent to both suites.

5% isn't a massive gap, but it’s good to verify that both suites are implemented the same way and receiving the same data. I’d recommend double-checking -

• The s.t() and s.tl() calls in the debugger or Network tab

• If both suites are being called on the same hit

• Any segments, filters, or processing rules that might differ between the suites

Hope that helps!

[pradnya_balvir]

Hi @user70977 ,

Yes, a 5% difference is common and usually not a cause for concern. It often happens due to differences in how and when data is collected or processed in each report suite.

Reasons are:

1. Tracking Implementation Differences

Even though the same page is being tracked:

• The global report suite may have different variables or plug-ins firing

• One suite may be using virtual report suites with filters

• Or using different logic for bot filtering, link tracking, or fallback behaviors

2. Data Collection Timing / Beacon Failures

• If the tracking call fails (e.g., network errors), it may only register in one suite and not the other

• Mobile vs. desktop traffic may behave differently across suites

3. Bot Filtering Rules

• One suite may have stricter bot rules (e.g., IAB filtering enabled in one but not the other)

• This will reduce pageviews and clicks differently in each suite

4. Processing Rules or VISTA Rules

• Custom processing rules (like overwriting props/eVars or excluding traffic) may differ

• E.g., Clicks on a CTA might be suppressed in one RS due to internal filtering

5. Marketing Channels or Campaign Classification Differences

• Sometimes click events depend on campaign attribution, which might differ slightly across suites depending on classification rules

Thanks.

Pradnya

[DanIMS1]

Hi @user70977,

With the two report suites, one is the global and the second is a subset of the global. Do you mean this is a virtual report suite? This is typically how you should typically deal with a global report suit and then a subset of that report suites data, otherwise you end up paying for the same hit twice.

If so and you are looking at the same URL for both report suites then the discrepancy will be caused by the segmenting value you are using for the segment in the virtual report suite. The value would be present in the hits with the URL you are seeing in the virtual report suite and not in all the hits of the URL you are seeing in the global report suite.

If you are using two different report suites (i.e. sending the data directly to the individual to the report suites, one hit to the global and the same hit to the subset), then there will be an issue with the implementation or set up. Here are a few reasons that would cause the discrepancies you are seeing:

• There could be a processing rule, bot rule or filter that is being triggered in one of the report suites that is removing some of the hits. Check these to make sure they all align.
• There could be additional rules that are firing for one report suite that aren't being triggered for the other. Check the implementation to ensure that the hits are coming from the same source and not two separate launch profiles with different rules.

Hope this helps.
Thanks,
Dan

[Jennifer_Dungan]

When you say 2 different suites, do you mean two completely separate suites that you are tracking to (rsid123 and rsid55 for example)? Or do you mean you have a global suite and a virtual suite that gets its data from the global?

If you have two actual tracking suites, are they tracked in the same calls? Or separate calls that could result in one of the rules failing? 

I assume when you said "subset" that you are talking about a Virtual Report suite, but I still had to check the above... the likely cause here is that the definition for the Virtual Report suite isn't catching some of the hits that exist in the global suite... this could be due to some tracking calls are missing a value that is being used by the Virtual Suite (so you see it in global but not in the virtual) or the segment definition isn't matching on some of the hits, so you may need to review the segment and adjust it to catch all the hits.

[gautham_madala]

Yes, a ~5% difference in pageviews and clicks between two report suites (global vs. subset) is expected. This can be due to differences in processing rules, bot filtering, tag firing, or visitor ID handling. Even if the homepage URL is the same, discrepancies arise from how each suite collects and processes data. To resolve this, compare suite settings, ensure consistent implementation, and validate data collection using debugger tools.

To investigate the ~5% discrepancy in pageviews and clicks between the global and subset report suites, you can use the following checklist. First, confirm that both suites receive the same tracking calls (s_account) and that the homepage is firing tracking and link tracking (s.tl()) consistently. Then, compare admin settings to ensure bot filtering, internal IP filters, VISTA rules, processing rules, and time zone settings are identical. Check that both suites use the same eVars, props, and events for pageviews and clicks, and that marketing channel configurations match. Use the Adobe Experience Platform Debugger and tools like Charles Proxy or browser dev tools to validate that the same data is being sent. Finally, create a segment in the global suite to match the subset suite’s filtering, and use breakdowns (e.g., by device, region, or referrer) to pinpoint the source of the discrepancy.