Skip to Content
Torque Lift Docs

Troubleshooting

What to do when the setup command stops, a setup code fails, AWS refuses the stack, or events aren't arriving.

Start with what the command printed. It says which check failed, and it never prints your setup code.

Setup

Events aren't arriving

Check these in order. The Data page in your console shows whether events are arriving and what was turned away.

  1. The tracking pull request is merged and deployed. Events can't arrive from a branch that isn't live.
  2. The environment variables are set in production. NEXT_PUBLIC_TORQUELIFT_WRITE_KEY and NEXT_PUBLIC_TORQUELIFT_JITSU_HOST (VITE_ instead of NEXT_PUBLIC_ in a Vite, Remix or React Router app). If either is missing, the wrapper logs [torque] analytics is off in the browser console and sends nothing. See Code in your repo.
  3. Your app has recorded consent. Nothing is sent until setAnalyticsConsent(true) runs or TorqueLiftAnalytics gets consent. See Recording consent.
  4. You aren't testing from a browser a script is driving. The wrapper sends nothing when navigator.webdriver is set.
  5. The variables were set before the build. The build tool inlines NEXT_PUBLIC_ and VITE_ names when it builds, so a variable added after a deploy needs a new build. The wrapper also sends only from a production build.

Events arrive, but some are turned away

A call that can't be kept at all goes to the quarantine table with a reason, and never the call itself. Among the reasons: not valid JSON, an unknown call type, no received time, and no user or anonymous ID left after filtering. Read them on the Data page, or from the API with List turned-away calls.

A call that is kept can still lose parts of itself. A property your plan doesn't declare is dropped or set aside, and a value shaped like an email, a phone number or a card number is removed, even from an allowed property. Each row records how many values were removed and the names of undeclared properties, never the values. See Data ownership and privacy and Event tables.

To track something new, add it to the plan in a pull request.

Still stuck?

Write to us with the command's full output.

On this page