Skip to main content
All CollectionsAnalytics & AccountsAnalytics & Revenue
How Octane AI Revenue & Quiz Analytics are Tracked
How Octane AI Revenue & Quiz Analytics are Tracked

Understanding Attribution, Cookies, and Best Practices for Accurate Data Syncing

Mark Baek avatar
Written by Mark Baek
Updated over a week ago

Octane AI uses a browser cookie to capture customer quiz answers before they've submitted an opt-in. If they submit an opt-in through an Octane AI feature later, this allows quiz data to sync through.

πŸ’‘ What you'll learn


Revenue attribution in Octane AI

πŸ’‘ Revenue & conversions analytics update

On February 10, 2024, Octane AI deployed an upgrade to revenue & conversions tracking in preparation for quiz A/B testing.

The following section describes how revenue & conversions are tracked in Octane AI. For any further questions or feedback, just reach out to our support team.

Octane AI has a 7 day attribution window, and counts an order if it was placed within that window after interacting with an Octane AI feature.

Feature

When can a customer be attributed?

Quiz

If an order is placed in the attribution window after landing on a result page.

Attribution isn't limited to quiz products and can still happen even if the customer didn't add products directly from the quiz.

Pop-ups

If an order is placed in the attribution window after landing on the submitted state.

This includes opt-ins but also if your pop-up has a custom CTA instead.
​
Note: Non-quiz pop-ups do not track revenue.

πŸͺ Octane AI's cookie & how it tracks revenue

Octane AI remembers customers through browser cookies. This means revenue may not attribute if an order was placed on a different cookie than the one that was used to interact with Octane AI.

For example, this can happen if a customer:

  • orders on a different browser / device.

  • uses incognito or private mode.

  • has erased their original cookie.

Remembering quiz answers with the cookie

When a customer takes your quiz, their answers will be remembered through their browser cookie. This means if the customer submits an email opt-in later (instead of when taking the quiz), their answers will still sync.

πŸ“• Testing Octane AI Features with Octane AI's Cookie

Because cookies remember answers, submitting multiple opt-ins under different emails may result in answers from previous quiz sessions being pushed through.

When testing opt-ins with different emails/phone numbers in a quiz, we recommend clearing cookies or using a new private / incognito mode each time.

Caveats with Revenue Tracking for EU-Based Users

There may be some issues with revenue tracking for EU-based users, which are related to the cookie consent banner and its settings. Our web pixel for revenue tracking relies on cookies, so it only tracks revenue properly if the cookies are accepted by the user.

If you use an app to manage your cookies and help you ensure that they are GDPR compliant, you need to check if they prevent web pixels from running on your page, as this will stop the revenue tracking. Using the default consent settings should make tracking work normally. To make sure nothing is interfering with our web pixel, we recommend reaching out to your cookie manager app's support.

Frequently Asked Questions (FAQ)

  • How do I see which products were ordered from my quiz?

You can visit your quiz's analytics page by clicking on your quiz name from the quiz page in Octane AI.

Products that were ordered directly from a quiz will be displayed in your result page analytics. Products that are not included in your quizzes won't be shown here.

  • Why are my quiz syncs pulling in the wrong custom properties?

Once you've verified that your custom properties are up-to-date in your quiz by going to Settings > Custom properties, another factor that can cause incorrect data to sync are cookies.

Cookies can remember quiz answers & results independent of an opt-in, which means if you submit different emails and phone numbers on the same cookie a customer profile may take on quiz data that was submitted through another email or phone number.

This happens disproportionately during testing! The most common scenario this might happen to real customers is for customers that shop on a single device with multiple customers which is luckily an edge case.

Did this answer your question?