Lead sources — one campaign per source, and why that matters
Every lead source gets its own campaign card carrying its webhook, its field mapping, its routing and its AI settings. Merging two sources into one campaign is the mistake that costs you the ability to tell them apart.
Who this is for
Admins and whoever buys or generates leads.
One card per source
Each campaign holds the webhook URL you give that source, the fields it sends, where its leads route, whether the AI works them, and how they perform. Open one to see all of it in a single place.
Capture a test lead before you go live
Send one real submission through the webhook before you point spend at it. That captures the actual field names the source sends, so you can map them properly rather than guessing — and it proves the pipe works end to end while it's still cheap to find out that it doesn't.
Don't merge sources
It's tempting to run two vendors through one campaign because the leads look the same. Don't. Once merged you can't compare cost per booked appointment between them, you can't turn one off without the other, and if their opt-in language differs you've now got one AI opening for two different consent stories.
Separate campaigns cost nothing and are the only way ROI per source means anything.
How to check it worked
- Submit a test lead through the webhook and confirm the fields land where you mapped them.
- Confirm it routed to the right rep and got the right product.
- Read the first AI message it triggers — it should match what that source's form promised.
Common mistakes
- Running several vendors through one campaign, then having no way to tell which is working.
- Going live without a test lead, so field mapping is guesswork.
- Copying a campaign and forgetting to change the product intent.
Related
Where this lives in the app
This is documentation for Virtual Closer. Book a walkthrough or sign in.