Support Center

Using the Facebook Pixel and the Conversions API

The combination of Conversions API with other Facebook Business Tools allows learning more about how customers connect with the company. To help maximize the effectiveness of the website events, use the Conversions API in addition to the Facebook Pixel.

Website events sent through the Conversions API are related to Facebook Pixel and behave in the same manner that events delivered through the Pixel do:

  • They’re both used for the same forms of ad optimization, such as conversion and value optimization.
  • They can be found in a lot of the same places, such as Ads Manager and Events Manager.
  • They abide by our Off-Facebook activity tool, third-party data ad personalization control, and other Facebook Business Tools Terms limits.

Benefits of the Conversions API

The Conversions API creates a connection between an advertiser’s marketing data and the Meta systems! Here are the main benifits of this:

  • Reduce the cost per action as a result of improved connectivity: Browser loading difficulties, network challenges, and ad blockers have less of an impact on data from the Conversions API than on the Pixel. When using Conversions API in conjunction with Pixel, it establishes a more secure connection, which aids the delivery system in lowering the cost per action.
  • Optimize ads for actions that happen later in the customer’s journey: Actions that occur after a purchase (such as subscriptions), actions that occur in stores, and even customer scores are examples of these occurrences. This data allows Facebook to target adverts to customers who are more likely to be profitable and valuable to the company.
  • Improve measurement: From discovery through conversion, the Conversions API can help better measure ad performance and attribution across a customer’s whole journey. This allows us to better comprehend how digital advertising influences both online and offline outcomes.
  • Reduce the cost per action as a result of increased event matching: When the marketing data can be linked to accounts on Facebook apps and services, it’s most successful. The Conversions API can be used to incorporate additional customer information factors that will help enhance the number of matched events and the quality of your event match.
  • Increase data control: The Conversions API, when used apart from the pixel, allows more flexibility over what is shared and when it’s shared.

Adblock explained

Apple’s iOS 14.5 update forces developers to give users an option to opt out of every tracking in their applications. This is something that affects every single business that relies on Facebook Ads to reach their audience, as now target audiences with iOS devices are going to be harder and more expensive to reach if users don’t opt-in to Facebook Tracking. This affects the most-used technique to track conversions; the Facebook Pixel. Ad-blockers will also block the Facebook Pixel, regardless of cookie settings. Conversion API is the solution to this problem.


Setting up the Pixel

  • Go to events manager, logging in to your Facebook account

  • Click “Connect data sources” in the left sidebar

    insert-domain
  • Choose “Web”, name your Pixel

  • Enter store’s URL (e.g. demostore.jumpseller.com)

  • Choose “Pixel only”

  • Close the window asking to manually install the code or use a partner integration (Jumpseller already has the code installed)

  • Copy the ID of the Pixel and paste it in Jumpseller’s General Settings

insert-domain


insert-domain

Setting up Conversions API

  • Install Facebook Commerce

  • Login to FB Commerce; during the login, choose one of your existing Pixels or create another one (inside the “Meta pixel” option)

    insert-domain
  • If you created a new pixel or chose one with an unfinished configuration, go to events manager and choose to “Continue Pixel Setup”

    • Choose “Conversions API” > “Set up manually”
    • Choose the events we support via the API & Pixel
    • When reaching “See instructions”, ignore it, as Jumpseller already has all the necessary code installed

Events

Event Source Description Trigger Affected by iOS 14.5 privacy update
AddToCart Server Add product to cart Add product to cart No
Contact Server Submit contact form Visits contact page No
InitiateCheckout Server View first page of the Checkout process Visits Checkout page No
Purchase Server Reach the final Checkout success page for the first time Visit to the success page No
CompleteRegistration Server Customer registers in store Customer is registered No
Search Server Submit a search query Visits a search page No
ViewCart Server View Cart page Visits the cart page No
ViewContent (Category) Server View page of category Visits a category page No
ViewContent (Product) Server View page of product visits a product page No
AddPaymentInfo Browser View Checkout’s page after adding payment info Visits Payment Page in Checkout Yes
Lead Browser Customer logs in or registers at store Visits log in page Yes
PageView Browser View any page Visits any page Yes

All events marked as “Server” (Conversions API) are also available on the “Browser” (Pixel), however, they’re only sent via the API if it is available.

For more information about events, please review Facebook support documentation:


FAQs

  • Not receiveing browser events.

    If you are only receiving browser events instead of server events, make sure that you are “logged in” to the Facebook Commerce sales channel.

  • Browser events being sent alongside server events with anomalous data.

    In this case, you should disable codeless event tracking (see image below). We already handle all events with our own code, Facebook should not track button clicks and page loads on top of it (we only send events via either browser or server, never both at the same time).

    insert-domain

If you still have questions, please contact us and we will get back to you as soon as possible.

Start selling in Facebook Commerce with Jumpseller

Free trial for 14 days. No credit card required.