You know things about your leads that we can't see — who actually booked a call, who became a client, and who showed up to your seminar. When you send that back to us, we can tell the ad platforms which leads were good ones, and they'll go find more people like them. This guide shows you how to send it automatically.

Booking through Calendly? You can skip this entire guide — it's a one-click connection with no Zapier and no JSON. See Connect Calendly (Automatic Booked Calls).

Not technical? You have an easy option. You can upload a spreadsheet instead from My Leads → Import conversions — no setup at all. This guide is for when you'd rather have it happen automatically.

In your portal, go to Account → Webhooks and find Send us your conversion data. Click Create my endpoint. You'll get a web address that looks like this:

That long token on the end is what identifies you, so treat it like a password — don't post it publicly. If it ever leaks, click Rotate and you'll get a new one.

Everything below is just "send some information to that address."

Each thing you tell us about is one small record with two required parts:

The simplest possible message we accept:

The four things you can tell us

Those alternate words in the last column all work — so if your CRM already calls it "Appointment" or "Won", you can usually send it as-is. Capital letters, spaces, and dashes are fine too: "Booked Call", "booked-call", and "booked_call" are all understood.

Optional extras

Sending several at once

You can send up to 1,000 records in one go.

We look up the person by email first, then phone, and only ever inside your account — your data can never touch another firm's. Phone formatting doesn't matter; (883) 952-7547 and +1 883-952-7547 both match.

If we can't find them, we tell you exactly who we couldn't match and nothing is saved for that row. The rest of the batch still goes through — one bad row never breaks the whole thing.

Tip: send the same email address the person used to register for your event. That's what we have on file.

This is the important part, and it's easy. Add ?dry_run=1 to the end of your address:

In dry-run mode we check everything and tell you what would happen — but nothing is saved. Send a few real people through it and read the reply:

Read it like this:

When matched looks right, remove ?dry_run=1 and you're live. You can also see every delivery we've received under Account → Webhooks.

Calendly — one click, no Zapier

If your consultations are booked through Calendly, this is by far the easiest path: you paste one token and we build the connection for you. Nothing on this page — no address, no JSON, no testing — applies to it.

👉 Connect Calendly (Automatic Booked Calls) — the full walkthrough, including the exact permissions your token needs and how to choose which meetings count as a booked call.

⚠️ Calendly needs a paid Calendly plan (Standard or above) for this.

Everything else — use a connector

Most other tools can only send data in their own format, which won't match ours. For those the recipe is: your CRM → a connector (Zapier or Make) → us. The connector is what translates.

Zapier

Turn the Zap on and confirm the reply says matched: 1.

⚠️ Two Zapier gotchas. First, Webhooks by Zapier is a paid feature — it isn't on Zapier's free plan, so you'll need a Professional plan or higher. Second, never leave the Data section empty — if you do, Zapier quietly forwards every field from the previous step and we won't understand any of it.

Make (formerly Integromat)

n8n (for technical teams)

If you already run n8n, use an HTTP Request node: Method POST, your URL, Send Body on, Body Content Type JSON, and Specify Body Using JSON with our format. If you've never heard of n8n, use Zapier or Make instead.

Lots of firms track this in a spreadsheet — especially seminar sign-in sheets. Here's the good part: you don't have to reshape it. Send your sheet the way you already keep it and we'll work out the columns.

Your sheet only needs two things:

The easy way — yes/no columns

This is how most people already track it, and it works as-is:

We read yes · y · true · 1 · x · done · completed as "it happened" — and a date in the cell counts as a yes too. Blank or no means it didn't happen.

One row can say several things. Bob above booked, attended, and converted — that becomes three separate records automatically.

Column names we already understand (capitals, spaces and punctuation don't matter):

Want to date one specific outcome? Add "Date" or "On" to that column's name — Booked Call Date, Converted On. Otherwise a plain Date column applies to the whole row.

If you'd rather be explicit, add an Event column containing booked_call, converted, attended, or rated. An Event column always wins over the yes/no columns.

Google Sheets

Open Extensions → Apps Script, clear the editor, paste this in, put your own address in the first line, then click Run. Google will ask you to authorise it the first time. You don't need to change anything else — it sends each row using your own column headings.

The reply appears in the Execution log at the bottom — check that matched looks right. When you're happy, remove ?dry_run=1 from the address and run it for real. To make it automatic, open Triggers (the clock icon) and schedule it daily.

Excel

Excel can't send data out by itself, so you have two choices:

Here's where to start for the systems advisors use most. In every case you're picking a trigger, then sending it on with a connector.

⚠️ Because neither Wealthbox nor Redtail can notify Zapier directly, Zapier has to check them periodically — so expect a short delay rather than instant delivery. That's fine for conversion tracking; nothing is lost, it just arrives a few minutes later.

Don't see yours? If it connects to Zapier or Make at all, the recipe above will work — and if it can't send data out, the spreadsheet route always will. Send us a message and we'll help you find the right trigger.

Most systems don't have a single button that means "this lead became a client" — it's usually a stage, status, or pipeline change that you defined. So before you build anything, answer this: in my system, what exactly changes when someone becomes a client? Once you know that field and value, pick the trigger that watches it and add a filter for that value. That one decision is 90% of the setup.

Send the same thing twice? No harm — we won't double-count it. That means you can re-send a corrected spreadsheet safely.

Stuck at any point? Use Chat with us in the portal — send us a screenshot of your setup and the reply you got back, and we'll sort it out.