Documentation & Best Practices Flashcards

What is the recommended approach for UTM parameter documentation across teams?

Answer: Maintain a shared naming guide with approved values and lowercase usage

A shared guide prevents fragmented source/medium values in reports.

Which item belongs in a tracking plan (tracking specification)?

Answer: Event name, trigger, parameters, and owner

A tracking plan lists events with triggers, parameters, and responsibility.

Why annotate dashboards or reports with key events such as campaign launches or site releases?

Answer: To give context for changes in trends

Annotations help readers connect trend changes to known events.

What should QA documentation for a new tracking implementation include?

Answer: Test cases, expected results, and validation outcomes

Test cases and results prove tracking works as specified.

Which is a best practice for KPI documentation?

Answer: Define formula, data source, owner, and reporting frequency

Complete KPI definitions prevent ambiguity and ownership gaps.

When maintaining separate views or properties for testing, what should be documented?

Answer: Which view is raw, filtered, or test and the filters applied

Documenting view purposes and filters avoids using the wrong data.

What is the benefit of keeping an unfiltered raw data view or backup?

Answer: It preserves unaltered data in case filters or settings cause errors

A raw view lets you recover from misconfigured filters.