Routing QA Guide

# Routing QA Guide

Do not infer routing success from incomplete evidence.

## Page checks

Confirm the page or form URL and current accessibility. A page load does not prove routing.

## CTA checks

Confirm CTA text and destination. Shopper-facing CTAs must route to pricerightrv.com.

## UTM checks

Confirm source, medium, campaign, content, and term fields if used. Do not include private data.

## Endpoint checks

Confirm endpoint URL, method, and reachability only when approved. Do not execute private webhooks without approval.

## Visible field checks

Confirm user-facing required fields.

## Hidden field checks

Confirm route keys, source fields, and UTM capture fields when evidence is available.

## Destination checks

Confirm sheet, CRM, platform, or webhook destination from downstream evidence.

## Alert checks

Confirm chat, email, SMS, or webhook alert behavior from logs or received alert evidence.

## Fix Now, Test Next, Monitor Later classification

- Fix Now: high or critical suspected impact with evidence of failure.
- Test Next: incomplete evidence with meaningful routing risk.
- Monitor Later: low risk or no current evidence of failure.

## Status language

Use not_checked, partially_checked, pass, warn, fail, unverified, blocked_missing_evidence, awaiting_downstream_confirmation, downstream_confirmed, or resolved_confirmed.

Last updated: 2026-06-11T10:47:53Z