Davies Meyer – home
    Data3 min read

    Intent Data

    Intent data records observed activity from which interest in a topic, product category or offer is inferred. It can provide clues for marketing and sales. It does not automatically establish purchase intent, a budget or the identity of the decision-maker.

    Intent Data explained

    Someone reads a comparison, a company appears more frequently around a specialist topic, or a contact requests a demonstration: these clues differ in strength. Distinguish explicitly expressed requests from interpretations of observed behaviour. A label such as “high intent” initially reflects the classification rules of the particular system.

    Owned data may come from interactions with your offers that you are permitted to record. External providers analyse activity in the sources available to them. Bombora, for example, describes topic activity within its network and matching that activity to companies. Such data does not cover all internet research or reliably identify everyone involved in a purchase.

    Check origin, collection period, topic classification and resolution: does the data concern a person, a company domain or an estimated match? Specialist research may also concern education, competitor analysis or a completed project. Old signals, shared networks and automated requests can complicate interpretation. Missing activity in a dataset does not mean an absence of need.

    Use signals as a starting point for a better question or more relevant information. In B2B, a cluster of topic activity can help examine an account hypothesis. It does not justify telling individuals that you know their confidential plans. Establish permitted use and contact routes independently of any score; a provider’s assurance cannot replace that assessment.

    Examples

    Hypothetical application

    A building-technology supplier sees increased interest in maintenance attributed to a company in external data. It first checks whether the company match and topic fit its offer. For an already agreed meeting, it prepares questions about operations. A specific procurement plan is only assumed once the customer confirms it.

    Key Points

    • Separate observed interest from explicitly confirmed needs.
    • Make data origin, freshness and matching visible.
    • Use signals for orientation and test assumptions in conversation.

    Practical application

    Choose a clearly bounded question. Document the source and interpretation of each relevant signal, then compare them with information confirmed later. Stop using the data if the additional clues do not justify the review effort.

    Useful measures

    Confirmed relevance

    Check how often topic clues connected to an actual suitable need.

    Matching quality

    Record uncertain, incorrect and outdated company or topic matches.

    Additional value

    Compare decision quality and total effort with the previous approach.

    Common mistakes

    • Treating every interest signal as an immediate purchase request.
    • Attributing company data to a particular individual.
    • Treating unobserved activity as proof that no need exists.

    Sources and context

    Frequently Asked Questions about Intent Data

    It can provide clues about interest. It cannot reliably establish who decides, whether a budget exists or when a purchase will happen in every case.

    Loading related terms…

    All Terms