Hello,
I have integrated the Stape CAPIG and I’m seeing inconsistent information.
The Problem: In the Stape CAPIG, I’m seeing PageViews being reported, but 0 Lead events.
In Events Manager I’m seeing PageViews and Lead events being reported, with Integrations Multiple (Sent via browser and conversions API)
I’m pretty sure I’m seeing duplicate events on the FB side, but my main issue right now is trying to figure out why the Browser is sending Lead events, but my CAPIG isn’t.
The Setup
The pixel is installed on two websites, one is the current brand, and one is the old brand that we are transitioning away from. We’ll call the old website HG and the new website IM.
On HG the base pixel was installed in the child theme header file, and is working great. The fbq(‘track’, ‘Lead’); tag is installed via GTM and fires with the trigger “PageView Contains congratulations”.
On IG the base pixel is installed via GTM and fbq(‘track’, ‘Lead’); is also installed via GTM, firing with the trigger “PageView contains thank-you”.
On both websites, the Lead event has been firing as expected, before we integrated with Stape CAPIG.
I connected the pixel to the CAPIG using the Authentication method, and immediately it began to report PageView events, but not Lead events.
In the Pixel settings I can see it’s connected to the CAPIG
And in the CAPIG I can see that it’s connected to the Pixel.
I tried adding a Tag Firing Priority of 100 to the Base Pixel tag to ensure it’s firing first, but that didn’t change any of the results.
In short, everything fires in GTM as expected. We were receiving reliable data from both websites before integrating the Pixel with CAPIG, and now I’m getting inconsistent information. All of my testing shows that everything is setup as it should be, and there are no custom features or functionality built in or on top.
Has anybody ran into this before?

