Meta is rolling out Occasion Protection. This gives extra perception into whether or not you’re following finest practices together with your server and browser occasions.
Right here’s what you have to know…
What It Is
Inside Occasions Supervisor, go to Information Sources. Throughout the Overview display screen, broaden one in all your occasions and click on View Particulars.
You might even see a brand new possibility for Occasion Protection.
It reads:
Your occasion protection contains the full variety of browser and server occasions despatched to Meta. When utilizing each pixel and Conversions API, the full variety of server occasions must be equal to or increased than the full variety of browser occasions.
You could be sending server occasions from the Conversions API to get any significant knowledge right here.
That is fairly easy. Meta needs us to ship as many or extra server occasions than browser occasions for every particular person occasion. Once you do, you’ll meet finest practices.
Assembly Finest Practices
So long as you ship no less than as many server occasions as browser occasions, you’ll get the message that you simply meet finest practices.
Once you don’t, Meta gives some sources to troubleshoot.
Listed here are the troubleshooting steps…
In any other case, Meta gives hyperlinks to the next sources:
Know When It’s a Downside
Within the case that didn’t meet finest practices, the 2 have been extraordinarily shut. It was a excessive quantity of occasions, so the proportion distinction was extraordinarily low. My guess is that it’s a short lived blip (possibly a delay for server occasions) that may appropriate itself since these occasions are despatched the identical method as all of my others.
Like all of those messages from Meta, ensure it really is an issue earlier than doing something.
