Pipedrive, Close or any CRM without an ad integration: the webhook pattern that works for all of them

If your CRM doesn't have a built-in connection to Meta or Google Ads, or the one it has is too limited, you're in the largest group of all. And here's the good news: the fix is the same for every CRM. Once you understand it, Pipedrive, Close, Zoho, Freshsales, Airtable, your own database: they're all one pattern.

Every CRM can do three things: store a person, move a deal through stages, and trigger an automation when a stage changes. That's all you need.

The pattern, step by step.

Step one: store the click ID on the person when they arrive. Add custom fields for the click IDs (gclid, fbclid, ttclid, li_fat_id), and make your web form write to them. This is the step that decides match quality, so do it first.

Step two: choose the stages that matter. Most pipelines have eight or ten stages, and a platform doesn't need eight or ten signals. Pick three or four that separate buyers from form fillers: qualified, meeting held, won, and perhaps paid.

Step three: trigger a webhook when a person or deal reaches one of those stages. Most CRMs have this built in, or you can use Zapier, Make or n8n as the trigger. The request carries the event name, the person's email or phone, the value, an order ID, and the stored click IDs.

Step four: receive it, match it and send it. The receiver finds the ad click, hashes the identity, and sends the stage to the ad platforms.

Step five: watch the log. When something fails, you want to see it the same day.

A made-up mapping for a generic CRM. Stage "Qualified" maps to a lead event. "Demo held" maps to a scheduled event. "Won" maps to a purchase event with the deal value. "Lost" and "Stalled" are not sent.

Why does a webhook beat a native integration for many teams? Because it's yours. When you rename a stage, you change the mapping in one place. When you add a platform, you add it at the receiving end, not in every CRM flow. And it doesn't depend on a vendor deciding to support your CRM.

The trade-offs, honestly. It needs a little setup, and somebody has to own the automation. There's no one-click app. And if the CRM's field names change, the webhook needs updating. That's the price of flexibility.

To show how the stage design works, here's a made-up exercise for three kinds of CRM.

A sales CRM with a ten-stage pipeline: keep three. Qualified, meeting held, won. Ignore the other seven.

A service business CRM with statuses like new, contacted, quoted, booked, completed, paid: keep booked, completed, paid.

A simple deal board with only open, won, lost: send won. It's a thin signal, but it's honest, and it's a start.

The exercise is to write down, for each stage you send, one sentence saying what it means and who marks it. If you can't write that sentence, the stage isn't ready to be a signal. Ambiguous stages make noisy conversions.

Which CRM are you on, and which stages would you send?