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, hovering over an icon, 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 sites. For example, a business would use a Facebook Pixel to track account sign-ups from visitors that navigate to their site via a Facebook ad.

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 a native conversion 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.

The Flowcode Pixel is available with our Growth and Enterprise plans. If you’re interested in talking to our team about pricing, you can book a meeting here.

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.

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 won't necessarily tell you when a conversion occurs. Whereas the Flowcode Pixel will track when and where the conversion happens, as opposed to just the pathway they take. We’d recommend that you use both UTMs as well as the Pixel, so you're able to track in two different places, since lots of folks use Google Analytics as the source of truth.

We would not recommend using more than one Flowcode Pixel on a site. You should add one Pixel on your website, because you only need one way to track user behavior. In the current version of the Flowcode Pixel, you can establish one conversion event to track and measure conversions through.

Yes, you would want to generate a different Flowcode Pixel for each site, because we need to have the code running on each of the individual sites that we're sending traffic to in order for it to track the behavior of somebody as they are moving around on that site.

One! You would want to have the same Pixel if it's the same domain/website. If you're installing the Flowcode Pixel in Shopify, for example, there are two different spots where you'd paste that Pixel within the Shopify backend: theme.liquid before the closing </body> tag and in the “Additional Scripts” box in the checkout flow.
​

However, it will be the same Flowcode Pixel code. This will ensure that it both fires on every page as they move around on the site, as well as the checkout page itself.

The Flowcode Pixel captures and stores the following data by default:

If a user wishes to track conversions but hosts their conversion event, such as a checkout or payment, through a third-party payment processor, the client may not have control over the domain on which their conversion event takes place. In this case, the client would need to work with their vendor to ultimately install the pixel on that specific domain.
​

Some clients may have control over this third-party domain to insert the code snippet, however, others may need to forward the HTML embed to their provider to do so. Note that some providers such as Shopify require premium subscriptions (Shopify Plus) in order to install custom code on their checkout pages.

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 right. 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, as opposed to a different entry point.

To get started with the Flowcode Pixel, head to the Analytics section in the left side navigation. Here, you will be able to initiate set up through the Pixel Management tab. You can then locate your Pixel-related analytics under the Conversions tab.

Currently, only account Admins are able to create or delete a pixel. However, installation on the client's site or deletion can be managed by other account Members by accessing the Pixel on the management dashboard and copying the pixel code into google tag manager.

The Flowcode Pixel can be set up in three simple steps. For more details on creating a pixel, defining a conversion action, and installing a Pixel on your site, a step-by-step guide can be found here.

This would normally be something done by an IT team so if you have an IT team that's able to access the backend of your website, they would be able to install the Pixel. Usually, it's done through a tool like Google Tag Manager if that's something that you would leverage for your website but again would be something we need to ask your IT team.

If you don’t have an IT team, no worries! All you need is access to your website’s builder and you can follow these instructions.

If you select Setup Flowcode Pixel, you will generate a code snippet to add to your website that will build a direct link between your Flowcode campaigns and your domain. This will enable you to universally track customer behavior across your site on each page.

If you select Setup Conversion Action, you will still complete the same steps of the Pixel set up, but add an additional step of defining a clear conversion url path you would like to track (e.g. /order-confirmation). If you are looking to specifically track a clear action on your website, this may be the best selection for you.

Currently we support one conversion action, which is if a certain page on your website was reached like an “/order-confirmation” page.

Currently, you cannot add a conversion action path or edit a pixel after creation. The client will either need to reach out to Flowlytics to update the pixel to add multiple paths, or if the pixel has not been placed yet on their site then delete the pixel and create a new one. Still if they want multiple conversion paths like “/order-confirmation” and “/form-submission” they will need to reach out to CS/flowlytics to get that update as it is not in the UI yet.

If you would like to define a new conversion action to be tracked on your website, you will need to go through the Pixel + Conversion Action creation flow again, as well as install that updated Pixel to your website via Google Tag Manager.

No, when using Google Tag Manager, you can apply this to All Pages which will universally integrate the Pixel across all site pages.

You can check that your Pixel has been installed either through the platform you used to install the Pixel (Google Tag Manager) or through the Flowcode platform.

You can also search on your webpage code for “cdn.flowcode” to see if the pixel is loaded on the site.

Once you install your Pixel using Google Tag Manager, you will see the Workspace Change logged on your Overview Dashboard. This is indicative of successful installation.

Similarly, you can head to Analytics then Conversions to view your Conversion Analytics Dashboard. By completing a sample flow of your campaign using another browser, you will begin to see these scans, pageviews, and conversions registered after a couple hours.

For immediate verification of events after the pixel is installed on the site:

The Flowcode Pixel can be natively deleted from the Flowcode platform. By clicking the three dots on the side of a specific domain, you can access the domain details. Here, there is a Deactivate Pixel button that will stop recording activity and conversions.

No, it does not. The Deactivate Pixel button will only 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 can begin to track data instantly. The data will start appearing in the dashboard on a couple hour delay.

The Conversion Analytics Dashboard holds all Flowcode Pixel performance data and will populate in this dashboard after a slight delay. This data can also be exported and downloaded as a CSV or PDF to share with other team members.

In your dashboard, you can navigate through every customer interaction on your site with efficiency. From page views to conversions, get a full funnel view of your user's journey.

Yes, you can create data segments and view information by specific folders, tags, or teams. The filters that you create make it easier to manage and report on various campaigns or client activities within a single account.

No, the Pixel will not fire events if the user blocks all cookies and site tracking via the permissions (privacy policy and cookie settings) on that brand’s site.

However, if the user has these Chrome settings below they will be able to see a conversion in an incognito browser.

But, if they block all cookies like this below then they will not be able to see events.

For more Flowcode Pixel-related information, check out these articles:

For more help, please email our support team or reach out to your dedicated Client Success Manager.