# Intent data > Understand intent data in SaaS marketing: a plain-language definition, a worked example, common mistakes and practical next steps. Source: https://saas-marketing.net/glossary/intent-data/ Topic: SaaS Demand Generation Type: glossary Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/glossary/intent-data/ ## Short answer Intent data consists of signals interpreted as evidence that a person or account may be researching a topic or preparing to buy. Signals can come from owned properties, product activity or external providers. ## Key takeaways - Check signal freshness, collection permissions, account matching and false positives. Test whether it improves opportunity quality beyond existing first-party evidence. - An account-level signal is often mistaken for knowledge of a specific person's needs or permission to contact them. - Use the definition consistently across your marketing, product and sales discussions. --- This concept sits within [saas demand generation](/saas-demand-generation/). Use the definition above to align terminology before comparing reports or planning work. ## A SaaS example An account repeatedly visits implementation and pricing pages. That behavior can justify a closer fit review, but it does not establish budget or purchase authority. This is an illustrative scenario, not a reported result from a customer study. The point is to show the meaning of the term and the decision it affects. ## The mistake to avoid An account-level signal is often mistaken for knowledge of a specific person's needs or permission to contact them. ## Put the definition to work Check signal freshness, collection permissions, account matching and false positives. Test whether it improves opportunity quality beyond existing first-party evidence. When adding the term to a brief or dashboard, write down the scope and the evidence the team will use. Assign an owner for the definition so it does not change quietly between reporting periods. If two teams use the same label differently, resolve that difference before combining their numbers or handing work between them. ## Related reading - [Demand creation vs demand capture](/guides/demand-creation-vs-demand-capture/) - [B2B SaaS demand generation strategy](/guides/b2b-saas-demand-generation-strategy/) - [Demand generation for SaaS startups](/guides/demand-generation-for-saas-startups/) - [The 90 day demand generation plan](/playbooks/saas-demand-generation-90-day-plan/) Browse the [full glossary](/glossary/) for adjacent definitions and the [resource library](/resources/) for working materials. {/* expanded-practice-2026-09 */} ## Apply intent data in a working review Start by explaining the term without repeating its label. Then point to an observable example and a counterexample. If it is a metric, write the unit, numerator, denominator and time window. If it is a role, process or strategy, identify the responsibility or decision that distinguishes it from adjacent terms. This prevents a shared word from concealing different operating assumptions. For this topic, involve the campaign owner and the team receiving requested follow-up and work from the audience hypothesis, offer and campaign handoff. The relevant unit is an eligible participant or buying account. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare Keep education, engagement and purchase intent separate. A useful campaign can help someone understand a problem without creating an immediate opportunity. Define the learning objective and the commercial next step independently so the program can be evaluated without inflating either. | Review field | What to record | | --- | --- | | Topic | Intent data | | Decision | The specific action this explanation should help you choose | | Working evidence | the audience hypothesis, offer and campaign handoff | | Unit and scope | an eligible participant or buying account | | Responsible people | campaign owner and the team receiving requested follow-up | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When community engagement comes from the wrong audience A broad founder community can be valuable while still being an unsuitable primary channel for a specialized enterprise operations product. Use this check: Review participant needs and compare them with the intended customer problem. Do not exclude useful non-buyers solely to make lead metrics look stronger. The [focused diagnostic guide](/guides/community-engagement-does-not-fit-the-market/) provides the correction process and a working evidence sheet. #### When demand campaigns reach sales without context Someone attending a pricing workshop may want research guidance rather than a demo of every product feature. Use this check: Inspect the handoff record for the campaign topic, participant action and stated question. Do not turn inferred interest into a fabricated statement from the prospect. The [focused diagnostic guide](/guides/demand-campaign-has-no-sales-context/) provides the correction process and a working evidence sheet. ### Record the decision and the limit A workshop attendee who completes an exercise has received a useful outcome. An attendee who asks for a tailored evaluation has taken a different step. The handoff should preserve that distinction instead of sending the same aggressive follow-up to everyone. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-demand-generation/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### What does intent data mean? Intent data consists of signals interpreted as evidence that a person or account may be researching a topic or preparing to buy. Signals can come from owned properties, product activity or external providers. ### What is an example of intent data? Illustrative example: An account repeatedly visits implementation and pricing pages. That behavior can justify a closer fit review, but it does not establish budget or purchase authority. ### What mistake should teams avoid with intent data? An account-level signal is often mistaken for knowledge of a specific person's needs or permission to contact them. ### How should a SaaS team apply this concept? Check signal freshness, collection permissions, account matching and false positives. Test whether it improves opportunity quality beyond existing first-party evidence.