Hi @TheBishopAG 

Good question.

Help article: https://help.zapier.com/hc/en-us/articles/8496055479181-How-to-set-up-your-Google-Ads-New-Lead-Form-Entry-trigger#prerequisites-0-0

Make sure to test your GAds Lead Form, then pull thru the example in the Zap trigger: https://help.zapier.com/hc/en-us/articles/8496310366093

Appreciate the assistance Troy, but my issue is that I can’t get the Lead Form to push its’ fields to the Zap.

I can’t see the option to add the multiple-choice questions in the Google Lead Form, into ANY of the Zap fields.

Eg: Question: What is your monthly budget? > Zap fields don’t see this question (or others)

@TheBishopAG 

Did you test the Lead Form?

Did you then pull thru the test you submitted that had the custom questions answered in the trigger step?

https://developers.google.com/google-ads/webhook/docs/testing

@Troy Tessalone, I am experiencing the same issue as mentioned above. I have set up a lead form in GoogleAds, but the value for Quality Questions is not picked up by Zapier.

The test is only available for a direct webhook, not if the connection is made through a connected account.

Hi there @Sem Huray and @TheBishopAG,

I did some digging into this, and if you're finding that the sample data from Google Ads isn't aligning with the actual data from your Google Ads app, you might want to consider using a custom pill mapping workaround.

Don't worry if you're unsure how to do this - we have a comprehensive guide that walks you through the process. You can find it right here: 

Hopefully, this points you to the right direction! 

Using a custom pill would help to get the data from the received form data into the action data, but as the data from the Quality Questions field is not picked up from the Trigger Test, there is no way to scrape the “name of the field” from the Lead form entry.

I have asked ChatGPT for an answer, it said the custom question would be the “name of the field”, but it is not in the lead form entry data.

Hi @Sem Huray,

If that’s the case, I suggest skipping the testing phase of the Zap by clicking on the "Skip test" buttons. Once you've done that, go ahead and publish the Zap. To ensure everything is working as expected, trigger the Zap with a test run. Afterward, take a look at the Zap History and see if the "Quality Questions" data shows up there. If it does, then you can proceed with the custom pill mapping workaround.

Please give that a try, and keep us posted! 

I am having the same issue as above. The qualifying questions do not show up in the ZAP History

Same problem here. It’s a bug. I have done multiple tests and the DATA read by zap is the {{name of field}} and not the value; it’s not mapped well. and it’s from zappier side. Google send the good data and informations in the Data in, and the data out is really out 

Need zappier to confirm the bug. I need a fix on it.

For informations of what happens in the ZAP history :

In the Data out of the Google trigger :
 

Google_question ?: Answer

and in the DATA IN of the Zoho part:

picklist::My_field: {{Google_question}}

what is expected in the DATA IN is :

picklist::My_field: Answer

it’s a bug, all the other informations in the DATA OUT of Google trigger are ok in the DATA IN of Zoho part, but not the google qualified question.

Hope it helps. need a fix.

I’m having an issue with this too. There’s no option for inserting the qualifying answers into the Zapier email we receive.

Hi friends,

I suggest contacting our Support Team regarding this issue so they can take a closer look at the Zap and its log and provide a solution since they have the correct tools for that, and my access is limited here.

You can reach our Support Team here: https://zapier.com/app/get-help

I appreciate your patience and understanding.

WHAT THE HECK ZAPIER SORT IT OUT THIS IS BASIC FUNCTIONALITY...BRING IN ALL THE DATA POINTS INCLUDING THE QUALIFYING QUESTIONS. JEEEZ IT ISNT THAT HARD. #HALFBAKED

Hi @TheBishopAG, @Sem Huray, @Tim2, @DeGoZap, @Bruffell and @HYPER 

I’ve been looking into this and found that there’s a feature request to have custom fields supported. This would help to give access to the missing information from the lead form so I’ve gone ahead and added everyone’s votes to that feature request. I can’t make any sort of promises around when or if that feature request will be implemented by, but we’ll be sure to email you all once it is.

In the meantime, I wonder if it might be possible to subscribe to use Google Ad’s API Request (Beta) action to search for the lead form submission and obtain the missing information from it that way? It’s a bit more advanced as requires referencing Google’s API documentation but we’ve got a more general guide that may help to get you started: Set up an API request action

Thanks for everyone’s continued patience on this. If you give that workaround a try and run into any trouble please do let us know - happy to assist further! 

Adding my voice to this. Same problem. Really need this done asap. @SamB can you please add my vote to that feature request?

Please add me my vote to the feature request. Actively deploying 10+ GoogleAd Forms and was not aware of this limitation. Thank you.

Thanks for reaching out here @VPTAG Marketing and @Austin_B2B!

There’s no updates on the feature request at the moment. But you’ve both been added to the list so we’ll definitely be in touch by email once it’s implemented. Hopefully the workaround I suggested previously of using an API Request action will help to get your Zaps up and running in the meantime. 

Hey folks, 

Just circling back in here to share that the feature request has been implemented! 

In order to access the custom fields with the New Lead Form Entry trigger you’ll need to ensure your Zap is running the latest version of the Google Ads app - see: Update to the latest app version in Zaps. Then load in a new test record from Google Ads with the desired custom fields. 
 

We hope you’re able to start using those custom fields in your Zaps soon! And as ever, if you run into any issues with them let us know in the Community or contact our Support Team directly and we’ll be happy to assist. 

In the meantime, happy Zapping!