Skip to main content

How to Generate a Flowcode 2 Pixel

Updated this week

Before installing the Flowcode 2 Pixel on your site, you’ll first need to generate the pixel snippet(s) directly in the Flowcode platform. This self-serve setup allows you to create, configure, and copy your pixel script in just a few steps.


Step 1: Name Your Pixel and Set Its Domain

Start by giving your pixel a clear, recognizable name and defining where it should track activity.

How to do it:

  1. Enter a Pixel name (for example, Brand Site (Prod) or Landing Pages – US).

  2. Add your root domain (e.g., https://brand.com).

    • We recommend only one domain to keep things simple.

    • Use the root domain only and do not include paths or query strings.

    • Subdomains are automatically included.

  3. Click Next to continue.

This ensures your pixel is correctly associated with the domain(s) you want to track.


Step 2: Choose a Conversion Type

Next, select what actions you want the pixel to track. We recommend choosing just one conversion type most indicative of the action you’re trying to capture.

Callout: Advanced users can configure multiple conversion types depending on their goals and can toggle those types on and off at the flow level.

Available conversion types:

  • Page views: Track when a page loads.

    • Optionally limit tracking to specific URL paths or exclude certain paths.

    • For example, you would enter into Flowcode the following:

      • "Only pages where path contains: /order-confirmation"

  • Form submissions: Track when a form is successfully submitted (e.g., lead or signup forms).

    • Configure using attributes such as class names or IDs

      • <form id="demo-request-form">

    • For example, you would enter into Flowcode the following:

      • Attribute = ID

      • Condition = matches

      • Value = demo-request-form

  • Button clicks: Track clicks on specific buttons.

    • Define the button using a class, ID, or selector.

      • <button id="request-demo-btn">

    Request a Demo

</button>

  • For example, you would enter into Flowcode the following:

    • Attribute = ID

    • Condition = matched

    • Value = request-demo-btn

  • Purchases

    • If you’d like to capture revenue associated with a purchase made, this is the preferred conversion type. Make sure to toggle on this conversion type, and proceed to the next step.

After configuring your desired conversion(s), click Save and preview to proceed.


Step 3: Copy and Install Your Pixel

Once your pixel is created, Flowcode will generate a base pixel script for you and a purchase snippet if you selected the purchase conversion type.

If choosing the Purchase Conversion Type, please follow the instructions here to install both the base pixel and the purchase pixel.

To install your base pixel:

  1. Copy the base pixel code snippet.

  2. If you’re using Google Tag Manager, paste the snippet into a Custom HTML tag and set the trigger to All Pages.

  3. If not, add the script to your website before the closing </head> tag on the pages you want to track.

For more in depth instructions on how to install your base pixel, please read this guide.


Step 4: Enable Pixel Tracking on Your Flow

Installing your pixel sets the foundation, but pixel tracking must also be enabled at the flow level to start capturing conversion data. This step tells Flowcode exactly which flows should receive conversions from your pixel, giving you precise control over where and how conversions are tracked.

How to do it:

  1. Open the Flow Editor for the flow you want to track.

  2. Navigate to the External Destination you want to track.

  3. Toggle Enable Pixel Tracking on.

  4. Select the Flowcode Pixel you want to use.

  5. Choose which events should be marked as conversions (form submit, page view, button click, and trigger events for purchases).

Once enabled, this flow will begin sending conversion events to your selected pixel based on the configuration you set earlier, ensuring your reporting reflects intentional, high-value user actions.

Did this answer your question?