Davies Meyer – home
    Analytics3 min read

    User

    A user is a person using a website, app or service. In an analytics report, however, “user” refers to a usage entity distinguished under technical rules. The count is not automatically a complete list of uniquely identified people or customers.

    User explained

    Design concerns the actual person and their task. Someone may be looking for an assembly guide, comparing products or managing an account on behalf of a company. These roles explain possible requirements better than merely knowing that an identifier generated a click. The and paying customer need not be the same person.

    Measurement requires rules for recognising returning use. Depending on the method, device identifiers, signed-in IDs or models may contribute. One person may use several identifiers; a shared device may represent several people. Explain which technical entity the report actually distinguishes.

    A “Users” column also needs a precise meaning. GA4 distinguishes total, active, new and returning users, among other metrics. These classifications follow the tool’s criteria. Being “new” in a measurement does not establish that someone previously knew nothing about the brand.

    Combine behavioural data with suitable conversations or usage observations. An abandonment initially describes a recorded journey; its cause needs investigation. AI can organise patterns or prepare questions. It does not replace actual user voices. We take responsibility for the concept and quality.

    Examples

    Hypothetical application

    A spare-parts service is designed for people repairing equipment. Several employees may use one account. The team separates account counts from person counts and observes how users find the correct part number. It evaluates better design against that task.

    Key Points

    • Distinguish person, customer, account and measurement identifier.
    • Understand user needs through concrete tasks.
    • Name the exact user metric and identity logic.
    • Do not treat recorded journeys as complete explanations of motives.

    Practical application

    Separate the person and their task from the technical measurement definition in the brief. Document identity logic and data coverage, then test concepts with suitable actual users.

    Useful measures

    Defined user count

    Name the metric, period and identity logic.

    Task success

    Check whether suitable users achieve the intended result.

    Qualitative evidence

    Document observations and feedback with their provenance and limitations.

    Common mistakes

    • Presenting cookies or accounts as an exact count of people.
    • Describing assumptions from click patterns as proven motivation.
    • Presenting AI-generated answers as an actual user survey.

    Sources and context

    Frequently Asked Questions about User

    Not reliably. The count follows the identity and measurement logic in use. Device switching, shared accounts or missing signals can affect the mapping.

    Loading related terms…

    All Terms