Troubleshooting & Problem Resolution Flashcards

Organic search traffic seems to have dropped, but Search Console impressions are stable. Which should you investigate next?

Answer: Tracking or attribution problems such as lost tags or changed referrers

Stable impressions suggest visibility is unchanged, so measurement or attribution is the likely culprit.

Form submissions are tracked as events, but numbers include failed validations. What is the fix?

Answer: Fire the event only on successful submission

Triggering on successful submission prevents counting attempts that did not complete.

Which approach most reliably confirms that a tracking implementation is complete after a release?

Answer: Run a documented QA checklist comparing expected versus actual hits in debug tools

Systematic QA against a tracking plan catches missing or incorrect hits before data is lost.

A sudden drop to zero in all metrics begins at a specific time. What is the first thing to verify?

Answer: Whether the tracking code was removed or broken in a recent deployment

A hard cutoff to zero strongly points to a deployment that removed or broke the tag.

Users report seeing different prices than analytics e-commerce data shows. What is the likely data issue?

Answer: Data layer values are populated before the price is updated or are hardcoded incorrectly

Data layer timing or static values can send outdated or wrong prices to analytics.

Conversion rate appears to improve dramatically after a filter change, with fewer sessions. What should you suspect?

Answer: The filter excluded non-converting traffic, skewing the denominator

Removing sessions that rarely convert artificially inflates the rate without any real improvement.

What is the best way to document a resolved tracking issue for future teams?

Answer: Record the symptoms, root cause, fix and date in a change log or annotation

Annotating the timeline explains data anomalies and helps future analysis and troubleshooting.