Troubleshooting & Problem Resolution Flashcards

A new consent banner is launched and total sessions fall 30% overnight. What should you conclude first?

Answer: Tracking is limited to consenting users, so the drop is a measurement change not necessarily a traffic loss

Consent mode or blocking until consent reduces measured users without any change in real traffic.

Page load timing events show unrealistic values like negative or very large numbers. What is the best first check?

Answer: Verify how the timing is calculated and that it is sent after the page load completes

Timing errors usually come from incorrect calculations or events fired before the needed timestamps exist.

Internal staff visits inflate conversion rates. What is the most robust way to exclude them?

Answer: Filter by IP address or internal-traffic parameter and apply a data filter

Defining internal traffic by IP and filtering it keeps reports clean automatically.

Single-page application route changes never register as pageviews. What is needed?

Answer: Send virtual pageviews on history/route change events

SPAs do not reload, so pageviews must be triggered by route changes.

Event counts differ between two reports that use different scopes of the same dimension. What is the probable explanation?

Answer: Scope mismatch between session-level and event-level dimensions

Combining dimensions and metrics of different scopes produces differing or unexpected totals.

Tag fires on the staging site and pollutes production data. What is the best prevention?

Answer: Use separate properties or environments and hostname filters

Separate environments or hostname filtering keep non-production hits out of live reporting.

A report's session count is lower than expected after midnight shifts. Which setting could cause misaligned daily data?

Answer: Incorrect property time zone

A wrong time zone shifts hits into different days and misaligns comparisons with other systems.