Outcome source

Send outcomes from your server the second they happen

The Events API is for outcomes only your product knows about, such as a trial starting or an account becoming active. Your server sends each one to ReadyLift as it happens.

Three cards for adding a source: MCP server, Events API and Webhook, each with a diagram of who sends
Sample data.

Three steps

Create a key
One key per source, shown once, with rotate.
Send events
One call carries an event name, the Visit ID, an account ID, a time and an optional amount. Outcomes are mapped by event name.
Test and turn on
The setup waits for your first real event, or sends a test one from the screen.

Best when

You want each outcome counted the second it happens and you have a developer for about ten lines of code.

The same rules for every source

  • Every event needs a Visit ID to be tied to an ad. The page tag creates it.
  • An event with no Visit ID is stored and shown as Not from an ad.
  • The same event arriving twice is counted once.
  • An event that cannot be read is shown as Rejected, with the reason.
  • Names, emails, document text and card details are dropped before anything is stored.
  • Nothing counts until the source is turned on. A test never counts.

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.

Request early access