Why speed matters here
A lead form submission is the highest-intent moment you will ever get from a paid ad, and it decays fast. The broker who calls in five minutes has a conversation; the one who downloads a spreadsheet on Friday leaves a voicemail for someone who has already spoken to two other people. The gap is almost never effort — it's that the lead sits in the ad platform instead of the CRM.
BrokerDam closes the gap with an inbound webhook. Every account gets one, secured with its own secret. Anything that can POST JSON to a URL can push leads into your account, and they arrive on your Leads page in seconds — not on the next export.
Three steps to set it up
- 1
Copy your webhook
In BrokerDam, open your lead capture settings and copy the inbound webhook URL and its secret. Every account has one, generated for you — there's nothing to provision.
- 2
Wire up the ad platform
In Make or Zapier, create a scenario with a Facebook Lead Ads or Google Ads lead form trigger, then add an HTTP / webhook action that POSTs the lead to your BrokerDam URL with the secret attached. Map name, email, phone and any custom questions to the matching fields.
- 3
Submit a test lead
Use the ad platform's test lead tool and watch it appear on your Leads page. Once you see it land with the right source and campaign, turn the scenario on and leave it running.
What arrives, and how it's tagged
Leads land on the Leads page as real records — name, email, phone and whatever custom questions your form asked — tagged with their source and campaign. That tagging is what makes the spend answerable later: when a deal funds, you can trace it back past the CRM to the campaign that produced it, instead of guessing which channel is carrying the month.
From there a lead is an ordinary BrokerDam contact. Text them from the same thread that lives on their file, add them to a campaign, convert them to a deal when the conversation gets real. Nothing about a webhook lead is a second-class record.
Security and rotation
The endpoint is authenticated by a secret held server-side in your account. Requests without it are rejected. If you suspect the value has been shared beyond where it should be — a contractor's Zapier account, an old scenario you no longer control — rotate it. The previous secret stops working immediately and you paste the new one wherever it's needed.
A note on consent
Leads arriving through the webhook carry no marketing consent record. An ad platform lead form is an enquiry, not an opt-in to a campaign list, and BrokerDam won't pretend otherwise by flagging these contacts as consented. Deciding when you have the consent or implied consent to market to someone under CASL stays your responsibility — as does honoring unsubscribes, which BrokerDam applies across every channel once recorded. This is general information, not legal advice.
Frequently asked questions
- Do I need Zapier or Make?
- No — any tool that can POST JSON to a URL works. Make and Zapier are the easiest route because they already have Facebook Lead Ads and Google Ads lead form triggers built in, so you don't write any code. If you'd rather post from your own website form, your ad platform's native webhook, or a script you already run, point it at the same endpoint with the same secret and it works identically.
- What happens if my webhook secret leaks?
- Rotate it. The secret lives in your BrokerDam settings and can be regenerated at any time — the old value stops working immediately, and you paste the new one into Make, Zapier or whatever is posting to the endpoint. Requests without a valid secret are rejected, so a leaked URL on its own can't inject leads into your account.
Point your ads at BrokerDam
Start a 14-day trial, copy your webhook, and watch the next lead arrive while the ad is still running. Step-by-step instructions live in the ad lead capture tutorial.
Start your 14-day trialCard required · Cancel anytime.