Hi @stellapuivoon,

Thanks for sharing this question with us.

Since we do not have a direct integration with Google forms, you could explore a 3rd party like Zapier to link Google forms with Klaviyo. Alternatively, once you have collected that information via Google forms, you can import it into Klaviyo via a .csv file. Although this would involve a manual step. We typically recommend either using a default Klaviyo form, you could also build a custom form or use one of the aforementioned native integrations like Typeform. In terms of cost, using a Klaviyo form would likely be your best option because it’s cost is included in our product.

I hope that’s helpful.  

Isn't there a way to do this with custom metrics?

The initial suggestions about using Zapier or manually uploading a CSV are valid, but if you're looking for a robust, automated, and ultimately more scalable solution that uses Google Forms, the best approach involves a combination of the Google Forms API, the Klaviyo API, Google Tag Manager (GTM), and a server-side solution like Stape or Google Cloud Platform (GCP).

While this method requires more technical setup than Zapier or a manual upload, it offers the most control and reliability for real-time synchronization.

The core challenge is that a Google Form submission doesn't automatically send a server-side signal that can be directly consumed by Klaviyo.

You can bridge this gap by using a Google Forms script that fires when a new response is submitted.

This script can be programmed to call your own server-side endpoint, hosted on a service like GCP or Stape, which then receives the form data.

The server-side component is crucial because it allows you to securely process the data and, most importantly, call the Klaviyo API.

Specifically, you would use the Klaviyo API's functionality to either create a new profile or, more commonly, update an existing profile with the answers from the form as custom properties.

For example, if your form asks about a customer's favorite product category, the server would map that answer to a custom property like Favorite_Category on the Klaviyo profile.

You could also use the server to trigger a Klaviyo track event, such as a custom Survey_Completed event, which is vital for starting flows or segmentation.

This is a much cleaner way to handle the data than trying to send it directly from the client side via GTM.

GTM's role, in this specific setup, is less about capturing the form submission itself, as that happens server-side, but more about ensuring the customer is correctly identified with a Klaviyo profile.

Before a user fills out the form, GTM can be used to set a Klaviyo cookie and potentially fire a Klaviyo Active_on_Site event to ensure the profile is ready.

If you were using a custom-built form on your site, GTM would be central to collecting the data, but for an embedded Google Form, the server-to-server connection using the APIs is the most reliable method for passing the form data itself.

Stape or Google Cloud Platform can act as the intermediary server, accepting the payload from the Google Forms script and then executing the necessary call to the Klaviyo API.

This entire API-driven architecture ensures that the data is synced immediately and server-side, which is the most secure and reliable method for updating customer profiles and triggering Klaviyo events like Profile_Updated or custom Survey_Data_Added events, bypassing the limitations of a direct client-side script or the rate limits and complexity of an off-the-shelf connector like Zapier for very high volumes.