Connecting the FB Pixel to a project on Kwiga

Facebook Pixel helps track user actions on your website and analyze ad performance. On Kwiga, you can easily add the Facebook Pixel through the tracking settings menu.

Go to Tracking Settings

Open the Site menu → Tracking Settings: GTM, GA, GAds, FB.

Click + (Add Tracking) to start the setup process.


Select the Tracking Code Type

In the pop-up window, choose Facebook Pixel. The system also allows you to add other types of tracking:

GTM — Google Tag Manager code

GA — Google Analytics code

GAds — Google Ads tracking code

FB Pixel — code for tracking Facebook events

Fill in the Fields

After selecting Facebook Pixel, you’ll need to fill in the following information:

Alias — a unique name for the tracking code (visible only to you).

Facebook Pixel ID — a unique identifier for the pixel, which you can find in your Facebook Ads Manager settings.

Conversion API Access Token (optional) — learn more here.

Conversion API Test Code (optional) — learn more here.

Domain Verification Code (optional) — if you need Facebook to verify your domain, add the hash code here. We’ll place it on your school’s pages. Learn more here.

Choose the event tracking method.

Kwiga supports two tracking methods:


Only Pixel — the classic method where events are tracked via the browser.

Only Conversion API — events are sent directly from the server for better accuracy.

Pixel and Conversion API — a combined approach that transmits events through both the browser and the server for maximum reliability.

Define the scope of application

Specify how the Facebook Pixel will be applied:
You can enable tracking for the entire project or select specific pages by checking the relevant boxes.

You can enable tracking for the entire project or only for specific pages — simply check the boxes next to the pages where you want Facebook Pixel to be active.



Save the settings

Click Add to save your changes. After this, Facebook Pixel will start collecting data about your website visitors.

Thus, connecting Facebook Pixel on Kwiga takes just a few minutes and allows you to effectively analyze your audience and improve your ad campaigns.

Facebook Pixel Events

Standard events for Facebook Pixel are sent using the following method:

fbq("track", eventName, eventOptions)

Here’s a list of standard events:

• PageView – Triggered when a page containing the code is loaded.
  
  

• CompleteRegistration – Triggered when the registration step in a modal/block is filled out, the confirmation button is clicked, and registration is successfully completed.
  
  

• Lead – Triggered when a CTA form is successfully submitted in a widget or mini-landing. This event can be customized in the CTA form settings.

Important: To track events in a widget used on third-party sites, the main tracker code must be added manually to that site. The widget only sends the event.

InitiateCheckout – Triggered when a user lands on the checkout page for a product/offer.

AddToCart – Triggered on the checkout page when the user successfully proceeds to the payment page.

Purchase – Triggered upon successful payment and when the user lands on the “After Successful Payment” page (unless it has been changed in the offer settings). This event includes additional parameters:

• value – the payment amount
  
  

• currency – the currency of the payment

Standard Events Sent via Conversion API:

• PageView
  
  

• InitiateCheckout
  
  

• AddToCart
  
  

• Purchase

Custom Events for Facebook Pixel

Custom events are sent using the method:

fbq("trackCustom", eventName)

List of custom events:

• clickGetAccess – Triggered when the “Get Access” button is clicked on Course/Module/Lesson pages.