It is very much encouraged in their UI to install the 'Meta's Conversion API Gateway'.
Some Seeka users are confusing this with something to do with their Seeka install, and new Seeka users are also arriving with this already turned on.
This has nothing to do with Seeka and is responsible for very low match rates, and being turned on will affect Seeka's ability to send maximum data.
This must be turned off immediately.
How do I check whether the Meta Conversion API Gateway is enabled?
Navigate to Event Manager and then to the overview of your pixel
Click settings and scroll down to the Conversions API section
If you see this as connected, you officially have the gateway installed, and we need to remove it.
How to remove the Meta Conversion API Gateway
In the left panel select 'Integrations'
Then select Conversion API Gateway
Check the Pixel ID of the Pixel connected in Seeka.
Click 'Settings' in the top right corner
Click the blue 'Disconnect' button
Click the checkbox and hit 'Next'
Once you reach the success page, click Finish
Repeat this for any pixels connected to Seeka
What issues arise from having the Meta Conversion API Gateway connected on top of Seeka?
The gateway will throttle Seeka's data flow
Poor signal delivery will show low match rates in the event manager.
Seeka will generally show a 9.3 for Purchase, whereas with the Gateway, you will see a 6-7, which is what you see with a poorly attempted native version of CAPI
Eventbrite and Moshix overcounts prior to Seeka
We have witnessed many cases of new Seeka clients who had previously been using Moshtix or Eventbrite's native CAPI, who ALSO had the Meta Conversion API Gateway plugged, experiencing over-reporting.
This is due to each system failing to deduplicate, which could result in counts up to double the actual ad wins.
Due to the presence of other sources, such as organic traffic, this may often have gone unnoticed.
This is bad for actual performance, as the pixel is being fed duplicates of the limited data those systems are able to track.
How to spot this visually?
In events manager, navigate to the events overview for your pixel
Click on any event and look for a large disparity of server counts higher than browser in the graph or the tool tip.
Subject to the severity of the over-reporting, this can mean that you may view an initial decline in 'reported results' when plugging Seeka in for the first time. Obviously this is due to looking at the correctly deduplicated figures and not false ones.