{"id":4977,"date":"2022-02-16T11:50:50","date_gmt":"2022-02-16T08:50:50","guid":{"rendered":"https:\/\/trackingchef.com\/?p=4977"},"modified":"2022-09-04T17:21:05","modified_gmt":"2022-09-04T14:21:05","slug":"facebook-conversions-api-with-zapier-and-gtm","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/facebook\/facebook-conversions-api-with-zapier-and-gtm\/","title":{"rendered":"Creating a Facebook Conversions API with Zapier and GTM"},"content":{"rendered":"\n
My recent blog post on creating a Facebook Conversions API (aka CAPI) using Pipedream has been quite a success. Released in February, it’s already ranking as our 4th most popular blog post on my blog.<\/p>\n\n\n\n
One of the most frequent questions I get about this post is how come I didn’t choose Integromat or Zapier instead of Pipedream. While I’m a big fan of these two platforms (Integromat slightly more), Pipedream simply offers better pricing for scale. This is very lucrative if you’re switching your entire pixel tracking to server-side (i.e. including Pageviews), which can easily add up to tens of thousands of events.<\/p>\n\n\n\n
At Zapier or Integromat’s pricing, this becomes a major expense. So Pipedream was my go to for this.<\/p>\n\n\n\n
But some advertisers want a simpler solution (though in all fairness I think it’s simple enough), so I figured I’d write up a quick guide for implementing Facebook’s Conversions API using Zapier.<\/p>\n\n\n\n
Important note<\/h2>\n\n\n\n
This guide will help you build a CAPI solution that is utilizing the key concepts of the API but is built as a client-side solution. This means you won\u2019t get the full benefits of the CAPI (mainly overcoming ad blockers) but can expect an increase of 5-10% in the number of events tracked, resulting in larger audiences to target in your campaigns (e.g. more users recorded that added to their carts).<\/p>\n\n\n\n
Facebook even released this case study with \u201cLove your Melon\u201d which showed a 17% increase in attributed revenue<\/strong> after switching to the Conversions API.<\/p>\n\n\n\n
When is Zapier the right choice for you?<\/h2>\n\n\n\n
You’re lazy – No need to be ashamed of it. You have other, more important, stuff to handle so you’re willing to pay the premium<\/li>
You’re tracking only few events – In many cases, advertisers don’t need each and every event tracked using the CAPI solution, making the overall sum events sent smaller<\/li><\/ul>\n\n\n\n
Important note:<\/strong><\/p>
To implement the CAPI solution via Zapier you are required to have a paid Zapier account (as the free account doesn’t have the Webhook app (Premium App)<\/p><\/blockquote>\n\n\n\n
Benefits of using Zapier<\/h2>\n\n\n\n
Simpler set up – no need to extract your Pixel or Token, just click on your ad account and you’re all set<\/li>
No code – While Pipedream uses a ready made code snippet, you still need to make minor changes to it<\/li><\/ol>\n\n\n\n
Step 1 – Create a Zap & Trigger<\/h2>\n\n\n\n
In your Zapier account, create a New Zap. The Zap’s trigger should be set to “Webhooks by Zapier” and the trigger event to “Catch hook”.<\/p>\n\n\n