I can’t speak to Zapier, but this is definitely doable with Make. Make has over 1,600 prebuilt connectors for Google Ads Conversions, Klaviyo, Shopify and many more.
Make exposes more endpoints than other integration solutions on almost all connectors, and works out more cost-effective for most workloads.
If you’ve already integrated Shopify and Klaviyo and that’s working well, then you shouldn’t need to add Make (or Zapier) into that mix.
If you’ve got any specific questions about Make, feel free to DM me!
It sounds like you're trying to set up a powerful conversion tracking system, and it's understandable that the coding part is a hurdle!
You definitely don't need to be a developer to get this working.
The main challenge with tracking email subscriptions as conversions on Google Ads is that the subscription event happens on your site (often handled by Klaviyo's form or the embedded form) and you need a reliable, server-side way to communicate that conversion back to Google Ads, along with the user data Google needs for things like Enhanced Conversions.
Integrating Klaviyo, Shopify, and Google Ads without custom code on your site is tricky, but doable.
While Zapier could work as a simple bridge, it can become expensive and might not be the most reliable or fast method for sending conversion data, and it generally won't handle the specific data requirements for Google's Enhanced Conversions feature as cleanly as a dedicated tracking setup.
If you've already synchronized your lists and segments directly from Klaviyo to Google Ads, you should not need to re-import them through Zapier; that synchronizing step is typically for audience targeting, not for sending real-time conversion events.
The best approach for managing these integrations is to centralize your event tracking, which is why a server-side solution is often recommended.
A very robust and increasingly standard approach is using the Google Ads API combined with the Klaviyo API, managed through Google Tag Manager (GTM) and a server-side environment like Stape or Google Cloud Platform.
The Klaviyo API can be used to capture the subscription event details, including the user's email, the moment it happens.
Then, the Google Ads API is the mechanism for sending a conversion event directly from your server environment back to Google Ads.
GTM, specifically its Server Container, acts as the central hub.
When a user subscribes, a signal is sent from your website (the Web Container) or directly from Klaviyo via a webhook to your GTM Server Container.
The GTM Server Container then processes this signal, formats the data correctly (especially the email for Enhanced Conversions), and uses its integration capabilities to call the Google Ads API and send the conversion using the dedicated conversion action you've set up, potentially using the Standard Events Purchase or Lead (or a custom one like Sign Up) depending on how you categorize the subscription.
Services like Stape offer a user-friendly, managed server environment that eliminates the need for you to set up and maintain a Google Cloud Platform instance, making the whole server-side tracking process much more accessible for non-coders.
This method is superior because it's more accurate, less prone to being blocked by browsers, and directly supports the secure, server-to-server data exchange Google Ads prefers for high-quality tracking.
