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 understand the behavior of their audience and the actions they are taking on their sites.

Once your Flowcode Pixel is set up, insights can be analyzed on the analytics dashboard in your account. Whether you’re trying to study pageviews or purchases, Flowcode’s native UI is providing a central hub to distill learnings from post-scan actions.

Leveraging the Flowcode 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. This also provides insight into existing gaps in any offline to online conversion funnel, allowing brands to identify exactly where through the campaign and online experience they may be losing a customer.

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.

Using the Flowcode Pixel, users will be able to:

UTMs are primarily used to track the effectiveness of marketing efforts (for example, we use UTMs to track clicks to pages in emails). Whereas a pixel is used to track each individual user's interactions and conversions on a website that result from specific campaigns.

UTMs show you the path a visitor took, but they don’t tell you when a conversion actually happens. The Flowcode Pixel fills that gap by tracking real conversions, where and when they occur, giving you full-funnel visibility.
​

Unlike UTMs, which are session-based and anonymous, the Pixel can tie conversions back to real users through FlowID, if they submit identifying information like an email. This unlocks identity-based insights UTMs simply can’t offer.
​

Plus, the Pixel makes performance data more accessible: marketers can analyze campaigns and see what’s working without needing help from a data team — reducing friction and speeding up decision-making.
​

We recommend using both: UTMs for consistency with tools like Google Analytics, and the Flowcode Pixel for deeper attribution, identity resolution, and faster, self-serve 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. While we generally recommend configuring one pixel per domain for clarity and consistency, deploying it across multiple sites is valid for testing or demo purposes.
​

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.

While we typically recommend creating a separate Flowcode Pixel for each website to keep data clean and segmented, one Pixel can be deployed across multiple domains (up to 10) for testing or demo purposes. Keep in mind that tracking across domains is supported, but for production use cases, using a unique Pixel per site is usually the best practice.

One! You should use the same Flowcode Pixel if your landing page and checkout page are part of the same root domain (including subdomains). You may need to place the Pixel in multiple locations across your site to ensure it fires correctly on all pages, but the code itself should remain the same. This ensures full tracking coverage throughout your funnel on the same site.

Out of the box, the Flowcode Pixel automatically tracks key user actions on your website to help you understand engagement and conversions. Here’s what it captures:

All of the above events can be fine-tuned using filters like specific URL paths, HTML element IDs, or custom conversion settings (See next FAQ 'Can I customize which events the Pixel tracks?').

In addition to these automatic events, you can configure custom event tracking for deeper, tailored insights based on your specific use cases.

Yes - the Flowcode Pixel is fully configurable and allows you to fine-tune which events are tracked, where they are tracked, and whether they count as conversions. This is done using filters and tracker settings that control what data is collected across different parts of your site.

Check out the Flowcode 2 Pixel - Event Configuration Guide for a breakdown of what you can customize.

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

When that happens:

Important: The Pixel must be installed before the traffic is driven to the site, and it must be configured to track the correct form fields. Data is not tracked retroactively.

The Flowcode Pixel only works on Flowcodes that point to a website you can edit the html code of. Unless you can access the backend code for the destination, the Pixel cannot be installed. Codes that point to SMS, email, vCard, or destinations other than a website usually send to a third-party site that you don’t have access to, so the Pixel would not work with them.

The Flowcode pixel doesn't have a native integration with Google Ad accounts. If you wanted to get some Google Ad behavior tracked then you could use UTMs or you could have that Google Ad link back to your site upon which that Flowcode Pixel was installed.

The goal of the Flowcode Pixel is to measure offline to online campaigns. Whereas a Google Ad would be online to online. So we encourage you to use the Flowcode Pixel when it starts with a scan or short URL click, as opposed to a different entry point.

We are actively developing self-service pixel configuration. Until this is ready, please work with your AE and/or CSM to access the Flowcode Pixel HTML snippet.

Once self-service pixel configuration is complete, Organization Admins will be able to create/delete a pixel and define conversion actions.

You have two installation options:

Creating the Pixel is the first step - it generates the unique code snippet that gets installed on your website. This Pixel allows Flowcode to track user behavior across your site, such as page views, button clicks, and form submissions.
​

Defining a conversion action comes next. This is where you tell the Pixel what success looks like by specifying which user actions should count as conversions - for example, submitting a contact form, clicking a specific button, or viewing a thank-you page.

In short:

You can define conversion actions when you configure your Pixel, or update them later as your goals evolve.

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. You can also apply filters, like URL paths or specific HTML element attributes, to ensure conversions are tracked only where they matter most.
​

This flexibility helps you capture the full picture of how users are engaging with your site and what actions are driving success.

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.

No developer work or code changes are required after the initial installation.

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 may result in incomplete tracking, especially for multi-step journeys.

Yes. The F1 Pixel only supports pageview tracking out of the box—all other events (such as button clicks or form submissions) require custom implementation.

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

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

Yes. An F2 Pixel can be transferred to the appropriate organization once it’s been set up.

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

No, it does not. 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 and the data will start appearing in your dashboard immediately.

When someone scans a Flowcode and is redirected to a page with the Pixel installed, their activity, such as visits and conversions, will appear in:

⚠️ Note: The current UI only supports displaying visits and conversions from pixeled sites. While the Pixel collects additional event data (e.g., button clicks, page views, and custom events), these are not yet surfaced in the dashboard UI. 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.
​

In the analytics view of a Flow, each module (e.g., a website button or link) may display a conversion count in its own row. A conversion will be counted if either of the following happens:

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.

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, the Flowcode Pixel will still fire (i.e., technically run) even if a user blocks all cookies and tracking through the brand’s privacy or cookie settings.
​

However, if the user has opted out, the Pixel will not capture any session-level data - such as visit source, conversion attribution, or other analytics tied to that session.
​
As a result, their activity will not appear in Flowcode’s analytics dashboard.

So while the Pixel is still active on the page, it respects the user’s privacy preferences and does not report their behavior.

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.