That's a frustrating but common issue.
It sounds like you're correctly using Google's call reporting to track conversions, but getting that data out and into Jobber is the sticking point.
The reason the standard Zapier integration for Google Ads isn't working for your phone leads is because those conversions are tracked server-side by Google when the call happens, and they aren't generated from a simple web form submission that Zapier can easily "watch."
The data you need lives in Google Ads, but it's not a standard webhook trigger.
The best way to automate this requires a slightly more advanced setup that involves several services working together to bridge the gap.
The most robust and future-proof approach would be to use a combination of the Google Ads API, Jobber's API, the Google Analytics Data API, Google Tag Manager, and a service to manage the server-side flow, like Stape or a custom solution on Google Cloud Platform.
Here's why this combination is a good solution for you.
First, the Google Ads API is the only way to reliably extract the specific details of a recorded phone call conversion.
It allows you to query the conversion data, including the recorded phone number and the call duration, which are essential for creating the Jobber "Request."
Second, Jobber's API is necessary to programmatically create the "Request."
The connection between the two would be handled by a service like Stape or Google Cloud Platform, which can execute a script or a cloud function.
This script would poll the Google Ads API for new phone conversions, extract the caller's phone number, and then use Jobber's API to push that phone number and maybe a note about the call duration and time into a new "Request."
Third, while not strictly required for the phone number, the Google Analytics Data API and Google Tag Manager are critical for a fully refined system.
If you were sending the call data to Google Analytics (GA4) using server-side tagging in GTM and Stape, you could enrich the lead data with more customer journey details (like the original ad or keyword).
Even without that step, you would still use GTM to handle your normal web events, and for calls that start on your website, you can use a click-to-call event and a custom phone_call event in GA4.
The goal, however, for your recorded Google Ads leads, is to use the Google Ads API to pull the data out and Jobber's API to push it in.
Finally, a service like Stape or Google Cloud Platform acts as the middleman.
They are the execution environment for the code that connects the APIs.
Zapier is great for simple connections, but it can't handle the multi-step, logic-based API polling and data manipulation required for this specific task.
Using a custom solution allows you to look up the phone_call_conversion Standard Event data in Google Ads and map it perfectly to the required fields in Jobber, ensuring your missed calls are converted to service requests automatically.
