HockeyStack
HomeLive DemoBook a DemoLogin
  • Getting Started
    • 👋Welcome to the Docs!
    • Product Onboarding
    • HockeyStack Implementation Scope: Reporting Product
  • Release Notes
    • May 5, 2025
    • April 21, 2025
    • April 14, 2025
    • April 7, 2025
    • March 31, 2025
    • March 24, 2025
    • March 14, 2025
    • March 6, 2025
    • February 28, 2025
    • February 17, 2025
  • Guides
    • ❓FAQ
      • Merging in HockeyStack
      • Why has my data changed?
      • Viewing form submissions by page
      • A touchpoint's influence on conversion rates
      • Average number of touchpoints
      • Self-reported attribution
      • Trend of Engagement Score
      • How do I see which individuals / companies are included in a metric?
      • What touchpoints get credit in attribution?
      • What object/integration is this field pulling from?
      • What is "Source"?
      • What is "UTM Source"?
      • What is "UTM Medium"?
      • What is an Action?
      • How can I add Salesforce Task object into Defined Properties?
      • How can I track offline events in HubSpot?
      • How can I use LinkedIn Impressions and Engagements in my reports?
      • Measuring sales and marketing penetration in an account list
      • Measuring number of engaged contacts per company
      • Offline conversions for ad platforms
      • Tracking progression on targets
      • Building a Campaign / Asset Grouping property
      • Percentage of high quality job titles by Channel
      • Measuring conversion rates
      • Building a goal that shows open opportunities
      • Number report: Funnel stages influenced by different types of marketing touchpoints
      • Best Practices for Lifecycle Tracking in Salesforce / HubSpot
      • Adding HubSpot form fills to defined properties
      • Does HockeyStack website pixel track US States?
      • Measuring Time Between Two Goals in HockeyStack
      • What is the HubSpot "email bounces" action?
      • Hiding Fields from your CRM in HockeyStack
      • How long does it take for a relation mapping to be ready to use?
      • Can I integrate multiple LinkedIn ads accounts?
      • Can I use Zapier for integrations with HockeyStack?
      • I created a new field in Salesforce (SFDC), but I don’t see it in HockeyStack. What should I do?
      • Using two similar fields in one breakdown
      • Why can't I map back to property?
      • GA4 vs. HockeyStack Website Data Tracking
      • How does HockeyStack deduplicate accounts?
      • How do Table Totals Work: Campaign vs Campaign Group?
      • Can I create one field that calculates the total ad spend + SFDC campaign spend?
      • HubSpot: Can I filter a goal on X object by Y object fields?
      • LinkedIn Impressions: Different Ways of Measuring
      • How to define Engaged Accounts and Engaged People?
      • Building a Campaign Grouping property
    • 🖥️Dashboard Building Guides
      • Business Overview Dashboard
      • CMO Dashboard
      • Website Analytics Dashboard
      • Paid Ads Dashboard
      • Google Ads Dashboard
      • LinkedIn Ads Dashboard
      • In-Person Events
      • ABM Live-Demo
      • Content/Organic Dashboard
      • Dashboards from Labs Reports
        • LinkedIn Ads Benchmarks
        • Google Ads Benchmarks
        • Q1 2024 Recap
        • G2 Impact 2024 Report
        • Website Benchmarks
  • Documentation
    • The HockeyStack Data Model
    • 🎯Goals
      • Funnel Stages Goals
      • Form Fill Goals
      • Page View Goals
      • Click Goals
      • Finding Out a Button's CSS Selector
      • Goals on the Task Object
      • Building an All Touchpoints (Channel) Goal
    • Defined Properties
    • Track Date Properties
    • 📊Reports
      • Building a Basic Report
      • Journeys Use Cases
      • Customer Touchpoint Hierarchy
      • Sequences
      • Lift Reports
      • Lift Analysis vs. Multi-Touch Attribution
      • Types of report filters and when to use them
      • Attribution Models
      • Attribution Lookback
      • Defining Custom Attribution Weights
      • Importing a Google Sheet to use as a Goal Column
      • Advanced Attribution Models
    • 🖥️Dashboards
    • Dashboard Filters
      • When to use AND vs. OR logic?
      • Using Regex
    • 🌠Journeys
      • Syncing journeys to CRM and Slack
    • 🥇Golden Paths
    • Funnels
    • Attribution Funnel
    • 👥Segments
    • ⚙️Settings
      • Account Reset Guide
      • Auto-tagging of URLs
      • Data Categorization in HockeyStack
      • Team Sharing
      • Tracking Multiple Domains
      • Excluding Users
      • Reporting Configuration
      • Multi-Factor Authentication
    • Advanced Data Connections
      • Account List Import
      • Property Relation Mappings
      • Sync Spend
      • Syncing spend from offline channels and campaigns
    • 🔃Audience Syncs
    • Send View updates to Webhooks
    • Odin AI
      • HockeyStack AI: Security, Privacy, and Responsible Use
  • DataSyncs
    • Connecting your Warehouse
      • Authenticate Snowflake
      • Authenticate Google Sheets
      • Authenticate BigQuery
      • Authenticate S3
        • Use an S3 User
        • Use an IAM Role
    • Configure a DataSync Import
    • Configure a DataSync Export
      • Data Export Schema
        • Raw Actions Export Schema
  • Integrations
    • Website Tracker
      • Google Tag Manager
      • WordPress
      • React
      • Troubleshooting
      • Reverting to Cookie-Based Tracking
      • Identifying Users
      • Tracking Custom Goals
    • Ad Platforms
      • LinkedIn Ads
      • Bing Ads
      • Capterra Ads
      • Google Ads
      • Facebook Ads
      • Tiktok Ads
      • Twitter Ads
      • StackAdapt Ads
      • Reddit Ads
      • AdRoll Ads
    • Analytics & Data Warehouse
      • Snowflake
      • Amazon Redshift
      • Google Bigquery
      • Amazon S3
      • Azure Databricks
    • CRMs
      • Salesforce
        • Properties Pulled from Salesforce
        • Salesforce Pulled Objects List
        • Sending Data to Salesforce
      • HubSpot
        • HubSpot Pulled Objects List
    • SSO
      • Azure AD
      • Google Workspace
      • Okta
    • ABM
      • Qualified
      • 6sense
      • Demandbase
      • Clearbit
      • Rollworks
      • G2 Intent
      • Stackadapt
    • Marketing Automation
      • Marketo
        • How to Find Your Marketo Account Details
        • Marketo Pulled Objects List
      • Pardot
      • HubSpot
        • HubSpot Pulled Objects List
    • Other Integrations
      • Calendly
      • Drift
      • Okta
      • Segment
      • Customer.io
  • Setting up your Data for import
    • Import Custom Actions
    • Import Website Actions
    • Import Properties
    • Import Metadata
  • Technical Details
    • ↖️Website Tracking
      • How Website Tracking Works
      • Cookieless Tracking
      • Bot Traffic
      • Privacy Policy
      • GDPR Compliance
    • ⚙️Data Processing from Integrations
    • 🧮Data Cleaning
  • Account Intelligence
    • ☕Getting Started
      • HockeyStack Implementation Scope: Account Intelligence Product
      • Salesforce
        • Salesforce Permissions
        • Salesforce iFrame Installation
        • Salesforce Sync Fields
    • 🏗️Workflows
      • Creating a Workflow
      • List of Workflows
      • Starter Workflow
      • Recurring Workflow Runs
      • Nodes
        • Transformations
          • Condition
          • AI for Accounts
          • Contact Discovery
          • Contact Enrichment
          • Branching
        • Destinations
          • Salesforce
          • HubSpot
          • Outreach
          • StackAdapt
          • Salesloft
          • LinkedIn
          • Pardot
    • 👀Views
      • Create a New View
    • 🔢Scoring
      • Data
Powered by GitBook
On this page
  • Steps on the sequence
  • Breakdown step
  • Time range step(s)
  • Metric to analyze
  • Filter
  • Common Use Cases
  • Influence
  • Conversion Rate
  • Cohort Analysis
  • Lift
  1. Documentation
  2. 📊Reports

Sequences

PreviousCustomer Touchpoint HierarchyNextLift Reports

Last updated 4 months ago

Using sequences in reports allows you to be even more flexible with how you define the data in your reports.

To start, click on “A sequence of actions”.

Here, we have 3 options:

  • Adding & changing steps on the sequence

  • Changing the breakdown step

  • Changing the time range step(s)

Steps on the sequence

Whichever step you select on the sequence, HockeyStack will try to find the first possible action that fits the sequence. Imagine the below journey:

(1) LinkedIn Ads Visit → (2) Google Ads Visit → (3) LinkedIn Ads Visit → (4) Deal Created → (5) Google Ads Visit → (6) Deal Created

If you selected a sequence of LinkedIn Ads Visit → Google Ads Visit → Deal Created, actions 1, 2, and 4 would be selected (provided it fits the time range, which we get to later in this guide).

Whether or not actions are grouped at the individual or the company level depends on what metric you select.

If you select Unique Users, actions will be grouped at the individual level. If you select Companies, actions will be grouped at the company level (meaning if the actions in the sequence came from different individuals, it will still count in the sequence), and actions that are not tied to a company will be disregarded. If you select any other option, actions will be grouped at the company level if possible, but actions that are not tied to a company will still be grouped at the individual level.

Note: “Tied to a company” in this case is not related to the company-contact associations in your CRM. HockeyStack has different methods for tying every possible related contact to a company. An example is, if a Lead in Salesforce has a business email that matches the domain of an Account, it will be tied to the company in HockeyStack.

Breakdown step

You are required to select a single breakdown step for every sequence. This is, by default, the first step.

The breakdown step is used to understand which action should be used as the breakdown for that datapoint.

Imagine a sequence of LinkedIn Ad Impressions → Deal Created, with the report breakdown being Date. In this case, if we selected LinkedIn Ad Impressions as the breakdown step, the data would be tied to the Date of the LinkedIn Ad Impressions. And if we selected Deal Created as the breakdown step, it would be tied to the Date of Deal Created.

In a line chart, the breakdown is inherently selected as “Date”, so you should always be mindful of which breakdown step you select when using a sequence in a line chart.

For attribution, since the breakdown determines what attribution touchpoints there will be, the sequence breakdown step also determines what attribution touchpoints there will be. Only touchpoints before the selected breakdown step will be included.

Time range step(s)

You are required to select at least one time range step for every sequence, but you can also select multiple. This is, by default, the last step. The selected step(s) influence which step will be filtered by the report date range.

Metric to analyze

The metric dropdown applies to the last step of the sequence.

Filter

The filter next to the metric dropdown applies to the last step of the sequence.

Common Use Cases

Influence

Sequences can be used to create reports of “X-Influenced Y”. For example, to create a report of “Blog Influenced MQLs”, you just have to create a sequence of Blog Visits → MQLs. This will capture all MQLs that had Blog Visits before converting.

Conversion Rate

Conversion rates should use sequences. Very commonly, companies have complex buying stages with skippable steps. There may be SQLs that never were MQLs. In this case, if you were to create a conversion rate report from MQL → SQL, if you don’t use sequences, you’ll get MQL-skipped SQLs also included in your report.

All conversion rates should look like below:

Cohort Analysis

Cohort Analysis refers to the practice of separating all data into cohorts of individuals/companies and tracking the same metric for each cohort. In this case, cohort analysis refers to separating individuals/companies by the date they performed an action.

To visualize more clearly, imagine a sequence of Sales Accepted Lead (SAL) → Opportunity, divided by the number of SALs. This signifies the conversion rate from SAL → Opportunity.

If we were to put this on a line chart (which means our breakdown is Date), and selected SALs as our breakdown step, we would be looking at a report of “Cohorted SAL → Opportunity Conversion Rate”. This means, for each date range of the line chart, we would be looking at SALs in that date range, and the Opportunities created any time after that date range.

If, instead, we used Opportunity as our breakdown step, we would be looking at any Opportunity generated in a given date range, regardless of when the SAL happened. The SAL might be created 3 years ago, but it will be counted in the date range of when the Opportunity was generated. When you divide this by SALs, which will be in that same date range, you aren’t really looking at the conversion rate, but more so looking at the division of two unrelated numbers in a date range.

Cohorted approach (recommended) Absolute number approach

The caveat to this, is that your numbers will skew lower at the later ends of a cohorted conversion rate report, because some of the conversions will not have happened yet. If you have a 4-month average sales cycle, for example, numbers for the last 4 months will be lower than the previous numbers.

Lift

Learn more about Lift Reports before continuing.

Sequences can be used both to create lift reports with the Lift report type, and to create lift reports manually using any other report type.

When using the Lift report type and defining your conversion rate, you need to use a sequence. (Refer to the “Conversion Rate” section above, and the Lift Reports doc).

When using other report types to manually create lift reports, you need to prepend a step to the sequence signifying your cohort.

Let’s unpack that.

The lift report models the impact of an action on a certain conversion rate. Let’s say the action is “LinkedIn Ad Visits” and the conversion rate is MQL → SQL. We call the users who have done LinkedIn Ad Visits our “cohort”, and the users who have not done LinkedIn Ad Visits our “anti-cohort”. Then, we draw the conversion rate in the cohort after the LinkedIn Ad Visit, and the conversion rate in the anti-cohort, and compare the two numbers. Here’s how you define both:

  • Cohort: LinkedIn Ad Visits → MQL → SQL sequence, divided by the LinkedIn Ad Visits → MQL sequence. This shows the conversion rate from MQL → SQL when there is a LinkedIn Ad Visit prior to the MQL action.

  • Anti-cohort: MQL → SQL sequence, divided by MQL, with a filter for “Users who have not done LinkedIn Ad Visits”. This shows the conversion rate from MQL → SQL when there isn’t a LinkedIn Ad Visit.

The Lift report type shows the number (Cohort conversion rate - Anti-cohort conversion rate) / Anti-cohort conversion rate as the lift percentage.

All touchpoints before the first Linkedin Ad Impression.
All touchpoints before the first Deal Created after any LinkedIn Ad Impression.
Cohorted approach (recommended)
Absolute number approach