Now that you have set up your Pixel on your website, you might want to track more events happening on your website, especially if you have an e-commerce website or if you want to know when someone filled a form.

The main rule is to trigger specific events when a person is taken on a new page as a result of an action you want to track. On the Business Manager, Facebook is giving some raw templates to help you setting this up. You'll have to toggle the events you want to activate in order to track them.

Here are the standard events codes you might use for each specific use cases:

Purchase

Add this event into the page that confirms a purchase to collect data about people who bought articles on your website and the value of what they bought.

Base code

Here, the Pixel will fire a standard Purchase event every time it is fired, but without any indication about the value of the object purchased.

<script>
  fbq('track', 'Purchase', {
    value: 120,
    currency: 'USD',
  });
</script>

Generate Lead

Add this event into the page that confirms to a user he successfully filled and sent his information through your form. 

Base code

The code here is pretty simple since you should not need to put any other parameter (value or currency).

<script>
  fbq('track', 'Lead');
</script>

Complete registration

This event is pretty similar to the Lead one, but it should be used when a user is filling a form to register to your website. Add this in the confirmation page, after the completion of the form.

Base code

The code looks similar to the Lead one, so no need to push any other parameters to be able to track your users' registration.

<script>
  fbq('track', 'CompleteRegistration');
</script>

Add payment info

This event should be triggered when the user successfully added a payment method, so when a confirmation page is loaded.

Base code

<script>
  fbq('track', 'AddPaymentInfo');
</script>

Add to cart 

This event should be used when a user add something to their cart. It should be placed in the page where the user is redirected when adding a product into their cart. If the redirection is not happening, this event should be added in an inline way (see the Inline Actions article).

Base code

<script>
  fbq('track', 'AddToCart');
</script>

Add to wishlist  

This event should be used when a user adds something to its wishlist. It should be placed in the page where the user is redirected when adding a product into his wishlist. If the redirection is not happening, this event should be added in an inline way (see the Inline Actions article).

Base code

<script>
  fbq('track', 'AddToWishlist');
</script>

Initiate checkout 

This event should be triggered when a user initiated a checkout process. It should be placed in the page where the user is redirected when initiating the checkout process.

Base code

<script>
  fbq('track', 'InitiateCheckout');
</script>

Search 

This event should be triggered when the user is doing a search in your website, if you provide a search engine. Add the code in the page showing the results of the query.

Base code

<script>
  fbq('track', 'Search');
</script>

View content 

This should be used when a user is viewing details of a specific item for example.Add this code to the page where the user will be redirected when asking for more information.

Generic code

<script>
  fbq('track', 'ViewContent');
</script>
Did this answer your question?