Troubleshooting

Troubleshooting hub

SDK, event, goal, variant, flicker, SPA route, ad blocker, billing and reporting issues.

Last updated: May 22, 20268-14 minBeginner to intermediate
Start free See pricingMethodology

What does this do?

Troubleshooting hub helps make the troubleshooting workflow decision-ready in Testvoy. The goal is not only finding a setting, but understanding why it exists, how to read the outcome and where to debug first.

Know when to use it

Learn which UI fields matter

Know what success looks like

Troubleshooting hub screen flow
SetupQAReport
This placeholder can be replaced with a real product screenshot later.

When should you use it?

Use this guide during first setup, experiment creation, report interpretation or before sharing with a client or team. Testvoy keeps the workflow approachable for non-technical users while still exposing SDK, event and security context for developers.

  1. 01

    Choose the relevant workspace and project

  2. 02

    Follow the checklist on this page

  3. 03

    Verify with preview or verifier

  4. 04

    Share the setting or report with the team

How to do it

Most Testvoy workflows follow the same pattern: choose context, define the rule or change, then verify through QA and reporting. This keeps the product focused on decision quality, not only running tests.

  • Is the workspace correct?
  • Is the project key or domain correct?
  • Does the goal/event match?
  • Were mobile and desktop checked?
  • Any bot/SRM or dropped event warning?

Example troubleshooting record

Do not debug by guessing. Record the symptom, page URL, expected result, actual result, console error, project key status and the last accepted/dropped event time together. Sending support this context speeds up resolution.

  • URL and environment
  • Project key
  • Expected event/goal name
  • Console error screenshot
  • Last accepted event time
  • Dropped event reason
  • Ad blocker/consent state
Example information to send support
Project: storefront-production
URL: https://example.com/pricing
Issue: signup_completed goal does not fire
Expected event: signup_completed
Last accepted event: 2026-05-22 14:10
Console: no SDK error
Note: GTM preview shows tag fired

Practical scenario

A growth team changes CTA copy on the pricing page, connects signup_started and signup_completed goals, then reads Google Ads and returning visitor segments separately. If the result is promising, they share a report link with the client or leadership.

Common mistakes

Most mistakes come from wrong project keys, overly broad selectors, missing goals, staging/prod mixups, early decisions on small samples or skipping mobile QA.

Naming an experiment 'test'

Launching without a goal

Deciding on total CVR only

Sending screenshots instead of shareable reports

Related pages

TroubleshootingSDK not loading

Check script URL, project key, CSP, network, ad blocker and consent causes.

Frequently asked questions

Who is Troubleshooting hub for?

Marketing, growth, product and developer teams can use the same guide at different depths.

Do I need a developer?

Not for basic visual changes and report reading; SDK, custom events, custom JS or enterprise security benefit from technical support.

How do I know it worked?

Verifier, recent events, preview, QA checklist and report warnings show setup and experiment health.

What is the common mistake?

Wrong project keys, missing goals, fragile selectors, early decisions on small samples and skipped mobile QA are common.

Docs

Try this guide in the app

Finish setup, create your first experiment and read the report with cleaner data in Testvoy.

Start free Docs