Best practices for Meta pixel standard event setup

Standard events help you understand how people are interacting with your website, optimise for conversions and build audiences. Here are best practices for using standard events with the Meta pixel:

• Copy the code snippet exactly as it appears. Standard event codes are case sensitive. For example, the standard event code for Page views is fbq('track', 'ViewContent');. If you accidentally add fbq('track', 'viewcontent'); to one of your web pages instead, you'll see an event called viewcontent appear in your Ads Reporting as a custom event rather than a standard event. Learn more about standard and custom events.
• Set the value and currency for the purchase standard event. This will help better reflect your conversion. Learn how to set the value and currency of your Meta pixel standard events.
• Add a full funnel of events. For example, view content, add to cart and purchase. This will allow your pixel to receive all relevant purchase actions. For example, if you sell toys on your website, you would place the corresponding standard event code on your add to cart page and purchase page.
• Use the Conversions API in addition to the Meta pixel, and share the same events using both tools. We call this a redundant event setup. For example, if you share the purchase, initiate checkout and contact events using the pixel, share those same web events from your server using the Conversions API. Redundant setups are useful because the Conversions API allows you to share website events that the pixel may fail to capture due to network connectivity issues or page loading errors. Learn how to check if you're sharing redundant web events.

Note: The page view event is included as a part of your pixel base code. Page view tells you when someone lands on a web page with the pixel base code installed. This is different to a view content standard event, which is not included as part of your pixel base code.