Outcome source
Read outcomes from an MCP server you already run
If your product or CRM already has an MCP server, ReadyLift connects to it as a client and reads the outcomes you choose. Your server never has to know about ReadyLift.

Three steps
- Connect
- Give the server address and sign in. OAuth is recommended, so you approve access on your own sign-in page and ReadyLift never sees a password.
- Map to outcomes
- Pick a tool, pick the outcome its rows mean, and say which fields hold the Visit ID, the account and the time.
- Test and turn on
- Check a read before anything counts.
Reads, never writes
- ReadyLift calls only the tools you tick. Nothing else on the server is touched.
- Tools that change data stay locked.
- Each read asks only for what changed since the last one.
- The sign-in stays in your workspace. Disconnect to revoke it.
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.
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.