Post live QA of Meta Events Graph

Post live QA of Meta Events Graph

Following steps to be followed
Step1 :- Go to Facebook Business Manager. Select your pixel in which conversions API is implemented.


Step2 : Click on the event and observe Graph.

Note : In Graph,
1. Green line represents events coming from the server.
2. Blue line represents events coming from the browser.
 
Ideal Scenario : Green line should be either equal or slightly higher than blue line.
 
Corner Cases :-
Case 1 : Blue(browser graph) line is much higher than the green line (server graph).
 
Solution 1 :-
Check if the event setup tool is on or not?
If the event setup tool is on then ask the client to turn it off.
Before turning it off, check if they are running any ads on automatic tracked events or not.
You can see defined rules in the Manage Events section.
 
 
Sometimes it is also possible that a pixel is implemented via connected partners like shown in the screenshot.
Solution 2 :-
Check domains on which event is firing.
Ask the client to update the content security policy on different domains. You can update this doc and send this to the client.
Whitelist all domains from server side.
 
Solution 3 :- 
If the event is coming only from one domain then check if pixel base code is present on the page or not.
If Pixel base code is present then ask the client to remove base code bcz it will overriding datahash’s code.
 
Solution 4 :- 
Check all event parameters like content_ids , value, currency in Conversion API request.
Parameters should pass as per below document.
https://developers.facebook.com/docs/meta-pixel/reference 
If parameters are not passed with above format then facebook will discard API’s request and that’s why server graph will remain low.
 
Case 2 : Server Graph is higher than browser graph.
 
Solution 1 :-
It normally happens when there are more than one pixel implemented on the website.
To solve this issue put a filter in the DhPixel file to send the request if only a particular pixel is firing an event.
To solve above case we put a filter in Dhpixel file so that it will fire for a particular pixel only.
 
Solution 2 :-
Check if the pixel is installed and firing correctly or not. Sometimes we get errors in the console like below screenshot.

    • Related Articles

    • Post Live QA of Event Matching

      Step 1 : Go to Event Matching. Step 2 : Follow below steps for event matching. During the audit please make sure that script is making First Party data correctly. Reference : How to check First Party data on a website? For Lower funnel events like ...

    • Facebook Conversion API QA Process

      Document Purpose This document will help to perform QA for Facebook Conversion API.It covers all corner cases and its solution occurs during the QA process. Owner of the Document Yaman Patel (yaman@datahash.com) Maan Patel (maan@datahash.com) Agenda ...

    • Meta CAPI for CRM

      Overview: The Meta Conversion API for CRM is a performance optimization tool designed specifically for lead ads. It enables businesses to send updated lead information back to Meta, allowing for more precise optimization for campaigns that you are ...

    • App CAPI (Conversions API for App) Integration Guide

      Overview: App CAPI enables server-to-server (S2S) event tracking for mobile apps, improving measurement accuracy in privacy-restricted environments like iOS (post-ATT) or Android with limited advertising ID access. It ensures more reliable ...

    • Meta Web Conversions API[Step 3: Set up Meta Conversions API Destination]

      Overview Description: The Facebook Conversions API (CAPI), formerly known as Facebook Server-Side API, is designed to help businesses deliver personalized advertising experiences to customers while maintaining data privacy. This is achieved by ...