What impact do your configuration changes have on our Facebook account?
As a first step, we send events with custom names that don't impact anything in your Facebook account for validation before you switch from your previous CAPI solution to ours. Our solution starts improving EMQ for the standard events after you switch over from your previous CAPI solution.
What do you need the Facebook Access Token for?
The Facebook Access Token allows integration with Black Crow AI's Smart ID for Facebook. It enables Black Crow AI to send events and information to your Facebook account when users on your site view products, add to their carts, start checkouts, add payment info, make a purchase, etc.
What should I do if I see a diagnostic warning/error in Facebook Events Manager that says to "Update to IPv6" for any of my events?
No action is required and these warnings can be ignored. EMQ and ad performance will still improve compared to your previous solution.
In the Meta Platform, how can I detect that Smart ID CAPI is functioning?
There is no direct way to trace Black Crow CAPI in Meta. However, server events can only be processed through a CAPI solution. So, if Shopify CAPI is turned OFF, Black Crow CAPI is ON, and server events are still being processed, our CAPI is functioning properly.
What are EMQ scores?
Event Match Quality scores are Facebook’s way of understanding the quality of data you’re sending, that they can match back to their ID graph. The higher the score the better. You’ll have larger retargeting audiences, more accurate in-platform attribution, but above all else – a more accurate bidding algorithm.
More information can be found here.
Why is the “Purchase_BlackCrow” event displaying lower or equivalent EMQ scores compared to the “Purchase” event?
After initially setting up our _BlackCrow events, it takes time for Facebook to assess EMQs accurately. As more data is processed, EMQ scores will improve.
Additionally, optional user data, such as a phone number, may not be submitted consistently, which could lower EMQ scores.
What is the timeframe for seeing improved EMQ scores?
Typically you'll see the Event Match Quality scores increase about 24 hours after we launch and have disabled your existing CAPI solution.
After launching the Black Crow CAPI, why is the EMQ score for the “Purchase” event still the same or lower?
Traffic spend on Facebook significantly impacts EMQs. Higher EMQs may result from an increase in users with a Facebook click ID, and vice versa. A change in Facebook spend can positively or negatively affect EMQs.
What is the purpose of the "_BlackCrow" events?
The _BlackCrow events serve as a crucial measuring tool for assessing the success of our CAPI solution before it launches. These events ensure minimal fluctuation in the total event count when transitioning to our Black Crow CAPI. Additionally, they help us predict the expected EMQ lift once our CAPI goes live.
Are the "_BlackCrow" events feeding into my current CAPI solution?
The _BlackCrow events operate independently from your active CAPI and won't impact your campaign or ad set metrics. Please don't use them for campaigns or ad sets.
Can we delete the "_BlackCrow" events?
The Events Manager view only allows permanent deletion of events by discontinuing their transmission. By pausing the sending of our _BlackCrow events, they will be removed from the Events Manager scope after 28 days, thus no longer appearing on your pixel.
The "_BlackCrow" events are displaying a "No recent activity" message or the event is no longer received in Events Manager
Upon activating our CAPI, we send the 'standard' events to the Meta Pixel. Additionally, we cease sending the corresponding "_BlackCrow" events since their testing purpose has been fulfilled and sending is no longer necessary.
Why are there fewer "_BlackCrow" test events than the current Meta CAPI standard events?
Our "_BlackCrow" test events are only sent server-side. The Meta CAPI sends both browser and server-side events. Therefore, the Events Manager will show a lower event count for our test events.
When we launch our BCAI CAPI, we send both browser and server-side standard events