Standard events can be reported in the following format, where customData is optional and the first value 'track' should not be altered.

Standard events also support parameter objects with specific object properties, which allow you to include detailed information about an event.

fbq('track', 'eventName', {customData});

• Event Name (Évènements standards dans le lien ci-dessous)

There are predefined standard events, each of which covers a common type of user activity.

You can use one of the following standard events in your fbq track call by replacing the <eventName> in the template format above with the event name in the following table : **https://developers.facebook.com/docs/facebook-pixel/reference#standard-events**

• **Custom Data (**Propriétés des objets dans le lien ci-dessus)

These are the data you can send to provide more insights on each event, and can be further used on Facebook platform to create custom audience and custom conversions.

You can include one or more of these parameters as a JSON structure to the customData field in the fbq track call.

Best Practices to Consider :

Tip 1: Send the value and currency parameters when possible and always use the real-world value of the conversion. This allows you to understand the conversion, the Return on Ad Spend (ROAS) of a specific campaign, and optimize your ad delivery towards consumers with higher values.

Tip 2: The three parameters (content_ids, content_type, and content) are important for Dynamic Product Ads (described in the "Dynamic Ads" lecture). Make sure that the values are correctly sent if you're planning to run a DPA campaign.

For more information on standard pixel events and parameters, see the Facebook for Developers site : https://developers.facebook.com/docs/facebook-pixel/

(Cliquez sur "Prêt ? Commençons")