Flowcode 2 Pixel FAQs

A tracking pixel is a snippet of code that businesses place on their website to understand how visitors behave on the site. Pixels can track different kinds of visitor actions, called events, such as viewing a webpage, clicking a button, purchasing an item and more.

Tracking pixels are often used to report on and optimize marketing campaigns that are driving users to complete a specific action on a website. For example, a business might use the Flowcode Pixel to track form submissions or purchases from visitors who land on their site after scanning a Flowcode on a flyer, packaging, or in-store signage.

The Flowcode Pixel is the first product of its kind to show a full funnel, offline to online, attribution model. From offline scans in the real world to online conversion, customers using the Flowcode pixel can measure how many consumers convert.

The Flowcode pixel is a conversion pixel, which means that it only tracks conversions. The pixel does not track other site activity not tied to conversions e.g. a user clicks a menu option on the top-nav.

Leveraging the Flowcode Conversion Pixel enables you to identify how traffic from your Flowcodes is converting on your site. The Pixel expands the view of your success tracking by collecting data through to the end conversion on your destination, allowing for full funnel ROI calculations. You can also use the pixel to track purchases/donations. Our platform captures the dollar amount tied to the given conversion.

Our pixel is built to take advantage of existing datalayer events you have configured on your website as well. We even offer a customer trigger, which can be used for any datalayer event your team wants to track as a conversion.

Additionally, the Flowcode Pixel powers FlowID - Flowcode’s identity resolution feature. When a visitor completes a form on your site and provides an identifier (like an email address), that information is sent back to Flowcode. This enriches your FlowID data, enabling you to tie scan activity and site behavior back to known individuals for deeper customer insights.

Conversions appear on:

Purchase conversions appear in the ‘Results’ tab of the Flow-level analytics page. Aggregate purchase data is configurable via custom tables as well.

Purchases appear as “Purchases” in any aggregate charts. Custom triggers appear as ‘Pixel conversions’. Behavioral conversion events (form submit, pageview, and button click) appear as ‘Pixel conversions’.

⚠️ Note: In the platform UI, there is no differentiation between conversion types for the behavioral conversion events (button click, form submit, pageview). However, this data is still being collected and can be accessed via a data sync. To request access, please contact your CSM.

The image below shows what analytics for a pixeled Flow look like in the Flowcode platform:

This gives you real-time visibility into how each Flow is performing across all tracked visits and conversions.

If a user enters identifiable information (like an email address) into a form on a pixeled destination page, they will appear in the Known Users table on the Audience page. This table can be downloaded as a CSV and shared with your team.

UTMs can tell you which campaign a user came from, but that data lives outside the Flowcode platform and typically requires help from a data or analytics team to access and interpret.

The Flowcode Conversion Pixel goes further by reporting conversions directly within the Flowcode platform, giving marketers immediate, self-serve visibility into performance without relying on analytics resources. When users submit identifying information, such as an email address, the Pixel can tie conversions back to real people through FlowID. This makes it easier to understand not just what converted, but who did.

We recommend using both together: UTMs for consistency with tools like Google Analytics, and the Flowcode Conversion Pixel for deeper attribution, identity resolution, and faster decision-making through in-platform reporting.

We would not recommend using more than one Flowcode Pixel on a single website. One Pixel is sufficient to track user behavior across your entire domain, including any subdomains.

Yes, you can use a single Flowcode Pixel on multiple domains—up to 10 in total. We highly recommend against configuring one pixel per domain for clarity and consistency.

When specifying a domain, only the root domain is needed (e.g. mysite.com). All subdomains (like www.mysite.com or subdomain.mysite.com) are automatically included. Query strings are not considered.

Lastly, if you update or add domains to an existing Flowcode Pixel, there's no need to generate a new pixel snippet.

Yes. The best practice is to use a unique pixel per domain.

No. The Flowcode Pixel only tracks user activity if the visit originates from a Flowcode scan or short URL click associated with a conversion flow that has Pixel tracking enabled. In other words, there is no 30-day attribution period. The Flowcode Conversion Pixel uses session-level attribution.

If the user revisits the site directly (e.g., by typing in the URL or using a bookmark), their actions will not be tracked.

Yes! If you place the purchase pixel on the checkout page of your website, it will track all conversions and dollars spent, sending that critical information back to Flowcode. This allows you to seamlessly track and measure the full consumer journey, all in one place. Most customers use Datalayer events via a tag manager. As long as the revenue is passed to the tag manager via a Datalayer event, our pixel can transfer that data to Flowcode.

Yes. The F1 Pixel only supports pageview tracking out of the box—all other events (such as button clicks, form submissions, purchases, custom datalayer events) are not possible to track in Flowcode 1.

In contrast, the F2 Pixel offers enhanced functionality, including:

The Flowcode Pixel automatically tracks key user actions on your website to help you understand engagement and conversions better. Here’s what it captures:

Check out the Flowcode 2 Pixel Generation Guide for a more detailed breakdown.

By using the pixel, no 3rd party cookies are added to the client site. All the info Flowcode needs to tie a scan to user activity is stored as a query param. If a session cookie is generated, it will be classified as a first-party cookie because the pixel tag is hosted directly on your domain — either through a tag manager (like GTM) or embedded via custom JavaScript on your site.

Yes - the Flowcode Pixel is fully configurable and allows you to fine-tune which events (button clicks, form submits, and pageviews) count as conversions.

Check out the Flowcode 2 Pixel Generation Guide for a more detailed breakdown.

Yes for form conversions. If the Flowcode Pixel is installed on an external site and configured to track form conversions, it can capture identifiable information (like email or name) when a visitor completes the form.

When that happens:

The Flowcode Conversion Pixel only tracks conversions on websites.

No. Flowcode does not support 3rd party pixels. For example, you cannot place a Meta tracking pixel on a Flowpage to share which site visitors do or don’t convert.

Organization admins can access this pixel in the ‘Organization Settings’ tab of the Organization Admin Console.

Yes, you can define multiple conversion actions for a single Flowcode Pixel. This allows you to track different types of meaningful user behaviors on your site such as:

Each of these can be marked as a conversion event during your Pixel configuration. Page view conversions are filtered with specific URL paths, while form submissions and button clicks are filtered using HTML attributes (IDs, class names).

Yes, you can add new conversion actions without needing to reinstall or change the Pixel code on your site.

Once the Flowcode Pixel is installed, all event tracking and conversion logic is managed through the Flowcode platform. That means you can update your settings—such as defining a new page view, form submission, or button click as a conversion—at any time, and the changes will take effect automatically.

For button clicks, page views, and form submissions, you can simply configure the base pixel to fire on all pages. For a purchase and for custom datalayer triggers, you will need both the base pixel to fire on all pages and a purchase pixel / custom datalayer trigger pixel to fire directly on the page that hosts the conversion.

We recommend installing the Flowcode Pixel on every page where you want to track user behavior, especially if you're measuring full-funnel performance across landing pages and forms.

If you’re using Google Tag Manager (GTM), this is simple - you can apply the Pixel to All Pages, which will universally integrate the Pixel across your entire site with a single setup.

If you’re installing the Pixel directly on your site, you should place the Pixel code before the closing </head> tag on every relevant page. This ensures consistent data collection and accurate conversion tracking.

Missing pages will result in incomplete tracking.

No. The F1 and F2 Pixels are not compatible and cannot be transferred between systems.

Please contact your CSM to deactivate a pixel. Once deactivated, the pixel will stop registering activity.

Deactivating a pixel will stop it from registering activity. In order to make structural changes to the code of your site you would additionally need to manage it directly on your domain or through Google Tag Manager if you installed it that way. The only way to ensure that code is no longer attached to your site, even if latent, is to manually remove it the same way you manually installed it.

The Pixel fires immediately after installation. The conversion data will appear in your dashboard immediately.

While the pixel still technically fires, it respects the user’s privacy preferences and does not report on their behavior. As a result, their activity will not appear in Flowcode’s analytics dashboard.

Once the Pixel is installed, you can follow these steps to verify that it's correctly installed.

For more help, reach out to your dedicated CSM.