> For the complete documentation index, see [llms.txt](https://ask.fivetier.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.fivetier.com/home/resources/case-studies/g-o-media-a-success.md). # G/O Media - A Success! G/O Media's campaign was a triumph in strategic timing and targeted messaging. During the pivotal media planning season spanning the end of 2019 and early 2020, we focused our efforts on the bustling New York and Chicago markets, specifically during peak commuting times to ensure the highest impact. The campaign's effectiveness was immediately apparent, with the microsite garnering an average of over 100 direct visits daily, complemented by more than 20 text inquiries. The precision of Five Tier's platform allowed us to trace each visit and lead back to the exact moment and location of the ad's appearance. Additionally, the agility of our platform facilitated seamless and instant creative updates. The numbers tell the story of our success: 77,000 ad plays at an efficient $13.75 CPM, a reach of 10.9 million impressions across 5 integrated channels, and an exceptional 78% in added value. This is the Five Tier impact—efficiency, precision, and results. --- # 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://ask.fivetier.com/home/resources/case-studies/g-o-media-a-success.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.