Everflow has added the ability to fire server-side Facebook events in addition to standard Everflow events. Server-side events use Facebook’s Conversions API. Their system works well for someone who is doing their own marketing - that is, someone who generates 100% of the traffic going to a particular domain. However, it does not work at all for a shared network like GiddyUp.
This is because of the way that Facebook is responding to Apple’s new Privacy restrictions. Facebook has decided to severely limit the number of Facebook pixels/events that can fire in a top-level domain. A maximum of 8 pixel/event pairs can be fired, and the owner of the domain gets to determine what they are and what their priority is. To make things even harder, if a customer has opted out of tracking for the Facebook app on iOS then only 1 pixel/event will be fired for them.
Server-side events are also required to follow these restrictions. If a Facebook campaign fires pixels/events that are not on the list, Facebook will suspend that campaign.
Everflow’s system does not change any of these rules. So for a Network like GiddyUp, we simply can’t have all our Marketing Partners running Facebook traffic on our standard offer domains. It will result in chaos, with many Marketing Partners getting their campaigns shut down.