Skip to main content

Embed Flow's Cookies

Documentation on the Cookie that Embed Flows generate

Updated this week

The "_flowbox" Cookie

Once you implement an Embed Flow in your site, it will automatically generate a cookie named _flowbox. This cookie allows to track the visitor's interaction with the Embed Flow (visualizations, clicks...) and to visualize it in Flowbox's Analytics panel.

This cookie is automatically generated upon the Flow's load, but it can also be disabled by setting the allowCookies parameter to false during the Flow's initialization, allowing you to prevent the cookie from being generated depending on the consent that the visitor has granted.

When preventing the _flowbox cookie from being generated, it's no longer possible to track any data from the user.

The allowCookies parameter and how to manage it is explained in further detail in the following guide:

Cookie specifications

Cookie name

Category

Expiration time

Type

Description

_flowbox

Analytics

400 days

First-party

Tracks user interaction (views & clicks) with Flowbox UGC widgets and also the content of the user's purchased orders.

When using the Email automation feature for the Ratings & Reviews product, it's required to add additional fields in the Checkout Script in order to allow Flowbox to track personal data such as the user's name and their email.

This personal data is used exclusively to send users an email after their purchase, asking them to post a Review for the products they've purchased through a form.

How it works

The _flowbox cookie is generated when an Embed Flow loads. The cookie's value is a randomly generated UUID, which allows to track the user's interactions anonymously.

When interacting with an Embed Flow, events based on the actions "view" and "click" will be triggered. These events are tracked by Flowbox Analytics suite, and can be linked to a specific user by the UUID that the _flowbox cookie has generated.

Additionally, when tracking an finished order through the Checkout Script; a "checkout" event will also be triggered (identified by the same UUID), allowing to match the order with the previous Embed Flow interaction. This way, it's possible to establish if this sale counts as a Conversion or not.

Additional resources

Did this answer your question?