Contact data
Who?
The complete guide to demand intelligence.
A practical guide to signals, audience fit, geography, activation, and revenue feedback—with the limits made explicit.
What deserves action?
Different sources answer different questions. Demand intelligence connects their context around a commercial decision.
Intent data
What activity?
Market data
Where?
Recency
When?
Customer data
What converts?
Demand Intelligence → What deserves action?
Available inputs, permissions, coverage, and measurement determine what can be concluded. The categories can overlap.
What is demand intelligence?
Demand intelligence connects available commercial signals with customer fit, geography, timing, and an activation plan. Its purpose is to help a business decide which audiences or markets deserve attention before acquisition spending begins. It does not turn incomplete observations into certainty about an individual buyer.
Start with a decision: which service area to test, which eligible CRM segment to revisit, or which audience input to evaluate. Define the offer, market, exclusions, and desired outcome. Those choices determine which evidence is relevant. A larger dataset may add little if it does not support the decision.
A useful program produces both an actionable deliverable and an explanation of its limits: what is observed, how recent it is, where coverage exists, and which destinations may use it.
Apply this to your acquisition program ↗How demand intelligence differs from intent data
Intent data describes activity associated with interest or buying consideration. Demand intelligence is a broader operating approach that can use intent data alongside customer history, geographic context, audience processing, and downstream feedback. The two are complementary rather than mutually exclusive categories.
Providers vary. Some intent-data offerings include rich geographic analysis, refreshes, and activation services. Compare actual capabilities instead of assuming that a product label determines its limits. Ask whether the proposed data supports your market, channel, buying cycle, and operational workflow.
For example, research indicators may be useful inputs, but territory assignment also needs serviceability and sales capacity. A complete decision needs both the signal and the conditions under which your team can act.
Apply this to your acquisition program ↗What is a demand signal?
A demand signal is an available observation or inference that may indicate commercial relevance. Examples include authorized website engagement, product comparison activity, category research, a direct inquiry, or aggregate market changes. Their strength depends on context and how they were obtained.
The same behavior can have many explanations. Someone may be researching for work, helping a relative, maintaining a product already owned, or simply learning. Distinguish an explicit request from a modeled inference, and avoid presenting either as a guaranteed purchase.
Document the signal category, source permissions, observation time, geographic scope, and limitations. This record helps your team judge usefulness and prevents a label such as “in-market” from hiding uncertainty.
Apply this to your acquisition program ↗First-party vs external signals
First-party signals come from interactions your business collects through its own authorized relationships and properties. External signals come from sources outside that relationship. A detailed externally sourced record does not become first-party data simply because it has been enriched.
First-party history can explain what a customer requested, when a lead last engaged, and which permissions or exclusions apply. Permitted external context may add another reason to review an eligible segment. Keep provenance visible so that an inferred attribute is not mistaken for a customer statement.
Before combining sources, define the purpose, necessary fields, permitted processing, access, and suppression handling. Start with a scoped segment instead of uploading an entire CRM without a defined use.
Apply this to your acquisition program ↗Signal recency
Recency is the time since a relevant observation occurred. It is different from the date a file was delivered or a record was updated. A recently received record may contain old activity, so observation and delivery timestamps should be understood separately.
There is no universal decay rate. Emergency service needs may move differently from elective projects, vehicle purchases, or long consultation cycles. Repeated engagement can also change the interpretation. Choose the useful window for the offer and signal type rather than applying one rule to every industry.
Review expiration alongside refresh. A monitoring program should remove stale indicators and apply new exclusions, not merely add more records. Compare timing assumptions with actual downstream behavior when appropriate data is available.
Apply this to your acquisition program ↗Identity and audience resolution
Resolution connects appropriate records or attributes into an audience structure where matching is permitted and available. Deterministic methods use agreed identifiers; probabilistic methods estimate connections. Both require clarity about granularity, confidence, and unresolved records.
A household match differs from a person match, and an account-level observation differs from a named decision-maker. Those distinctions affect what your team can say and do. Avoid turning a broad association into an assertion about a specific individual.
Specify the identifiers, deduplication method, missing-data handling, and destination format before delivery. A usable match does not establish channel consent, platform eligibility, or purchase intent.
Apply this to your acquisition program ↗Audience qualification
Qualification applies the program’s inclusion and exclusion rules. Relevant questions include whether the offer fits, whether the business can serve the geography, whether an observation is timely, and whether the intended activation is permitted. These are distinct from a sales team confirming budget or buying authority.
Write the criteria before evaluating the output. Otherwise, the definition can drift toward whatever data happens to be available. Record which conditions are required, which add context, and which cannot be evaluated because fields or coverage are missing.
Review a sample against the written brief. Explain the resulting audience in terms the media or sales team can use, and preserve the distinction between a marketing-relevance hypothesis and a qualified sales opportunity.
Apply this to your acquisition program ↗Demand scoring
Scoring organizes evidence into a relative priority for a defined objective. A program might consider relevance, recency, geographic fit, and usable audience attributes. A score is not automatically a calibrated probability of purchase, and this framework does not claim a universal production scoring system.
Define weights, thresholds, missing inputs, and the comparison population. Avoid counting repeated versions of the same underlying event as independent confirmation. A lack of observed activity may reflect incomplete coverage rather than weak demand.
Evaluate priorities against customer outcomes over appropriate windows. Review whether the ranking adds useful information beyond simpler rules. Explain what the score can support and what decisions it should not determine.
Apply this to your acquisition program ↗Geographic demand intelligence
Geography connects observations with places your organization can serve. It can support local campaigns, sales allocation, franchise planning, or market expansion. Useful units may include ZIP codes, neighborhoods, counties, metros, or business-defined territories.
Raw counts and relative density answer different questions. A larger area may contain more observations because it has more people or better source coverage. Compare consistent category definitions, windows, and denominators before interpreting a concentration as a commercial advantage.
Add operational constraints: route efficiency, branch capacity, territory ownership, and existing customer penetration. Market evidence is most useful when paired with the practical ability to act.
Apply this to your acquisition program ↗Demand Maps
A Demand Map visualizes the location and relative concentration of relevant available signals. It is a planning view, not a certificate that a particular household needs a service or will buy. Geographic precision depends on source coverage and the agreed level of aggregation.
Begin by choosing the decision and appropriate scale. A national comparison and tomorrow’s canvassing route need different levels of detail. Keep the legend, time window, coverage limitations, and distinction between counts and indexes visible.
The website’s interactive demonstration uses simulated data and conceptual boundaries. A real map requires a scoped market, suitable data, and an explanation of how the observations were processed.
Apply this to your acquisition program ↗Audience activation
Activation is the handoff from intelligence into an acquisition workflow. That may mean an eligible advertising audience, a prioritized CRM segment, a direct-mail area, or a field-sales territory brief. The destination determines which identifiers, permissions, and formats are needed.
Confirm eligibility before preparing a file. A source’s license and a platform’s audience requirements are separate conditions. Contact information alone does not create permission for email, SMS, or another outreach channel. Match rates and platform acceptance cannot be assumed.
Assign an owner for delivery, exclusions, updates, and measurement. Document whether the handoff is a file, an agreed integration, or a planning brief rather than implying that every destination has an automatic connector.
Apply this to your acquisition program ↗Paid-media applications
Paid-media teams decide what audience enters a delivery system before a campaign can optimize. Demand intelligence may inform that input or the market strategy around it. Creative, offer, landing pages, follow-up, and platform delivery still influence results.
Choose a testable audience hypothesis and a permitted method. Keep campaign goals and outcome definitions consistent where practical. Review audience overlap and platform expansion behavior so the comparison does not imply that every impression came from the original seed.
Track appointments, qualified opportunities, and customers alongside cost per lead. A lower CPL can coexist with weaker customer economics; a more expensive lead can be worthwhile only if downstream value supports it.
Apply this to your acquisition program ↗Sales applications
Sales teams can use permitted context to prioritize eligible records or serviceable territories. Relevance may help decide where to begin, but it does not justify claiming knowledge of a person’s private activity or bypassing outreach restrictions.
Keep the team’s workflow manageable. Define the queue, information shown to a representative, permitted action, and disposition fields. Distinguish an externally inferred signal from a customer’s own statement so that follow-up remains accurate.
Review opportunities and customer outcomes over a suitable period. Team capacity, follow-up speed, offer fit, and territory differences can influence conversion, so avoid assigning all changes to audience intelligence.
Apply this to your acquisition program ↗CRM applications
Your CRM preserves relationship history, inquiries, customer records, and permissions. Demand intelligence may add current context to eligible records, supporting segmentation, reactivation, expansion review, or suppression of irrelevant groups.
Begin with a clear objective and a bounded segment. Preserve existing opt-outs, source information, and known customer facts. Label inferred attributes and avoid overwriting a declared preference with a modeled prediction. Match confidence and unresolved records should be visible.
Create an action for each segment and an owner for updates. A prioritization field without a defined follow-up process rarely changes the acquisition system. Measure progression into conversations and opportunities where the data allows.
Apply this to your acquisition program ↗Canvassing applications
Field teams need a reason to allocate time to one serviceable area rather than another. Aggregate demand context can support that decision alongside routes, territory ownership, staffing, and local knowledge. A hotspot does not establish a specific household’s intent.
Compare priority areas with suitable baseline areas using a consistent offer and observation window. Record conversations and opportunities at an appropriate geographic level. Weather, accessibility, team experience, and execution can affect results independently of the map.
Use feedback to refine the next territory brief. A map should support field judgment and operational planning, not require representatives to imply they know a homeowner has a particular need.
Apply this to your acquisition program ↗Direct-mail applications
Demand intelligence may help define an eligible audience or serviceable area for a mail program. The available data, address quality, source permissions, suppression requirements, and offer determine whether a household-level audience or broader territory approach is appropriate.
Plan the measurement before sending. Use a defined campaign window and a practical response mechanism, then assess leads and customer outcomes. Consider repeat exposure, other active channels, and unmatched responses when interpreting the result.
A geographic test can compare equivalent areas, but it is still affected by population, coverage, and execution. Do not equate a modeled concentration with confirmed purchase demand or claim individual intent in the mail creative.
Apply this to your acquisition program ↗Demand monitoring
Monitoring revisits a defined market or audience as available signals change. It differs from repeatedly sending the same static file. A useful program includes new observations, expired relevance, changed exclusions, and a clear activation handoff.
Choose cadence according to source availability and the buying cycle. Daily delivery is not automatically more valuable than a less frequent, well-defined refresh. Observation delays and minimum audience requirements may constrain the practical update window.
Agree how updates are reconciled with active campaigns and CRM records. Keep a change history where appropriate so the team can explain which criteria produced a segment and when it was last reviewed.
Apply this to your acquisition program ↗Revenue feedback
Revenue feedback connects downstream customer outcomes with future audience decisions. It can reveal which offers, segments, markets, and workflows produced useful opportunities. It depends on consistent CRM stages, campaign identifiers, customer matching, and a suitable revenue horizon.
Attribution assigns credit under a chosen method; it does not automatically prove incremental revenue. Unmatched conversions, repeat customers, delayed closes, refunds, and other channels can affect interpretation. Separate gross revenue from gross profit and acquisition cost.
Use comparable cohorts and document limitations before changing the next audience brief. Where data is sparse, treat the result as a question to investigate rather than a definitive ranking.
Apply this to your acquisition program ↗Privacy and responsible use
Responsible use begins before data is combined or activated. Define the purpose, permitted source use, necessary fields, appropriate access, destination requirements, and suppression responsibilities. First-party collection also carries obligations; ownership of a CRM is not blanket permission for every use.
Sensitive categories and restricted decisions need particular care. Do not treat marketing relevance as a basis for eligibility, underwriting, employment, housing, or credit decisions. Confirm the specific program and applicable requirements with the responsible business owners.
Agree retention and deletion handling for the actual engagement, including downstream copies. This guide provides operational considerations, not legal advice, a compliance certification, or a guarantee that a proposed use is permitted.
Apply this to your acquisition program ↗Building a demand-intelligence strategy
Start with one business decision and an outcome you can evaluate: a campaign audience, a dormant CRM segment, a field territory, or an expansion market. Define the offer, customer profile, serviceability, buying cycle, and operational capacity before seeking more data.
Inventory current sources and measurement. Identify gaps in signals, recency, identity, permissions, activation, or feedback. Select the smallest useful pilot, set a baseline and review window, and assign owners for the handoff and exclusions. Include the actual program cost in the economics.
After the pilot, review what the evidence supports. Refine the criteria, change the workflow, expand cautiously, or stop if the information is not useful. A demand-intelligence strategy should improve decisions rather than simply add another database.
Apply this to your acquisition program ↗Apply this to your acquisition system.
Continue exploring
Your market. An informed next move.
Define your offer, geography, available data, and intended channels. We’ll scope the intelligence and activation options for your program.
Find Demand in My Market ↗Signals indicate potential commercial relevance—not certainty that an individual will purchase. Coverage, permitted destinations, and refresh availability vary by program.