
Facebook CAPI Setup for Server-Side Ad Conversion Tracking
ABOUT
Facebook CAPI Implementation to Future Proof Ad Campaigns for A First Party Data World
Wayside Cross Ministries is a Christian nonprofit that helps men, women & children find hope and transform their lives following addiction, incarceration, and violence. They provide support through restoration, recovery and transitional housing programs.
Supported by private donations from individuals and partner churches as well as their thrift shop sales, Wayside runs multiple ad campaigns, currently on Facebook, to drive monetary & thrift donations.
They had installed Facebook pixels on their website to track conversions, including ad link clicks (page views), intent to donate, and donations made. They had three primary concerns:
- Facebook pixels were not firing appropriately, thereby undercounting the conversions that were happening through their Facebook ad campaigns. This was likely affecting the success of the campaigns as Facebook was unable to accurately identify all profiles of donors, interested donors, and their lookalike audiences, leading to under-optimized targeting & retargeting.
- They also had pixels integrated through their Google Tag Manager, which had not been updated in a while.
- Finally, in light of the current move toward a more privacy-centric solution, Facebook Pixel is to be replaced by a more robust and privacy-centric Facebook Conversion API (CAPI). Wayside Cross wanted Facebook CAPI enabled and optimized thereby making their ad campaign tracking future proofed.
Google Tag Manager Setup
Conducted Google Tag Manager audits & resolved bottlenecks that were impacting Facebook conversion.
Tagging Server Setup on GCP
Set up a tagging server on Google Cloud Platform (GCP), configured it for optimal performance and configured the server as a subdomain to allow for first-party data environment.
Facebook CAPI Enablement
Configured Facebook CAPI, along with tags, triggers and variables to allow or tracking of relevant events on the website through Facebook CAPI.


Facebook CAPI Implementation for First-party Data Environment
We worked to audit & resolve bottlenecks that were impacting Facebook pixel conversion tracking to ensure all donation events were being tracked accurately. We also enabled best data variables to be tracked for improved Facebook ad performance. Finally, we implemented Facebook CAPI to ensure there is no data events disruption when pixel is finally deprecated.
PHASE I
Enabled Client Side Google Tag Manager Setup
We enabled data flows from 3rd party iframe donor site to parent site for donor event tracking purposes. We next allowed for UTM parameters propagation when moving to different pages during site navigation. We finally set up GTM to track these events using pixels and moved to settting up of server side GTM for CAPI implementation.
PHASE II
Configured Tagging Server on GCP
We next configured a first-party environment for the tagging server on Google Cloud Platform that would allow us to set up Facebook Conversion API data flows to future proof Wayside Cross against third-party cookie restrictions and Intelligent Tracking Prevention (ITP) environments.
PHASE III
Facebook Conversion API (CAPI) Setup
We finally set up tags, triggers and variable for Facebook CAPI to track relevant events on the website. We then made sure CAPI stream met the quality criteria for the events with minimum score of 5. We removed all reference to the pixels once Facebook CAPI was setup.
HORIZONTAL CAPABILITIES
Marketing Analytics
Server Side Google Tag Manager
Facebook CAPI