SHOPLINE currently supports two ways to report Facebook data and complete conversion API reporting
They are:
1. Facebook Business Extension (FBE)
2. Manually enter the Facebook pixel and access token
In terms of experience, we recommend completing the connection through the Facebook Business Extension (FBE), which is easy to operate. However, if your advertising account is opened by an agency and you do not have full control (see attached image), you can manually create it through event tracking.
So for the common problems of Facebook data reporting, we have sorted out 4 common problems, click to view the corresponding answers directly~
How do I know if my store has been successfully configured and reported to CAPI?
How can I view the comparison report data?
How can I further view the data details?
Is it possible that the data will not be missed as long as the conversion API is configured?
attached drawing
1. How do I know whether my store has been successfully configured and reported to CAPI?
For the above two functions, you need to complete the settings to start reporting.
If you want to know the status of reporting and supplementary reporting, you can check it through the tools provided by Facebook.
2. How to check the comparison report data?
Admin panel entry:
1. Go to the Facebook Business Suite backend -> click on the event management tool -> find the pixel code configured for this store.
2. Click on a pixel to see all data reports received by this pixel by default.
① Here is the time period when the event data was received. When comparing, there are two caveats for time periods:
- time period must match
- Time zone correspondence: The time zone of the Facebook ad account (see the attached photo) and the store's time zone are set to different time zones, and the data will not be aligned
② The association method represents which channel is currently reported through. In the figure, the browser and the server are displayed at the same time, which means that the pixel reporting and the server reporting are configured at the same time.
③ Refers to the number of valid reported events that Facebook finally identified
④ Refers to the reported event type. Facebook limits reporting of up to 8 event types
3. How to further view the data details?
1. Click the event type you want to view, click to expand, you can see the overall trend
2. Click View Details to see further details
3. Illustration description, taking shopping as an example, we see that pixel pixel and conversion API have data, which represents the respective reception conditions of the two channels
| Number of events received | The number of things received by Facebook's two channels, the total |
| Number of events processed | Number of events identified by Facebook, total |
| Number of deduplicated events |
Number of events dropped by Facebook, total. Generally, duplicate events, events that Facebook cannot attribute are discarded. In the above picture |
4. Will the data be missed as long as the conversion API is configured?
- The conversion api can effectively supplement the missed reports caused by browser plug-ins in the browser environment.
- But it cannot solve the problem reported by iOS users. Since iOS 14, especially iOS 14.6, when users check Do Not Track, even if we have reported events to Facebook server, Facebook cannot match the event data with valid users, so Facebook generally discards these events. This is the current status quo, and we are actively communicating with Facebook to find a solution.
- According to relevant data feedback, only about 20% of users will enable tracking, and for these users, it is possible to match and identify the data reported by us.
Example:
- Store A has 100 orders, of which 50 are generated by iOS 14+ system;
- About 80% of users turn off ad tracking;
The reported data will probably be in
50+50X0.2=60;
Missed 40 orders;
The difference is about 40%;
Attachment:
1. Full control
2. Check Facebook Time Zone
Comments