Tracking
Track ads through to the customer who paid
ReadyLift counts outcomes in the order a customer reaches them, from the first visit to the first payment. Each outcome has one source, and each event is tied back to the ad and the page version that started it.

Outcomes, in order
Visit, sign-up started, trial started, activated, paid and, for a store, order placed. Each one shows its source, its 30-day count and when it last arrived. An outcome with no source says so and offers to connect one.
Where outcomes come from
| Source | Who sends | Best when |
|---|---|---|
| Page tag | Built in, on every ReadyLift page | Always on |
| Stripe or Shopify | ReadyLift reads from it | Billing is in Stripe, or selling is in Shopify |
| MCP server | ReadyLift reads from it on a schedule | Your product or CRM already has an MCP server |
| Events API | Your server sends to ReadyLift | An outcome should count the second it happens |
| Webhook | Another tool sends to ReadyLift | A billing, sign-in or booking tool can already send webhooks |

A Visit ID ties it together
The page tag creates a Visit ID when someone lands and passes it to the sign-up. Any event that carries the Visit ID can be tied to the ad and the page version behind it.
An event log you can check
Every event is marked Counted, Not from an ad, Duplicate ignored or Rejected, with the reason. An event with no Visit ID is still stored, and kept out of ad results.

Personal data is dropped
A source only needs an account ID and a Visit ID. Names, emails, document text and card details are dropped before anything is stored.
Nothing counts by accident
A source counts nothing until you turn it on at the end of setup, and a test event never counts. Sources are paused or disconnected, never deleted, so past results keep their origin.
Works with
See what your ads are really buying
ReadyLift.ai is opening to a first group of SaaS and AI companies. Tell us where you advertise and we will be in touch.