Intelligems Docs
  • Welcome to Intelligems
  • Getting Started
    • Getting Started
    • Adding Intelligems Script to your Theme
    • Updating the Intelligems Script
    • Common Use Cases
      • Price Test Common Use Cases
        • The Straddle
        • The Double Down
        • The Strikethrough
        • The Great Discount Debate
        • Savings Showdown: Volume Discount vs. Price Discount
      • Shipping Test Common Use Cases
        • The Flat Fee Face Off
        • The Threshold Trials
      • Content Test Common Use Cases
        • Landing Page Testing
        • Testing a Brand New Theme
        • Testing Different Imagery
        • Testing Cart Elements
        • Testing Announcement Bar Text
        • Navigation Menu
        • Testing Checkout Blocks
      • Offer Test Common Use Cases
        • The Volume Discount Duel
        • Gifting Games
    • Best Practices
      • đź§ŞTest Design Best Practices
      • âś…Best Practices During a Test
    • General FAQs
  • Price Testing
    • Price Testing - Getting Started
    • Price Testing Integration Guides
      • Integration Guide using Shopify Functions
        • Step 1: Add Intelligems JavaScript
        • Step 2: Tag product prices
        • Step 3: Update your cart
        • Step 4: QA your integration, and publish your changes
      • Integration Guide using Checkout Scripts
        • Step 1: Add Intelligems JavaScript
        • Step 2: Tag product prices
        • Step 3: Add the Checkout Script
        • Step 4: Update your cart
        • Step 5: QA your integration, and publish your changes
      • Integration Guide using Duplicate Products
        • Step 1: Add Intelligems JavaScript
        • Step 2: Tag product prices
        • Step 3: Hide duplicate products from collections pages
        • Step 4: Configure duplicate products
        • Step 5: QA your integration, and publish your changes
      • Troubleshooting
        • How to Add the data-product-id and/or data-variant-id Attribute to an Element
      • Replo Page Builder
    • How to Set Up a Price Test
    • Price Test QA Checklist
    • Starting a Price Test
    • Ending a Price Test
    • Testing Prices with Subscriptions
      • Testing Prices with Recharge 2.0 or Stay.Ai
      • How to Set Up a Price Test using Duplicate Products and Recharge Subscriptions
      • How to Set Up a Price Test using Duplicate Products and Skio Subscriptions
      • Managing Duplicate Products when Redirecting to Duplicate PDPs
    • Multi-Currency Testing
    • Price Testing FAQs
  • Shipping Testing
    • Shipping Testing - Getting Started
    • How to Set Up a Shipping Test
    • Shipping Test QA Checklist
    • Starting a Shipping Test
    • Ending a Shipping Test
    • Shipping Progress Bar Integration
    • Shipping Testing FAQs
  • Content Testing
    • Content Testing - Getting Started
      • How to Set Up a Split URL Test
      • How to Set Up an Onsite Edits Test
      • How to Set Up a Template Test
      • How to Set Up a Theme Test
      • How to Set Up a Test using our JavaScript API
    • Content Test QA Checklist
    • Ending a Theme Test
    • Content Testing FAQs
  • Personalizations
    • Personalizations - Getting Started
    • Personalization Modifications
      • Offer Modifications
      • Progress Bars
      • Offers: Integrating Widgets
      • Offers: Running a Large Number of Offer Personalizations with Shopify Functions
      • Theme Personalization Precautions
    • Targeting Personalizations
    • Targeting Modes for Personalizations
    • Previewing Personalizations
    • Testing Offer Personalizations
    • Offers Limits
    • Offer Combinations
    • Scheduling Personalizations
    • Rolling Out Tests
    • Personalizations FAQs
  • General Features
    • Targeting
      • Audience Targeting
      • Currency Targeting
      • Page Targeting
      • Mutually Exclusive Experiments
      • Targeting FAQs
    • Onsite Editor
    • Image Onsite Editor
    • CSS and JavaScript Injection
  • Analytics
    • Overview
      • How orders and sessions are attributed to experiments
      • Order and revenue accounting
      • How experiment targeting affects analytics
    • Analytics FAQs
    • Metric Definitions
      • Revenue
      • Conversion Funnel
      • Profit
      • Subscriptions
    • Filters
    • Statistical Significance
    • Timeseries
    • Custom Events
      • Overview
      • CSS Selectors
      • Scoping to specific pages
      • Custom Javascript Events
      • Testing Custom Events
      • Using custom events in experiment analytics
    • How to Add Profit to Intelligems Analytics
    • How to Add Product Groups to Intelligems Analytics
    • Tagging Orders by Test Group in Shopify
    • Exporting Data
    • Data Sharing
  • Performance Optimization
    • Site Performance
    • Optimizing Your Price-Test Integration
    • Anti-Flicker Modes
    • Edgemesh
  • Integrations
    • Google Analytics 4 Integration
    • Amplitude Integration
    • Heap Integration
    • Segment Integration
    • Heatmap Integrations
      • Integrating with Microsoft Clarity
      • Integrating with Heatmap.com
      • Integrating with HotJar
    • Navidium Testing
  • Developer Resources
    • Javascript API
      • User Object
      • Price Object
      • Campaigns Object
        • campaigns.getAll()
        • campaigns.getGWP(options)
        • campaigns.setHistoryStatus(params)
    • Intelligems Theme Snippets
    • Advanced Settings
    • Cart Permalinks
    • Targeting By Customer Parameters
    • Custom Add to Cart and Order Completed Events
Powered by GitBook
On this page
  • Default filters
  • Filter by time
  • Filters pane

Was this helpful?

  1. Analytics

Filters

Intelligems offers several filters that you can use to drill down on the sessions and orders included in experiment results.

Default filters

There are a few filters that are always on behind the scenes:

Orders

  • Recurring subscription orders (i.e., orders that are placed automatically, and are not the first in a recurring series) are excluded

  • Refunds, voids, and cancellations are excluded

  • Free orders (i.e., orders with $0 in net revenue) are excluded

  • Orders placed while an experiment is

Sessions / visitors

  • Sessions that started before an experiment was started, or while an experiment was paused, are excluded

  • Visitors who open an experiment in Intelligems preview mode are excluded

  • Bots are excluded

Filter by time

You can use the datepicker to filter by date and time. Only sessions started and orders placed during the filtered period will be included in results. Intelligems uses your store’s local timezone for all dates and times. You can see this timezone in the information bar at the top of the Key Metrics analytics page.

Filters pane

All other filters are available in the filters pane, which you can open by clicking the “Filter” button in the analytics header. Filters are “ANDed” together across sections, and “ORed” together within sections. For example, if you were to select “Desktop” from the Device Type filter section and check off “Paid Social” and “Google” from the Source Channels & Sites section, this will filter to visitors on a Desktop device who came from either a Paid Social source or from Google.

Available filters include:

  • Device Type: filter between Desktop vs. Mobile visitors. Tablets like iPads are generally included in “Mobile”

  • Visitor Type: filter between New vs. Returning visitors. A “Returning” visitor is a visitor who had visited the site while Intelligems was installed in a prior session before the experiment was started. Note that on initial installation, Intelligems won’t have seen your visitors before, so all visitors will be treated as new. It typically takes about 2 weeks for this data to normalize, and will become more accurate over time.

  • Source Channels & Source Sites: filter to visitors who came from certain sources. If you check off multiple sources, they’ll be “ORed” together, for example, checking off Paid Social and Google will filter to visitors who came from either a Paid Social source or from Google. Visitors who had multiple sessions are attributed to the source for their first session in the experiment. For example, if a visitor comes through a Paid Social ad and then comes back directly to the site, they would be considered Paid Social.

  • URL Parameter: filter the url parameters (eg, UTM parameters) set on a visitor’s landing page during their first session in the experiment. The parameters used here are those that were on the first page of the first session during which the visitor was exposed to the experiment, even if the visitor was not exposed on that page. For example, say a test is running targeted on a product page, and the visitor comes through an ad and lands on a landing page, then clicks through to a product page. The URL parameters considered for this filter are those that were set on that first landing page, even if they do not persist beyond that point.

  • User Behavior: filter by user behavior, including conversion funnel stage

    • Conversion Funnel: For the conversion funnel, a visitor counts towards a stage if they reached at least that stage. For example, a visitor who started checkout and reached no further would be included in the “All Stages,” “Added to Cart,” and “Started Checkout” filters.

    • Views: When "Orders with Target Products" is active, "Visited Product Page" means "Visited Target Product Page."

  • Filter Orders by Product: this filter is available only for price tests, or if you have chosen “Count only orders containing certain products” during experiment setup.

    • When “Orders with Target Products” is selected: only orders that contained at least one target product are included

      • For example, say product ID 123 is selected as a target product, and my order had two line items, one unit of product ID 123 and one unit of product ID 456, my order would be counted (because it contained product ID 123), and my whole order (including both product 123 and product 456) would contribute to revenue metrics, unit quantity, etc.

      • When this filter is active, it also applies to add to cart, begin checkout, and view product rate metrics and filters. For example, when this filter is active, the Add to Cart rate is the % of visitors who added at least one target product to cart

  • Z-Score: filter to exclude outlier orders. Each order is assigned a z-score which is the number of standard deviations its net revenue is above the average order value for the store, as of the creation time of the order. For example, a z-score of 3 means that the order is 3 standard deviations above the average for the store. Intelligems must have at least 750 orders in its dataset before it starts assigning z-scores to orders. By default, orders with a z-score >3 are excluded from analytics. You can change this filter on a case-by-case basis from the filters pane, or you can change the default for your store on the settings page.

  • Countries: filter to visitors from specific countries

PreviousSubscriptionsNextStatistical Significance

Last updated 1 month ago

Was this helpful?

Custom Events: If you have set up and associated custom events with an experiment ( for more), you’ll see them show up in this section. A visitor counts towards a custom event if they triggered it at least once. Custom event filters are “ORed” together, i.e., selecting multiple custom events will filter to visitors who triggered any of those events.

When “All Orders” is selected: all eligible orders are included ( for more on how orders are attributed to experiments)

see here
see here