> 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/buyer-guides/choosing-digital-marketing-partner.md). # Choosing a digital marketing partner A practical buyer guide for evaluating a digital marketing partner. Ask how the partner connects channel activity to business outcomes. Useful evaluation questions include: * What data is required before work starts? * How are conversions and lead quality defined? * Who owns analytics and tracking quality? * How are SEO, paid media, content and conversion issues separated? * What happens when the evidence says a channel should be reduced? * Can the team explain what it will not do? A strong partner should be able to distinguish activity from progress and should be comfortable discussing attribution limitations rather than hiding behind dashboards. --- # 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/buyer-guides/choosing-digital-marketing-partner.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.