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

1. Step by step Facebook conversion API QA process.

1. QA of Facebook event’s graph

2. QA of Event Matching section

3. QA of Event Deduplication section
   

4. How can clients share their query with us?
   

Step by step Facebook conversion API QA process.

Go to Facebook Business Manager.Select your pixel in which conversions API is implemented.

Repeat following steps for all the events of facebook pixel which has conversion API implemented.

QA of facebook event’s graph

         Step1 : 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.

QA of Event Matching section

Step 1: Go to Event Matching.

Step 2 : Follow below steps for event matching.

1. During the audit please make sure that script is making First Party data correctly.

Reference : How to check First Party data on a website?

2. For Lower funnel events like Purchase First Party data should look like below.

3. For upper funnel events like PageView initially First Party data will be low volume.It will increase as the user base will increase on the website.

QA of Event Deduplication Section

Step 1 : Go to Event Deduplication.

Step 2 : Make sure scores are matching ideal scenarios.If not find ideal scenarios from below conditions.

Ideal Scenarios :-

1)Server’s rate of event deduplication  should be more than 60-70%.

Note : It is okay if the browser's rate of event deduplication is 10-15%.But, it should not be more than 10-15%.

2)Pixel and conversion API should receive eventID and FBP more than 60-70%.

Note : If not all then one of the keys (EventID/ExternalID/FBP) should be more than 60-70%.

3)Overlap of Pixel and Conversion API’s eventID should be more than 60-70%.

Note: At least for one of the dedupe key overlaps should be more than 60%.

Corner Cases:-

Case 1:-

Rate of event deduplication of server events is very low.

Dedupe keys are not coming from the Pixel or Conversion API side.

Overlap of Dedupe keys is very low.

Solution :-

1. Make sure that one of the dedupe keys (eventID/FBP/ExternalID) is passing from both pixel and conversion API.

2. Event ID passing from pixel should be same as Event Id passing from server.

Reference :- https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events 

https://www.facebook.com/business/help/823677331451951?id=1205376682832142  

How can clients share their query with us?

If any of the above scenarios are not giving results please make a separate document in below format & send it us @ support@datahash.com

Event Name : Purchase

Graph : Share event’s graph.

Domains : Share domains of events.

URLs : Attach exported file in mail.