Ernie Civic | | Facebook & Instagram | 1 comments
How to Resolve the Aggregated Event Measurement Issue in the Facebook Pixel
3 min to read ✭ In this post, we'll cover the aggregated event management issue in the Facebook pixel and how it can be resolved.
Facebook Aggregated Event Measurement
What’s going on with the aggregated event measurement issue in the Facebook Pixel? Currently, we have seen a few nonprofits that are experiencing an issue. When we go to set up aggregated events, which is important for the new iOS update, we are met with an error that says, “No web event to select in this pixel.” What this means is that the Aggregate Event Tool is not identifying any events when that pixel fires.
We reached out to Facebook and they did not have an explanation for this, so we did some investigating ourselves. This is happening because waterisbasic.org is a verified domain, and they’re using Network for Good for their donations. They are using either the free version of Network for Good or the basic version. With that version, they don’t have the ability to make this a subdomain. Facebook is recognizing this as a new domain. In other words, waterisbasic.org is verified, but waterisbasic.com is not. We are reaching out to the Network for Good team to see if they are willing to add the meta-tag on or find out what it takes for us to get that in there.
The same thing is happening for another organization. When you go into the account, you are not able to add the event. We created a standard custom conversion event and a Facebook standard event and both of those fired, but the purchase event and the view content are not firing. This is occurring because they are using classy.org in their domain instead of their own domain. Their donation page is not a domain of skidrow.org, which is why the event is not pooling and we aren’t able to run the aggregate events set-up tool at all. To get this fixed, the Classy client needs to upgrade their membership to the paid version. It seems like they are using the free version of Classy, and it does not give them the ability to add the subdomain.
Let’s take a look at All Hands and Hearts. They have a paid version, and you can see the difference in the URL – give.allhandsandhearts.org. Allhandsandhearts.org is a verified domain and all sub-domains along with it will function. For the client mentioned above, that is not the case. There is no skidrow.org, but there’s a classy.org and that is what’s causing our issue right now. When we set up this event, it’s not picking up that purchase pixel, and it’s letting us know that classy.org is not verified.
Even if you are able to add this event and the pixel pools, only the actual event that is added to the website will fire, but the unverified one will not. To sum it all up, if you are experiencing this, it means either the client is using a free version of Classy or they’re using another donation platform, like Network for Good. They could also be using a membership or a donation platform that doesn’t allow subdomain features.