how do i integrate leads form with sell.do crm
i want to integrate leads form with my crm software ? how do i create a webhooks and key for sell.do platform
The short answer is:
Lead Forms with Sell.Do? The primary way to integrate Google Ads lead forms with Sell.Do is by using the native webhook feature built into Google Ads lead form assets, which sends lead data directly to an API endpoint you set up within Sell.Do.
You need to log in to Sell.Do, access the “Lead Integrations” or “API Based Integrations” section, and generate an API key and the correct POST URL (webhook URL) which Sell.Do is configured to receive.
This URL and key are then pasted directly into the lead delivery section of your Google Ads lead form asset.
For a more robust and advanced solution that also allows you to send offline conversion events (like a Standard Event for a confirmed Sale) from Sell.Do back to Google Ads, you should use the Google Ads API combined with Google Tag Manager Server Container and a hosting service like Stape.
The long answer is:
Your plan to use webhooks is exactly the right approach for real-time lead ingestion from a platform like Google Ads into a CRM like Sell.Do
Webhooks are simply a method for one application (Google Ads) to automatically notify another application (Sell.Do) when an event occurs, which in this case is a lead form submission.
To create the webhook URL and key for Sell.Do, you first need to log into your Sell.Do administrative dashboard.
Based on how CRMs like Sell.Do are structured, you will typically find the necessary settings under sections like “Marketing Automation,” “Lead Integrations,” “API Based Integrations,” or “Developer Settings.”
Sell.Do has a specific process for setting up API Integrations, where you would choose an API type (sometimes called a “Pusher” like “Youtube Pusher” or a generic “Lead Pusher”) and the system will generate a unique URL structure for you that looks something like https://app.sell.do/api/leads/YourUniquePusherNameHere/create.json.
The system will also prompt you to generate or assign a corresponding key, which serves as a security token to authenticate the incoming lead.
Once you have this precise Webhook URL (which includes your API key) and the Key (the security token, which might be a Secondary Key or a simple secret provided by Sell.Do), you then go into your Google Ads account.
You edit the specific lead form asset you are running and expand the “Export leads from Google Ads” section, then “Other data integration options.”
Here, you will paste the Webhook URL and the Key into the respective fields.
Crucially, Google Ads gives you the option to “Send Test Data.”
You must click this to confirm that Sell.Do receives the dummy lead data correctly and can process it, which is the final confirmation of a successful webhook integration.
The part you mentioned about using the Google Ads API, Google Tag Manager (GTM), and a server host like Stape or Google Cloud Platform (GCP) is an excellent, cheap, and future-proof solution that goes far beyond just lead capture.
While the direct webhook integration handles the incoming lead, this combined server-side architecture handles the crucial outgoing data flow, also known as offline conversions.
After a lead lands in Sell.Do, it progresses through stages like Qualified, Site Visit, and finally, Sale or Purchase
The value of the lead for Google Ads isn’t just the initial submission, but the final, high-value Standard Event that occurs days or weeks later.
You can’t send this critical, delayed information back to Google Ads directly via the simple webhook.
This is where the Google Ads API comes in.
You can configure GTM Server Container, hosted cheaply by a service like Stape, to act as a secure intermediary.
When a lead’s status changes to something like a Booking or Sale in Sell.Do, Sell.Do can trigger a simple server-to-server webhook to your GTM Server Container.
The GTM container then processes that lead’s data and uses a Google Ads API tag to send an Offline Conversion event back to Google Ads.
This process is highly accurate, privacy-compliant, and significantly improves the optimization of your campaigns because the Google Ads bidding algorithm is now optimizing based on real, high-value, confirmed sales that happened in your CRM, not just initial submissions.
Using a service like Stape makes setting up this server-side infrastructure accessible and cost-effective, effectively turning a complex developer task into a streamlined configuration process.
About The Author
