Turn a recurring support issue into a troubleshooting article
Help readers recover by recognizing the first point of failure.
Collect symptoms without private details
Record the error shown, where it occurs, and what successful behavior looks like. Use a recreated example where possible. A generic statement that the tool does not work does not identify a useful branch.
Order checks by evidence and cost
Start with easy observations such as whether the page loads or an input is missing. Then show when to inspect redirects or event definitions. Explain what each check rules out.
State when the reader should escalate
Include the details they can provide safely, such as time, browser, and an example with fictional inputs. Avoid requesting account credentials or sensitive form values.
Try a related tool
Find the share of eligible visits that completed a defined action. Count at most one conversion per visit for this calculation.
