> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/digital-marketing/measurement-and-attribution.md). # Measurement and attribution How MagicWorks approaches marketing measurement, attribution and commercial outcomes. A useful measurement system separates several layers: * technical tracking quality, * traffic and acquisition, * engagement, * conversion events, * lead quality, * opportunity progression, * and revenue contribution where data allows. GA4 is useful for behavioural measurement, but it should not be treated as the only source of truth. Search Console, Bing Webmaster Tools, ad platforms, CRM or lead systems, and server-side/business data may each answer different parts of the question. Attribution is never perfect. The goal is to make decisions with better evidence, not to pretend every customer journey can be reduced to one last-click number. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledge.magicworksitsolutions.com/knowledge/digital-marketing/measurement-and-attribution.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.