All Collections
Flowcode Pixel
Flowcode Pixel: a sample customer journey
Flowcode Pixel: a sample customer journey
Corinne avatar
Written by Corinne
Updated over a week ago

For this example, we’ll be using an imaginary company called SOPI. SOPI is using Flowcodes in various marketing campaigns to analyze the conversion rates from different mediums. They’ve already installed the Flowcode Pixel to their website, so they’re ready to start tracking!

In this case, we are looking to track if someone sees SOPI’s code on TV, scans it, and ultimately purchases one of SOPI’s products.

When setting up the Flowcode Pixel and defining the Conversion Action, SOPI had created their Website Path as /thank_you (see below). Because the only page on SOPI’s website that includes /thank_you in its URL is the order confirmation page, the only possible way a customer would get here would be to complete a purchase. Hence why making your Website Path a URL specific to order confirmation is important.

Below is the journey customers will follow and what information will be collected by the Flowcode Pixel at various stages.

1. Sees & scans Flowcode

The customer sees the code you’ve put out into the world, whether in a TV commercial, magazine advertisement, product packaging, or anything in the offline world.

Pixel path: SOPI TV code

2. Lands on your website

Upon scanning the Flowcode, the customer is brought to the homepage of your website. This pageview is recorded and tracked by the Flowcode Pixel (see Pixel path below).

Pixel path: SOPI TV code > /homepage

3. Clicks on product link

The customer clicks on the ‘Shop Now’ link on your homepage, which brings them to the product page.

Again, this pageview is recorded and tracked by the Flowcode Pixel to add to the map (see Pixel path below).

Pixel path: SOPI TV code > /homepage > /pumpkin_oat

4. Adds to cart and checks out

The customer adds the product to their cart and goes to check out.

Again, this pageview is recorded and tracked by the Flowcode Pixel (see Pixel path below). You’ll notice that it’s just continuing to map out the pageview path the customer is following.

Pixel path: SOPI TV code > /homepage > /pumpkin_oat > /checkout

5. Completes order

The customer finishes the checkout process and lands on your order confirmation page.

Again, this pageview is recorded and tracked by the Flowcode Pixel to add to the map (see Pixel path below).

Pixel path: SOPI TV code > /homepage > /pumpkin_oat > /checkout > /thank_you

As noted at the beginning, SOPI had set up their Website Path as /thank_you, so since the customer in the example above makes it to the order confirmation page with the URL /thank_you, it registers as a Conversion in Flowcode Analytics and be attributed to the SOPI TV code.

Below is an example of what the Conversion Analytics Dashboard looks like as the codes get scanned and generate website traffic and conversions.


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

Did this answer your question?