Facebook Pixel & Conversion API for leads with Deduplication
Client Background:
Jude has two Gravity form on her website, One is for those who are interested to fill out an enquiry form to know more about their services , and another is a Booking form for Booked their Service.
This Detailed case Study is a part of, Fix Google Tag Manager & Set up Server Side Tracking & Meta Conversion API.
In This Case study, We will explore How I Configured Pixel & CAPI
My Role:
I helped to implement Meta pixel & Conversion API with Event Deduplication. Also configured advanced matching parameters by sending additional customer data to enhance ad performance and optimize return on ad spend.
Challenges:
Clients Using Gravity form but the Forms Input field information was not showing on Data Layer, I tried the Popular Listener code to get User input but Failed.
Solution:
Thanks to JavaScript, I use a little bit of it to get the Accurate Expected Data.
I use Google Tag Manager to manage the Conversion Tags /Scripts from a single interface.
I create a lot of variables to get accurate data from the Data layer. Also Created some Tags and triggers in Google Tag Manager.
Configured Cloud Server(Client purchase Stape.io as as Cloud Server )
Configured GTM Server Container
Deploy Meta Pixel Tags In GTM web Container
Created Variables to get User Input from different Gravity Forms
Meta pixel Tag Contains Advance Matching Parameters for booking_submission Event
Meta pixel Tag Contains Advance Matching Parameters for enquiry Event
Configured Booking Form Tag for Server Event with Advance Matching Parameters
Configured Booking Form Tag for Server Event with Advance Matching Parameters
Configured Conversion API Tag in GTM Server Container
After Testing Everything in GTM Web & Server Container in built preview mode, Published the both container and made it live.
Around a week later i check the Event match Quality.
