Mari Luukkainen

Main

  • Home
  • Blog
  • Projects
  • About
  • Work with me
  • Resources
  • Now
  • Frameworks
  • GTM30
  • Strategic Growth Hacking

Account

XGitHubLinkedInEmail
  1. Home
  2. /Frameworks
  3. /GTM30
  4. /Glossary
  5. /Intent level

Intent level

A shared signal of how close someone is to action (low/medium/high), inferred from patterns like page types viewed, depth, and CTA behavior — used for routing and prioritization.

Last updated: December 12, 2025

Definition

A shared signal of how close someone is to action (low/medium/high), inferred from patterns like page types viewed, depth, and CTA behavior — used for routing and prioritization.

In practice

  • Infer intent from coherent patterns (entity + page type + depth + CTA), not from one click.
  • Treat intent as a shared field that powers both GTM routing and content prioritization.

Common mistakes

  • Using one-off heuristics hidden in a single tool (sales automation vs analytics disagree).
  • Confusing curiosity with purchase intent when someone is still in exploration mode.

Related terms

  • Programmatic content (in GTM30) — A structured system (not a pile of long-tail pages) that turns your website into: a discoverability layer, a single source of truth for your narrative, and a data layer for automation, CRM, and LLMs.
  • Entity model — A small, stable set of entities (problems, use cases, roles/personas, industries, etc.) and their fields/relationships that power content, analytics, automation, and LLM retrieval.
  • Signal schema — A minimal, consistent set of fields for capturing signals so Product, Sales, and Support can act without losing context (source, ICP segment, lifecycle stage, tags, severity, status, and link).
  • Lifecycle stage — Where a customer is in their journey (e.g. awareness → evaluation → activation → retention), used as a shared field to align content, sales plays, and support responses.
  • Traits — Machine-readable tags derived from page views and behavior (tied to entities) that feed analytics, automation, and CRM without manual interpretation.

Related GTM30 pages

  • Events and traits
← Back to glossary← Back to GTM30