# The SaaS Marketing Analytics Stack

> The six layers from event capture to board dashboard, what to buy at each ARR band, and why warehouse native reporting beats a pile of disconnected tools.

Source: https://saas-marketing.net/guides/saas-marketing-analytics-stack/
Topic: SaaS Metrics and Analytics
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-marketing-analytics-stack/

## Short answer

A SaaS marketing analytics stack has six layers: event capture, collection and CDP, warehouse, transformation, activation and presentation. Typical choices are Segment or RudderStack for collection, Fivetran for extraction, Snowflake or BigQuery for storage, dbt for transformation, Hightouch for reverse ETL and Looker or Metabase for presentation. Build the warehouse and identity spine before buying an attribution product, because every downstream tool inherits the definition problems left upstream.

## Key takeaways

- Six layers: capture, collection and CDP, warehouse, transformation, activation, presentation. Skipping transformation is why dashboards disagree.
- Lead to account matching is the layer that breaks most often and the one nobody assigns an owner to.
- Under 3 million dollars ARR you do not need a warehouse, you need a tracking plan and one source of truth.
- A working stack at 3 to 20 million dollars ARR costs roughly 40,000 to 90,000 dollars a year in tooling.
- Buy attribution software after the warehouse, never before, or you buy an opinion layer on broken data.
- You can produce trustworthy reportable numbers in 60 days if you build in the right order.

---

Every marketing team has the same argument eventually. The CRM says 62 opportunities came from content, the ad platform claims 41, product analytics shows a different signup count entirely, and the board deck picks whichever number is kindest. That argument is an architecture problem, not a reporting problem. This is how the data physically travels from a click to a board slide, what to buy at each stage, and the order to build it in.

## What are the six layers of a marketing analytics stack?

Six layers, each with a distinct job. Most companies buy tools for layers one and six and leave the middle four to chance, which is exactly where the disagreements come from.

| Layer | Job | Common tools | Skipping it causes |
| --- | --- | --- | --- |
| Capture | Record events with consistent names | Segment SDKs, native product events | Untrackable or duplicated events |
| Collection and CDP | Route events to destinations, resolve identity | Segment, RudderStack | Every tool sees a different subset |
| Warehouse | Store everything queryable in one place | Snowflake, BigQuery, Redshift | No adjudication between sources |
| Transformation | Turn raw tables into defined metrics | dbt | Each dashboard invents its own logic |
| Activation | Push defined data back into tools | Hightouch, Census | Insight that never reaches a campaign |
| Presentation | Show the numbers to humans | Looker, Metabase, Omni | Nobody uses the work |

Transformation is the layer teams skip most and the one that causes the disagreement they complain about. When "marketing qualified account" is defined in a dbt model, there is one definition. When it is defined in three dashboards, there are three, and they drift within weeks of anyone changing a filter.

Buying Looker before you have a transformation layer gives you a beautiful interface onto ambiguous numbers. Buying an attribution product before your identity spine holds gives you confident answers derived from broken joins. Downstream tools always inherit upstream problems, and they present them with more authority.

## What should you buy at each ARR band?

Three bands, three quite different answers. Building the 20 million dollar stack at 2 million dollars ARR is a common and expensive mistake, usually made by a first analytics hire who wants the architecture they had at their last job.

Under 3 million dollars ARR, the highest return investment is not a tool at all. It is a written tracking plan that says what every event is called, when it fires and what properties it carries. The [marketing tracking plan template](/templates/marketing-tracking-plan/) is genuinely the cheapest thing on this page and prevents the most expensive problem.

Between 3 and 20 million, the stack above is close to a default, and the debate worth having is BigQuery versus Snowflake. BigQuery is cheaper to start and easier if you are already in Google Cloud. Snowflake is easier to govern as more teams start querying. Either is fine; changing your mind in year three is not.

## Why does the identity spine break, and who owns it?

Four identifiers have to chain together: anonymous ID from the first visit, user ID once someone logs in, account ID in the product, and the CRM record ID. Every question you care about, from which content produced pipeline to which campaign touched an expansion, depends on that chain holding end to end.

Three points of failure, in order of how often I see them.

Anonymous to user stitching fails when someone reads three blog posts on mobile, signs up on desktop, and your CDP treats them as two people. Partially solvable with identity resolution in the CDP, never fully solvable, and worth knowing the error rate rather than pretending it is zero.

Lead to account matching is the worst one. A person signs up with a personal Gmail address, or the company is Example Company in your CRM and Example Companyoration in the signup form, or the enterprise has fourteen domains. Untreated match rates commonly sit between 60 and 80 percent, which means a fifth of your pipeline is invisible to any content attribution you run. Fix it with a domain mapping table you maintain deliberately, plus an enrichment provider, plus a monthly exception review.

CRM to warehouse sync breaks quietly when someone adds a custom field and nobody updates the pipeline. Schema change alerts solve this in an afternoon and almost nobody sets them up.

**60% to 80%** Typical lead to account match rate before deliberate remediation

Name an owner for the identity spine. Not a team, a person. This is the single most influential governance decision in the whole stack, because unowned joins degrade silently and you only discover it during a board prep at 11pm.

## What does reverse ETL actually unlock for marketing?

It closes the loop between product behaviour and campaigns, which is the thing marketing automation platforms have promised for a decade and never delivered on their own.

Concrete plays that need it:

- Accounts whose weekly active users dropped more than 40 percent over 30 days, synced to a CS alert and a re-engagement sequence.
- Warehouse computed product qualified lead scores pushed into Salesforce so sellers see them next to the record.
- Customers using two of five modules, synced to an expansion campaign for the third.
- Suppression lists built from actual product usage rather than an email platform's stale tags.

Each of those requires a metric defined once in dbt and delivered wherever it is needed, which is the entire argument for [warehouse native marketing](/guides/warehouse-native-marketing-stack/). The alternative is a marketing ops person exporting CSVs on Friday afternoons, which works until they take a holiday. These plays are also the mechanism behind most of the [expansion levers that move NRR](/playbooks/nrr-expansion-levers/).

## What build order produces numbers in 60 days?

This sequence assumes one competent analytics engineer or a good fractional partner, and it produces defensible numbers before the quarter ends.

**Sixty day build order**

The discipline that makes this work is limiting scope. Ten metrics, one dashboard. Teams that try to model everything in the first quarter ship nothing usable in the first year, and the credibility cost of that is hard to recover.

## Where should attribution sit in all this?

Last, and possibly nowhere. An attribution product applies a model to data you already own. If your capture is inconsistent and your account matching sits at 70 percent, the tool will produce a confident number derived from broken joins, and it will be believed because it came from a specialist tool with a nice interface.

Build the warehouse first, then decide. Plenty of teams find that once they have clean first touch, last touch and full path views in dbt plus a self reported attribution field on the demo form, the dedicated product adds a model preference rather than information. That is a legitimate purchase, just a much smaller one than the category's pricing implies.

Whatever you conclude, report multiple views to the board rather than one. First touch, last touch, and self reported, side by side, with the disagreement visible. Executives trust a range with an honest error bar more than a single number they suspect was chosen. The [board reporting playbook](/playbooks/board-reporting-for-saas-cmos/) covers how to present that without losing the room.

## What this costs beyond the tools

The uncomfortable part. Tooling is the cheap half. An analytics engineer costs 130,000 to 180,000 dollars in the US, and without one the stack decays: pipelines break, definitions drift, and within nine months you are back to arguing about whose number is right while paying 60,000 dollars a year for the privilege.

Two more honest limits. A warehouse does not make attribution true, it makes it consistent, and consistency is worth a great deal but it is not causality. And self service analytics is largely a myth in marketing teams under about 50 people. Someone will still build the queries. Plan for that person rather than budgeting for a tool that promises to remove them.

## Start with an audit, not a purchase

Before buying anything, run the [marketing analytics audit checklist](/checklists/marketing-analytics-audit/) and write down your current lead to account match rate. That single number tells you whether your problem is tooling or plumbing, and for most teams it is plumbing.

Then pick the band that matches your ARR and build in the order above. The [marketing analytics platforms](/tools/marketing-analytics-platforms/) roundup compares the presentation layer options, [Mixpanel versus Amplitude](/comparisons/mixpanel-vs-amplitude/) covers the product analytics choice specifically, and the [SaaS marketing dashboard template](/templates/saas-marketing-dashboard/) gives you a starting layout for that one dashboard. The wider [SaaS metrics](/saas-metrics/) hub covers what the numbers should mean once you can trust them.

## Frequently asked questions

### What is a marketing analytics stack in B2B SaaS?

It is the chain of systems that carries data from a user action to a number on a slide. Capture records events, collection routes them, a warehouse stores them, transformation turns raw tables into defined metrics, activation pushes those back into tools, and presentation shows them. Most teams own tools at the ends of the chain and nothing in the middle, which is why their numbers disagree.

### Do you need a data warehouse for marketing analytics?

Above roughly 3 million dollars ARR, yes. Below that a well maintained CRM plus product analytics will answer most questions faster and cheaper. The signal that you need a warehouse is when two teams present different numbers for the same metric and nobody can adjudicate, because that means the definition lives in tool configuration rather than in shared code.

### What is warehouse native marketing analytics?

It means the definitive version of every metric lives in your data warehouse, defined in transformation code, and every tool reads from there rather than calculating its own version. The alternative is each platform reporting its own attributed conversions, which is how you end up with three tools claiming credit for the same 40 opportunities.

### What is reverse ETL and why does marketing need it?

Reverse ETL pushes data from the warehouse back into operational tools such as your CRM, email platform and ad accounts. Marketing needs it to activate product usage: sending a list of accounts whose usage dropped 40 percent into a campaign, or syncing a warehouse computed lead score into Salesforce. Hightouch and Census are the common choices.

### How much does a marketing analytics stack cost?

Under 3 million dollars ARR, 5,000 to 15,000 dollars a year using product analytics and CRM reporting. Between 3 and 20 million, roughly 40,000 to 90,000 dollars a year across collection, warehouse, extraction, transformation and BI. Above 20 million, 120,000 to 400,000 dollars plus at least one analytics engineer, who usually costs more than the entire toolset.

### What is the identity spine in marketing analytics?

It is the chain that links an anonymous visitor ID to a logged in user ID, that user to an account, and that account to a CRM record. Every question about content driving revenue depends on that chain holding. Lead to account matching is the weakest link, especially with personal email addresses and multi domain enterprises, and it needs a named owner and a monthly audit.

### Should you buy an attribution tool?

Not first. An attribution product applies a model to data you already have, so if your event capture is inconsistent and your account matching is 70 percent accurate, the tool produces confident wrong answers. Build capture, warehouse and identity first. After that, an attribution tool is a reasonable purchase, and you may find you no longer need one.