Torque Lift

See that your events arrive, and arrive clean

Torque Lift writes the tracking as a pull request. Then Torque Lift shows whether events are arriving, what was turned away, and the paths people take.

Data
Torque Lift console, the Data page: events in the last 24 hours, the planned events firing this week, calls turned away, and how long a call takes to become queryable.

Is data arriving, on time and clean? What came in, and what was turned away.

  • Tracking is a pull request

    Torque Lift writes a tracking plan and the code for it, in your repo. Your CI runs on it, Torque Lift's guards check it for personal data, and a person on your team merges it.

  • Health at a glance

    Events in the last day, how fast they become queryable, which planned events are firing, and what was turned away and why.

  • Where people go and drop off

    Paths through a session, and the funnels people leave along the way, so you can see where they stall.

Next: growth analytics

This site's own tracking arrived as a pull request

Torque Lift added tracking to this site, and does the same for yours. Here is what happened, in order.

  1. A plan comes first

    Torque Lift proposed two events, CTA Clicked and Waitlist Joined, with where each fires and what it carries. A person approved the plan before the pull request merged.

  2. Then the code, in your repo's own files

    14 files changed, and 92 lines counted toward the 400-line limit; generated files and lockfiles don't. Events send from the browser only after a visitor accepts the cookie banner.

  3. Checks run before anyone reads it

    This site's CI ran the typecheck, tests and build. Torque Lift's guards checked that no personal data goes out and that every changed file was in scope.

  4. A person decides

    The pull request listed what to set in production before merging, and how to verify after: accept the banner, click through the tour, join the waitlist. A person merged it. Torque Lift never does.

torque-site · Pull request #14Real · this site

Torque Lift: tour and waitlist tracking

Merged torque-lift[bot] opened it; a person merged it into main on Oct 27

components/WaitlistForm.tsx
+import { track } from "@/lib/analytics";
const id = useId();
+useEffect(() => {
+ if (state.status === "joined")
+ track("Waitlist Joined", { form: variant });
+}, [state.status, variant]);
  • This site's CI: typecheck, tests, build
  • Torque Lift guards: no personal data, files in scope, 92 of 400 lines
  • Tracking plan v1: 2 events, approved before merge

This site runs on Torque Lift. Its tracking came from this pull request.

Get early access

We're starting with a small group of early partner teams. We set Torque Lift up with you, and you get weekly readouts and a direct line to the team. Leave your work email and we'll be in touch.

Privacy

Can we measure how you use this page?

A random ID in your browser, never your name or email. Nothing is tracked unless you accept. Privacy