Hi @Zam 

Looks

The structure of the data from the Zap trigger is different from the mapped variable, which is why the error happened.

Try mapping this variable.

{{231629672__data__email}}

Thank you @Troy Tessalone but Zapier still failed to capture {{231629672__data__email}}

@Troy Tessalone I forgot to mention in my first post that when performing a test with the mapped data, it does work. But once I tried on live data, Zapier failed to collect the value from the new submission.

@Zam 

Did you try to turn the Zap ON and test live again?

@Troy Tessalone yes i did try to disable and enable, even put up a new zap, but still fails.

@Zam 

For the new Zap Run, post screenshots of the DATA OUT from Step 1 and the DATA IN for Step 2.

 Thanks @Troy Tessalone! {{231629672__data__email}} does works!

Apparently all the mapped data don’t get captured by Zapier properly.

So based on the variable you gave, is this how I should map the following data? Are these variables valid?

{{231629672__data__id}}

{{231629672__data__email}}

{{231629672__data__popupId}}

{{231629672__data__productId}}

{{231629672__data__optinLocations__newsletter_footer}}

{{231629672__data__optinLocations__checkout_checkbox}}

{{231629672__data__optinLocations__list_builder_pro}}

{{231629672__data__optinLocations__custom_page}}

@Zam 

For some Zap app integrations the data structure returned when configuring the Zap steps in EDIT mode can differ from the data structure returned for live Zap Runs.

It can take a bit of trial and error to get the custom pill mappings correct.

When in doubt, test it out.