Davies Meyer – home
    Analytics4 min read

    Web Analytics

    Web analytics is the systematic collection and analysis of website data to answer concrete questions about usage and outcomes. It connects a measurement plan with checked data, interpretation and subsequent decisions. Observed behaviour does not automatically explain visitors’ motivations or the cause of a result.

    Web Analytics explained

    Good analysis starts with a question: Can people find the right information? Where does an enquiry fail? Which leads to suitable contacts? The question determines the required events, comparison groups and success criteria. An available template should not dictate this sequence.

    Check measurement before building a story from the numbers. Page views, sessions and users are different counting units. An attempted submission is not yet confirmed completion. Changes to tags, filters or consent conditions can shift values. Record these influences in the report.

    Segmentation can reveal differences, for example by device or landing page. A difference does not establish its cause. Connect the observation with a plausible hypothesis and an appropriate check: a technical test, an observed user task or a carefully planned experiment.

    Financial interpretation also needs clear boundaries. Attributed revenue is not automatically additional revenue; revenue is also not profit. Costs, enquiry quality and actual completions may change the assessment. Use suitable references and identify which data can be reliably connected.

    Creative Engineering connects the message, user journey, technology and learning from outcomes. AI may help screen anomalies or prepare analytical questions, for example. Value comes from an appropriate question and a professionally checked answer. We take responsibility for the concept and quality.

    A small, maintained setup may be sufficient for a clear question. Include data purpose, access and retention in planning. More tracking, an additional server or a larger dashboard makes analysis neither automatically better nor legally permissible.

    Examples

    Hypothetical application

    A product page receives many visits but few enquiries. Analysis reveals an unusual point of abandonment in the form. A subsequent test confirms a file-selection error on smartphones. The team fixes the error and then checks both functionality and the trend in confirmed enquiries.

    Key Points

    • Start with a concrete question.
    • Check measurement before interpretation.
    • Distinguish observation, explanation and effect.
    • Translate findings into a decision that can be checked.

    Practical application

    Formulate the question, hypothesis and success criterion. Check the required collection, investigate suitable comparison groups and record the next action and follow-up evaluation.

    Useful measures

    Data quality

    Keep defined test cases, known gaps and changes traceable.

    Appropriate outcome

    Assess confirmed, suitable enquiries rather than button clicks alone, for example.

    Learning progress

    Record which hypothesis was examined and which decision changed as a result.

    Common mistakes

    • Claiming motives or causes from numbers alone.
    • Equating recorded revenue with additional impact or profit.
    • Publishing unsupported client results or general improvement percentages as experience.

    Sources and context

    Frequently Asked Questions about Web Analytics

    It can show where unusual patterns occur in measured use. Motivations and causes require additional investigation, such as user tests, follow-up questions or experiments.

    Loading related terms…

    All Terms