Mapping the SaaS data landscape: sources, systems, and owners

Why source mapping matters before you touch a dashboard

Most SaaS "data problems" are not analytics problems. They are ownership problems. A churn number looks wrong not because the SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition → is bad, but because billing defines "customer" as an active subscription while product defines it as a logged-in workspace.

A source map is a simple artifact: for each dataset, who owns it, where it lives, what it's used for, and what breaks it. Before building metrics, build this mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition →. It prevents the single most common failure mode in SaaS analytics: two teams presenting different numbers for "the same" metric in the same board meeting.

The five core data sources in SaaS

1. Product telemetry (usage data)

This is event-level data: logins, clicks, feature adoption, APIAPIApplication Programming Interface: a standardised interface that lets applications communicate and exchange data without knowing each other's internal workings.View full definition → calls, session length. Captured via instrumentation tools like Amplitude, Mixpanel, or Segment (a customer data platformcustomer data platformA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition →, CDPCDPA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition →, that routes events to multiple destinations).

• Owner: typically Product or Data Engineering.
• Typical breakage: instrumentation drift. A developer renames an event ("signup_complete" becomes "user_created") and three months of trend lines silently break. No error is thrown, the data just quietly means something different.
• Grain: usually event-level, timestamped, tied to a user ID or account ID.

2. Billing and subscription data

Lives in systems like Stripe, Chargebee, or Zuora. This is the system of record for MRRMRRMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition → (monthly recurring revenuemonthly recurring revenueMonthly Recurring Revenue: the predictable, normalized monthly revenue from active subscriptions, the baseline metric for SaaS and subscription businesses.View full definition →), plan tier, seat count, discounts, and payment status.

• Owner: Finance, sometimes RevOps.
• Typical breakage: mismatched customer identity across billing and CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → (a company renamed in Salesforce but not in Stripe), and manual discounting that doesn't flow back into reporting systems.
• Grain: account/subscription level, usually monthly or event-triggered (upgrade, downgrade, cancellation).

3. CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → data (customer relationship managementcustomer relationship managementCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition →)

Salesforce or HubSpot records: leads, opportunities, deal stages, contract terms, renewal dates. This is the sales-side narrative of the customer.

• Owner: Sales Ops / RevOps.
• Typical breakage: stale or manually-entered fields. A rep forgets to update deal stage; forecasts built on CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → data become unreliable. Also duplicate account records when multiple reps create separate entries for the same company.

4. Support and success data

Zendesk, Intercom, or Gainsight tickets, NPSNPSNet Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend a brand, then subtracting detractors from promoters.View full definition → (Net Promoter ScoreNet Promoter ScoreNet Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend a brand, then subtracting detractors from promoters.View full definition →) surveys, health scores. This captures customer sentiment and friction.

• Owner: Customer Success / Support.
• Typical breakage: health scores built on stale usage snapshots, or ticket volume conflated with dissatisfaction (a power user files many tickets because they use the product heavily, not because they're unhappy).

5. Marketing and acquisition data

Ad platforms (Google Ads, LinkedIn), web analytics (GA4), and attributionattributionA framework for assigning credit to the touchpoints that contributed to a conversion, so you can measure which channels and interactions actually drive results.View full definition → tools. Captures CACCACCustomer Acquisition Cost (CAC) is the total sales and marketing spend divided by the number of new customers gained in a period. It measures how efficiently you grow.View full definition → (customer acquisition costcustomer acquisition costCustomer Acquisition Cost (CAC) is the total sales and marketing spend divided by the number of new customers gained in a period. It measures how efficiently you grow.View full definition →) inputs: spend, channel, campaign, conversion.

• Owner: Marketing / Growth.
• Typical breakage: attribution modelattribution modelA framework for assigning credit to the touchpoints that contributed to a conversion, so you can measure which channels and interactions actually drive results.View full definition → disagreements (last-touch vs. multi-touch), and cookie/consent restrictions under GDPR (General Data Protection Regulation, the EU's data privacy law) or CCPA (California Consumer Privacy Act) that shrink trackable traffic, especially in Europe post-2018 and increasingly in the US since 2020.

Building the source mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition →: a practical template

A usable source mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → has five columns. Here's a compressed example:

| Dataset | System | Owner | Grain | Common failure |

|---|---|---|---|---|

| Product events | Amplitude/Segment | Product Eng | Event-level | Renamed/untracked events |

| Subscriptions | Stripe/Chargebee | Finance | Account-level | ID mismatch with CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → |

| Deals/accounts | Salesforce | RevOps | Account-level | Manual entry, duplicates |

| Tickets/health | Zendesk/Gainsight | CS | Ticket-level | Stale scores, sentiment conflation |

| Campaigns/spend | GA4/Ad platforms | Marketing | Session/campaign | Attribution modelAttribution modelA framework for assigning credit to the touchpoints that contributed to a conversion, so you can measure which channels and interactions actually drive results.View full definition → conflict, consent gaps |

The critical column most teams skip is "common failure." Naming the failure mode in advance is what lets you build monitoring for it, rather than discovering it during a board review.

The identity resolution problem

The reason these five systems don't naturally agree: each uses a different key.

• Product telemetry keys on a device or user ID.
• Billing keys on an account/subscription ID.
• CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → keys on a company/contact record.

Reconciling these is called identity resolution, and it's usually done through a customer ID mapping table maintained in the data warehousedata warehouseA central repository that consolidates data from many source systems into a structured, query-optimized store designed for analytics, reporting, and business intelligence.View full definition → (Snowflake, BigQuery, Databricks are the common platforms in 2026).

A simplified mapping query looks like this:

If product_account_id and crm_account_id don't reliably mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → 1:1, every usage-based churn or expansion metric downstream is suspect. This join failing silently is one of the most common root causes of "the dashboard numbers don't match" incidents in SaaS companies.

For a deeper technical reference on building this kind of pipelinepipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.View full definition → discipline, the dbt Labs glossary is a solid, free primer on analytics engineering concepts referenced throughout this module.

Who owns what: a governance reality check

Ownership disputes are the norm, not the exception, in SaaS data. A few patterns worth knowing:

• Product-led growth (PLG) companies (Notion, Figma-style motion) tend to have Product own the most authoritative customer definition, since usage drives the business. Billing is often downstream and thinner.
• Sales-led enterprise SaaS (traditional Salesforce-style motion) tends to have CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → as the "source of truth" for account identity, with product telemetry treated as supplementary.
• Data governance councils, common at scale (Series C+ or public companies), formalize this by assigning a data stewarddata stewardA business-side owner responsible for the quality, consistency and appropriate use of data in their domain.View full definition → per domain: a named person accountable for definitions, not just data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition → tooling.

Governance frameworks worth knowing by name: the DAMA-DMBOK (Data Management Body of Knowledge) is the standard reference framework for data governancedata governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.View full definition → roles and responsibilities, useful if you want a formal vocabulary for these ownership conversations.

🎬 [VIDEO: "Data GovernanceData GovernanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.View full definition → Explained" - youtube.com - search for recent DAMA or Data Council talks explaining stewardship and ownership models in modern SaaS data stacks]

Where this breaks in practice: three real patterns

1. The renamed event. Engineering ships a refactor, renames trial_started to trial_activated. Growth's activation dashboard flatlines. Nobody notices for two weeks because no alert was tied to that event's volume.

2. The billing/CRM identity drift. A customer is acquired by another company, renamed in Salesforce, but the Stripe account still shows the old legal name. Revenue reporting by "customer" undercounts the true logo count.

3. The attribution war. Marketing reports CACCACCustomer Acquisition Cost (CAC) is the total sales and marketing spend divided by the number of new customers gained in a period. It measures how efficiently you grow.View full definition → using last-touch attributionattributionA framework for assigning credit to the touchpoints that contributed to a conversion, so you can measure which channels and interactions actually drive results.View full definition →; Finance reports CACCACCustomer Acquisition Cost (CAC) is the total sales and marketing spend divided by the number of new customers gained in a period. It measures how efficiently you grow.View full definition → using fully-loaded spend divided by new logos. Both are "correct" by their own definition. Without a documented source , this becomes a recurring, unproductive argument rather than a five-minute reconciliation.

Key Takeaways

• SaaS data comes from five core systems: product telemetry, billing, CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition →, support/success, and marketing. Each has a distinct owner, grain, and typical failure mode.
• Build a source mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → (dataset, system, owner, grain, common failure) before building metrics. It's the fastest way to prevent conflicting numbers in leadership meetings.
• Identity resolution, reconciling different ID schemes across systems, is the single most common root cause of "the numbers don't match" incidents.
• Ownership follows business model: PLG companies anchor on product data, sales-led companies anchor on CRM data. Know which model you're in before deciding whose number is authoritative.