How to Test SlideRule's Facebook CAPI Integration Against Your Current Facebook Integration

Here we’ll show you how to run a side-by-side, risk-free comparison test between your current Facebook pixel integration and SlideRule Analytics’s Facebook CAPI app.

This test will help you verify whether your current, original implementation method or SlideRule provides you more accurate and reliable data in Facebook for targeting before you make any changes to your Facebook campaigns or ad spend.

For this test, you’ll want to leave your ads connected to your original pixel until the test is complete so you don’t disrupt your current Facebook ads.

First, you leave your original Facebook pixel, however it’s integrated, exactly as is. If you used Shopify’s built-in integration, or another app, don’t change anything in the integration or in Facebook. 

Next, install the SlideRule Analytics Facebook CAPI app if you haven’t already. Then follow our documentation to create a new pixel and add it to the SlideRule app. Name it “SlideRule Analytics Pixel” or something sensible.

Don’t use the new SlideRule Analytics Pixel in any advertisements until after the test.

Wait at least 36 hours to collect enough data to test the results.

Once you have at least one full dayt worth of data, you can test the results. 

Go to your Facebook Event Manager, hover over the left menu and select Data sources.

Select the Original Pixel and select the date range for the test. Make sure you don’t include the day you installed the pixel in SlideRule or it will skew your results.

Look at the total events for purchases.

Open the SlideRule Analytics Pixel in a new tab. Select the same date range as the Original Pixel. 

Look at the total events for purchases.



Now, compare the purchases for each pixel to the actual purchases in Shopify for the same date range and see which one is more accurate. Remember, higher or lower isn’t better. We want more accurate purchases for optimal Facebook targeting.

You can also export the data for each pixel by clicking on the purchase event and selecting Export Data.

You should also take a look at the match rate and see which one is better. Note that it may take some time for the match rate of the new pixel to develop. If you see more accurate purchases but a lower match rate on the SlideRule Analytics Pixel, wait at least 7 total days before comparing.

Also note, match rates can fluctuate so don’t dismiss either pixel based on one day’s match rate.

You may notice some other differences about the SlideRule Pixel as well.

First, you’ll see that SlideRule only sends purchases events from the Conversions API (i.e. server-side) and not from a client-side pixel. The reason why is that if Facebook receives a client-side event and server-side event, it uses the client-side event. If you have upsells, there’s no way to send the revenue correctly client-side. Therefore, we can’t get accurate revenue data into Facebook when firing a client-side pixel.

This also means that, while we can’t see Facebook revenue numbers directly, we know that SlideRule’s revenue must be more accurate.

Second, if you have upsells, you’ll see that we fire an Upsell Purchase event. This event fires in addition to the correct purchase event. You can use this event to retarget or create lookalike audiences for upsell purchasers if you like. It doesn’t affect purchases at all.

Finally, you may see a little graph icon on one of your events. If you hover over it, you’ll see information about how many more conversions there are from sending server-side events than you would get with just a client-side event.

After running your test, you almost certainly see that SlideRule Facebook Conversion API app provides better data than your previous integration. If you don’t, reach out to info@slideruleanalytics.com and we’ll work with you to get you the best data possible at no additional cost.

To use the SlideRule integration to get better targeting with Facebook and see a lift in return on ad spend you need to start using it in your ad sets. To do so, you can: