> For the complete documentation index, see [llms.txt](https://help.foreverfanmusic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.foreverfanmusic.com/courses/advertising-101-your-complete-training-guide/conversion-vs-traffic-ads.md). # Conversion vs Traffic Ads {% embed url="" %} **In this video we’ll cover the key differences between conversion and traffic ad campaigns, analyzing their objectives, and the way the ad platforms' AI systems approach them.** It's important to consider the trade-offs between conversion and traffic ads when planning an advertising strategy. Conversion ads are generally the preferred starting point, as they ensure that the advertiser is paying for users who are more likely to convert. However, once the conversion ad campaign has been optimized, it can be worth testing a traffic ad campaign to see if it can drive more cost-effective traffic to the website. The decision to use conversion or traffic ads ultimately depends on the advertiser's goals and the specific characteristics of their target audience. Careful testing and analysis of the results are crucial to determine the most effective approach. --- # 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://help.foreverfanmusic.com/courses/advertising-101-your-complete-training-guide/conversion-vs-traffic-ads.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.