Skip to main content
Sign in

Search

Flight Control Help Center

Website Pixel Setup

  • Updated

General

You can create a website pixel data source in Flight Control that provides event data for all your websites, injecting dynamic parameters in real time based on user interactions.

Flight Control's website pixels support the following:

  • Page view tracking
  • Standard commerce and conversion events
  • Custom events tracking

Create a Website Pixel

Step 1: Create a Pixel in Your Account

  1. Go to Account > Data Sources.
  2. Click Create > Add Website Pixel.
  3. Enter a name for the pixel.
  4. Select a product type for the pixel.
  5. Select a product type (vertical) for the pixel: E-commerce, Flight, or Car.
  6. Click Add.

The new data source will be added to the Data Sources table.

Step 2: Configure Events for the Pixel

For each event, you can map individual incoming event parameters to names configured in your account's taxonomy.

This allows you to use custom values in a campaign - by mapping custom values to specific product attributes - e.g., for a cruise line campaign, mapping "Text Field 1" to ship name or departure port - you can retarget users with products that share the exact characteristics they previously engaged with on the website.

To configure events for the data source:

  1. Hover over the website pixel in the table and click Mapping.
    • The Events Configuration pane will open and display preconfigured website pixel events specific to your pixel's product type.image2.png
  2. Optional. Add or edit events as needed.
    1. Click Add Event to create a new event, or click on an existing event to edit it.
    2. If needed, change the product funnel event type (e.g., Purchase, Add to Card, Details, Custom, etc.).
      • Important: To prevent duplicate tracking, standard funnel event types (e.g., Search, Add to Cart) can only be selected once per pixel. Once chosen, that type is removed from the dropdown of event types you can select. However, you may create multiple Custom or Purchase events per pixel.
    3. Optional. If needed, configure the event's parameters.
      1. Select a Flight Control parameter name. (These are configured in your account's 1st Party Data Taxonomy.)
      2. Enter the expected parameter key name in the pixel. 
        • Note: Selecting a Flight Control name automatically populates this field in lowercase with underscores (e.g., Body Style becomes "body_style"), which can be edited as needed.
      3. For subtype event parameters: Enter a subtype name and value.
      4. Optional. Click Advanced Mapping Settings to configure a rule that modifies the parameter's incoming website pixel data, such as changing capitalization, replacing values, using Regex, and more. (These settings are for advanced use cases.)
      5. Optional. Click Add Parameter to include an additional parameter for the event.
    4. Repeat previous steps as needed to continue customizing the website pixel.
  3. Click Submit.

Step 3: Download & Implement the Pixel Code

  1. In the Data Sources table, hover over the website pixel and click Download Pixel Code.
    • The Get Code for Data Source modal will be displayed.
  2. Select an Implementation Type and follow its subsequent steps:
    • Script - This downloads an Excel file to your device that contains the global and event tracking scripts that you can implement in your website’s code.
      1. Copy and paste the file's global pixel code into the <head> tag of the website HTML document, just above the closing </head> tag. This will initialize the Flight Control script.
        • Note: This global pixel code will load on all pages and will automatically fire a “page view” event.
      2. Implement the tracking scripts, such as "Add to Cart" or "Search," for each event type/action and pass data through their parameters. You can use the following methods to implement them:
        • Call event trackers in separate <script> tags, placed after the base pixel has loaded. This is the preferred method.
        • Add the clq('track', ...) call directly within the base pixel snippet.
    • Manual Iframe - This downloads an Excel file to your device containing the <iframe> tags to use for each event type.
      1. Replace placeholder parameter values with real website data in the <iframe> tags.
    • Manual Image - This downloads an Excel file to your device containing the <img> tags to use for each event type.
      1. Replace placeholder parameter values with real website data in the <img> tags.

Preview Event Tracking Code

You can preview implementation code blocks for each website pixel event directly inside the Events Configuration drawer.

Click any of the three implementation preview icons on an event to preview its live-generated code snippet in a modal:

  • Script: JavaScript clq('track', ...) snippet.
  • IMG: Standard 1x1 tracking pixel URL.
  • iFrame: An iFrame-based tracking tag.

Monitor Website Events in Real Time

Use the Monitoring diagnostic tool, located in the Events Configuration pane, to validate that your website pixel ingestion matches your configured mappings.

The Monitoring Events table shows the most recent pixel payloads received by the server, defaulting to a sample size of 3 hits per event type, prioritized by those that contain mapping discrepancies.

It also validates live data against your active configuration based on the following logic:

  • Green Check (No Issues): The event type is recognized, and all parameters received in the raw pixel match your configuration perfectly.
  • Red Triangle (Discrepancy Detected): This status is triggered when:
    • An event parameter is received but not mapped. Add this parameter to the 1P Data taxonomy and use it within the relevant event parameter mapping.
    • A mapped parameter isn’t received in the pixel event.
    • An unrecognized event name is received.