Google Ads Lead Forms and Meta Lead Ads: Called in 30 Seconds

What is the actual gap in a typical lead form ad setup?

A lead form on Google Ads or Meta captures a name, phone number and a couple of qualifying fields, then hands it off. What happens next is entirely down to the business: an email notification, a spreadsheet row, or a CRM entry that sits until someone checks it. The ad platform has no idea whether that lead ever got called, let alone whether it turned into anything. That gap, between the form submission and a phone actually ringing, is where most lead-ad spend gets wasted.

How does a Google Ads lead form webhook connect into MAJ Leads?

Google Ads supports pushing lead form submissions to a business's own system via a webhook integration, rather than relying only on the lead being downloaded manually or emailed. MAJ Leads generates a per-client webhook URL and key in the console, which is entered as that client's webhook endpoint in Google Ads. When a lead submits the form, Google posts the submission to that endpoint, MAJ Leads verifies it using the client's key, and creates the lead record with the fields Google Ads sends: gcl_id, campaign id, and the lead id itself.

How do Meta Lead Ads leads reach MAJ Leads?

Meta's Lead Ads flow works differently: a business subscribes its Facebook or Instagram page to lead webhooks through the client's own Business Manager, and a per-client page access token authorises MAJ Leads to retrieve the lead data as it comes in. A single mapping ties each connected page id to the correct client workspace, so leads from a brokerage's Facebook page land in that brokerage's queue, not anyone else's.

How is a lead deduplicated, and what attribution is kept?

Every lead, regardless of source, is deduplicated on its phone number in E.164 format for that client, so the same person submitting a Google form and later a Meta form does not create two separate leads and two separate calling cadences. Alongside the lead itself, MAJ Leads writes a single attribution record capturing the source, campaign, ad set or ad group, the specific ad, the lead form id, gclid or fbclid where present, any UTM parameters, the landing URL, and the timestamp of first touch. This is what makes it possible to answer "which ad actually produced a booked lead," not just "which ad produced a form fill."

First touch matters specifically because the same person often interacts with more than one ad before ever submitting a form, clicking a Meta ad on a Tuesday, then converting through a Google search ad on a Friday. Recording the timestamp of first touch alongside the attribution that actually produced the submitted lead keeps that history intact rather than silently overwriting it every time the same phone number reappears.

What happens after the lead lands?

The lead enters the same cadence covered in Speed to Lead in the UAE: The Thirty-Second Standard: a first call attempt targeted inside thirty seconds, inside the 09:00 to 18:00 GST calling window, run either by AI Mode or surfaced to a rep's due-now queue in Team Mode. A lead that arrives outside the window still gets an immediate WhatsApp acknowledgement, with the first call attempt starting once the window opens. Nothing about the ad source changes this: a Google Ads lead and a Meta lead ad lead run through the exact same cadence and the same outcome tracking.

How does the outcome get reported back to Google Ads?

Once a lead reaches a terminal outcome, qualified or booked, MAJ Leads reports it back to Google Ads using Enhanced Conversions for Leads. Two conversion actions are configured per client, Qualified Lead and Booked, and each upload matches on the hashed phone number or email, together with the original gclid when it was captured on intake. This is what lets Google Ads' own bidding actually optimise toward a booked outcome, rather than treating every form submission as equally valuable.

How does the outcome get reported back to Meta?

The same principle applies on Meta, through the Conversions API, sent per client to that client's own dataset. A qualified outcome is sent as a Lead event and a booking as a Schedule event, each carrying hashed phone and email in user_data, the original fbc parameter derived from the stored fbclid where present, the original lead id for Lead Ads leads, and an action_source of phone_call, reflecting how the outcome was actually reached.

Both uploads run on a short cycle rather than once a day, so the feedback reaches each platform's bidding system while the campaign is still live, with retries and a dead-letter path for anything that fails to send rather than silently dropping it.

How is this actually tested before it goes live on a client's account?

Neither integration goes live on a real campaign untested. Google's side is verified against a Google test account before it is pointed at a client's live conversion actions, and Meta's side is verified using Meta's own test_event_code mechanism, which lets an event be sent and inspected in Meta's Events Manager without it counting as real campaign data. Only once both sides show the expected event arriving correctly does the integration switch over to the client's live ad accounts.

Why does this matter for a business running Google or Meta lead ads?

A campaign that only ever reports "form submitted" back to the platform has no way of learning which audiences, placements or creatives actually produce a customer, only which ones produce a click. Feeding a real outcome, called, qualified, booked, back into each platform's own optimisation loop is what turns a lead-generation campaign into something that can genuinely get more efficient over time, rather than staying flat at whatever cost-per-lead the initial targeting happened to land on.

This is also the piece that is easiest to skip when a business first sets up lead ads and hardest to retrofit later, once months of campaign data have already been optimised against form fills instead of real outcomes. Wiring up the webhook and the closed-loop reporting at the same time a campaign launches means the platform starts learning the right signal from day one, rather than a business having to unlearn months of the wrong one.

Does this only apply to Google and Meta lead ads?

No. The same underlying lead record and cadence handle leads from a website form, extended to capture gclid, fbclid and UTM parameters where a visitor arrived through a paid link before converting on-site, and from a CSV import for a list a business already has. Google Ads lead forms and Meta Lead Ads are simply the two sources where the closed-loop reporting back to the ad platform itself is possible, because they are the two channels that can receive a conversion event in return.

See the full mechanics on the lead management system page and compare running this with a human team on Team Mode. Pricing, Team Mode starts from AED 299 per month, is on the pricing page.