Connect your ad campaigns
Pull leads from Facebook, Instagram, LinkedIn and Google ad campaigns straight into your Kuvi Lead Inbox, no code, about five minutes.
Running lead ads on Facebook, Instagram, LinkedIn or Google? Kuvi can capture every lead the moment it comes in, so nobody has to download CSVs or copy details by hand. This guide mirrors the in-app wizard. Open Leads → Sources → Connect a source and Kuvi walks you through the same steps with pictures.
How it works
Ad platforms don't post leads to just any address, so a small, free automation connector sits in the middle and forwards each new lead to your private Kuvi web address:
Your ad form → a connector (Pabbly / Make / Zapier) → your Kuvi Lead Inbox
The connector holds your Facebook / LinkedIn login, so Kuvi never sees your ad account password. Google Ads is even simpler: it can post to Kuvi directly, with no connector.
You don't have to match up field names. Kuvi auto-detects the person's name, email, phone, company and message from whatever the connector sends.
Facebook, Instagram & LinkedIn
- In Kuvi, open Leads → Sources → Connect a source and pick your channel. Give it a name (e.g. Facebook · Diwali offer) and Kuvi generates a private URL for it.
- Create a free account with a connector. We recommend Pabbly Connect for Indian teams (one-time pricing); Make and Zapier also work.
- In the connector, start a new workflow. For the Trigger, choose "New Lead in Facebook Lead Ads" (or Instagram / LinkedIn Lead Gen Forms) and connect your Page. The connector handles the login.
- Add an Action → "Webhooks → POST". Paste your Kuvi URL as the destination and set the format to JSON. Leave the fields unmapped. Kuvi figures them out.
- Send a test lead from the connector: when it lands in your inbox, the source goes Live. (The in-Kuvi Test the connection button only checks the wiring; it never adds a lead to your inbox.)
Every future lead now flows in automatically, tagged with its channel so your Sales & pipeline report shows exactly which campaign converts.
Google Ads (direct, no connector)
- In Kuvi, connect a Google Ads source and copy its URL.
- In Google Ads → Assets, open your Lead form asset, then "Data integration" → "Webhook integration".
- Paste the Kuvi URL as the Webhook URL. Google asks for a Key. Type any word (Kuvi doesn't need it) and Save.
- Click "Send test data" in Google Ads to send a real test lead and confirm you are Live. (The in-Kuvi Test the connection button only checks the wiring; it never adds a lead.)
Is it connected? Reading the status
Every source in the Sources panel shows a status that it earns from real activity, so "connected" always means something. It is never just "I created it".
- Waiting for first lead. The source is set up, but Kuvi has not received anything through it yet. Finish the steps in your connector, then send one lead from it. The status turns Live the moment a lead lands.
- Check mapping. Kuvi received a request from your connector, but there was no readable name, email or phone in it. This usually means the connector is sending a status ping, or the wrong step, instead of the person's details. In your connector's webhook action, make sure it posts the lead's own fields as JSON, and that the trigger is the new lead itself.
- Live. A real lead has come through. You are connected, and every future lead flows in automatically.
- Paused. You switched the source off from the toggle. Turn it back on to resume capturing.
Leave the Sources panel open while you send a test from your connector. The status refreshes on its own and flips to Live within a few seconds of the first lead arriving, so you get instant confirmation.
"I set it up, but nothing shows"
If your source is stuck on Waiting or Check mapping after you have configured the connector:
- Check mapping status. If it says Check mapping, Kuvi is hearing from your connector, so the wiring is right. The fix is the field mapping: the payload had no name, email or phone. Point the connector's trigger at the lead, and send the person's fields.
- Still Waiting. Nothing has reached Kuvi at all. Recheck that you pasted the exact Endpoint URL from this source (not a different one), that the action is a POST in JSON, and that the connector workflow is turned on.
- Prove Kuvi's side. In the connect wizard's last step, tap Test the connection. If it shows Endpoint verified, Kuvi is working perfectly and the gap is inside the connector's setup. This check never adds a lead to your inbox.
- Rotate if unsure. If you think the URL leaked or was pasted wrong, use Rotate token to get a fresh URL, and update it in the connector.
Tips
- One source per campaign keeps your source-performance report clean, for example a separate source for each offer or audience.
- Turn a source off anytime from the Sources panel to pause capture without losing its history; rotate the token if a URL was shared by mistake.
- Leads arrive as New in the inbox. From there, qualify, convert to a deal, or drop. See Navigating Kuvi.