Hello @Hayden 

You can check the ZAP task logs to identify if Zapier is sending any additional parameter in Payload and then add the same parameter in your Unbounce field mapping page.

Awesome thanks Max - I’ll check that out now. 

Just adding here that the Unbounce + Webhook explicitly states that it doesn’t “Subscribe” the user to Marketing (marketing consent), but simply adds it to the specified List. See here:

If you have Zapier, another option is to do both the Webhook that adds the user to the List and passes in the Unbounce event “Filled Out Form” (along with all the data) AND you can fire a Zapier Zap that Subscribes the user to a List.  That way you get best of both and you wont’ have any time delays chaining from Unbounce to Zapier to Klaviyo.  

Here’s an example of the data you get from the native Unbounce Webhook to Klaviyo:

You get not only the “Filled Out Form” event, but also the IP, Page Name, Page ID, Page Variant, etc.  These are helpful later when you want to do Segments or Flow Filters based on which Unbounce Page they submitted from.  Granted, you can do this in Zapier as well, but this is easier and built-in!

Thanks @retention - this is very helpful. 

It’s annoying that Unbounce webhooks don’t subscribe users to a list. It would be a easy and clean integration. 

I have already set up the Zaps, it’s just an extra step for each landing page as I create new landing pages on a weekly basis. 

Perhaps Klaviyo can allow us to subscribe users to a list using Unbounce webhooks in the future. 

Anyhow, thanks for the useful tips and advice!