Facebook lead form radio buttons not being detected
Hi everyone,
we’re having an issue with one of our Facebook Lead Ads forms — the radio button options are not being detected correctly.
The data actually appears to be there (as you can see in the screenshots attached), but right after that an error (!) icon shows up, and the selected option doesn’t get registered in the lead.
Text fields seem to work fine, so the issue appears to affect only the multiple-choice / radio-button fields.
Has anyone else experienced something similar or found a fix for this?
Thanks in advance for any help or insight!
Page 1 / 1
Hi @s.d.u.
Looks like the mapped variable is invalid.
End of the mapped variable label says: Dell
But the full field label is: Delludito
Thanks @Troy Tessalone for your reply! The variable is actually mapped automatically — I don’t handle it manually, it’s managed by Zapier.
Is it possible that Zapier is having an issue with escaping apostrophes, since the text in question is: "hai già fatto un controllo dell'udito?"
@s.d.u.
You can and should manually map the variable.
Delete the mapped variable, then in the field click the [+] button to map a variable.
As you can see in the screenshot, I’ve already added all the mapped fields from Zapier, but none of them are being recognized.
From the video, I don’t see any option to write a custom variable manually — it only shows how to insert variables through Zapier’s field mapping.
Hey there @s.d.u. 👋
This is a strange one. I just tested in a Zap and the selected field names stayed the same, they didn’t get changed:
When you say it’s “managed by Zapier” do you mean that you used Copilot to map the fields for you?
If Copilot did map them for you, then it could be that something went wrong and it used the wrong field name. As the accents and apostrophes are missing from the fields shown in your latest screenshot, it could well be that those are what’s causing some trouble here. 🤔
Can you try selecting a new test record to see if that then allows you to select the correctly named fields? You might need to use the Facebook Lead Ads Testing tool to submit a new test lead.
Keep us posted on how it goes!
Hi @SamB,
no, I didn’t use Copilot — I mapped the fields exactly as I always do, and just like you showed in the animated example.
The problem is that this specific field isn’t being recognized at all. I’m starting to think the issue might be caused by the apostrophe in the word “dell'udito”, which could be breaking the mapping.
@s.d.u.
Copy and paste the invalid mapped variable value into a comment for us to see.
The workaround I can think of involves using the raw JSON output from Facebook and using a Code step to parse that JSON to create your own named variables with values to then map to the API request action step.
TIP: Try asking ChatGPT for help with the custom CODE to parse the JSON and create named variables while also including logic to remove special characters in the key label for the key/value pairs.
Thanks for clarifying that @s.d.u.! That definitely shouldn’t be happening. I’d recommend reaching out to our Support team so they can investigate this further. I think you’re right, it does seem like there’s potentially a bug with fields that include apostrophes.
In the meantime, do give that Code step Troy suggested a try and let us know how it goes!
Hi @SamB, Yes, I think the bug is actually caused by the apostrophes. At the moment I can’t test it myself since I don’t manage the social campaigns directly, but the alternative could be to use a typographic apostrophe (’) instead of the straight one (').
So basically writing “dell’udito” instead of “dell'udito” — that might work since it’s not a character that requires escaping.
That’s a great idea @s.d.u.! Definitely check with whoever manages those Facebook lead forms to see if they can try updating the apostrophe as you suggested, and then submit a test lead on the form. Hopefully that’ll allow you to then select the form field in the Zap without any issues. 🤞
