Davies Meyer – home
    Performance3 min read

    Conversion

    A conversion is a predefined goal action, such as an order or a qualified enquiry. What a report counts depends on definition, measurement and attribution. A recorded conversion therefore does not establish that advertising caused the action to happen additionally.

    Conversion explained

    Start with the business task. A submitted form can be measured technically; whether it contains a suitable enquiry becomes clear through assessment. Define separately when an event fires and when the business condition is met. Clicking “Submit” should not count as an accepted enquiry when the form returns an error.

    Main goals and intermediate steps answer different questions. An order may be a main goal, while a saved product configuration is an intermediate step. Whether that step predicts later completions needs investigation. The classification itself does not turn it into revenue.

    Record the counting rule, attribution window, value and data source. Several advertising reports may claim the same order. Adding their totals does not automatically produce a count of distinct orders. Separate observed and modelled values, and campaign attribution from additional effects.

    Tool terminology also differs: Google distinguishes Analytics key events from conversions in an advertising context. Clarify the actual meaning when handing data over. The creative idea, working user journey and checked measurement need to describe the same goal action.

    Examples

    Hypothetical application

    A consultancy defines a suitable appointment enquiry as its goal. The website confirms successful receipt, then the team checks the topic and contactability. The report separates received forms, suitable enquiries and conversations that actually took place. None of these stages is booked as new revenue without further assessment.

    Key Points

    • Align the business goal action with the technical event.
    • Distinguish main goals from intermediate steps.
    • Document multiple counting and attribution rules.
    • Separate recorded actions, attributed outcomes and additional effects.

    Practical application

    For each goal, specify the business condition, technical trigger, counting rule, data source and validation. Test successful, abandoned and failed journeys, as well as duplicate submissions.

    Useful measures

    Confirmed goal actions

    Business-validated outcomes under a documented definition.

    Measurement discrepancies

    Explain differences between operational outcomes and individual reports.

    Outcome quality

    For example, assess enquiry suitability or order validity.

    Common mistakes

    • Equating a button click with successful completion.
    • Counting a newsletter registration and a qualified sales opportunity as equivalent.
    • Presenting server-side collection as automatic data completeness or legal approval.

    Sources and context

    Frequently Asked Questions about Conversion

    No. An enquiry, registration or booking can be the goal. Name the action and its business value rather than combining different outcomes without assessment.

    Loading related terms…

    All Terms