CRM Glossary

What this glossary is for

Most CRM projects ship with two silent failures. First, teams talk past each other because words like attribution, incrementality, or deliverability mean different things in ads versus lifecycle versus data. Second, the stack looks live while the underlying definitions are fuzzy, so segments, triggers, and reports slowly diverge.

This glossary fixes the language layer. Each entry ties a concept to how it shows up in tools you use: Customer.io, Klaviyo, HubSpot, warehouses, CDPs, ESPs, and ad platforms. Where a term touches implementation, the term page points you to the CRM Implementation Playbook 2025 and the CRM Implementation Checklist 2026, plus calculators and planners when economics or warmup matter.

You do not need to read everything. Pick the cluster that matches your current bottleneck, then use the A-Z index when someone drops a term in a meeting and you want the full nuance.

Browse by topic

Measurement and causality. If channel discussions rely more on opinion than evidence, start with marketing attribution, marketing incrementality, and holdout tests. Attribution tells a story from the data you already have. Incrementality and holdouts ask what would have happened without the touchpoint.

Data, events, and activation. If journeys misfire or reporting disagrees with finance, read event tracking, webhooks, ETL, reverse ETL, and identity resolution. These entries connect product behavior to CRM state and warehouse models without hand-waving integrations.

Deliverability and consent. If campaigns land in spam or lists feel toxic, use email deliverability, domain warming, sender reputation, bounce rate, suppression lists, and double opt-in. They read boring until revenue drops because nobody owns the basics.

Lifecycle economics. When you argue about which cohorts or segments deserve budget, customer lifetime value, churn rate, and cohort analysis turn opinions into comparable numbers. Pair them with the CLV Calculator, CAC Payback Calculator, and IP Warmup Planner when you need quick ranges before you commit headcount.

How to use these pages with your team

Share one term page when someone says we should optimize X without defining X. Use the related-term links inside each entry to map dependencies before you change segmentation or spend. If you run Customer.io and want hands-on help aligning data, lifecycle, and deliverability, the CRM Implementation service and Customer.io Certified Partner page describe how I work with teams on exactly that stack.