> 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/fast-track-your-spotify-rollout-boost-streams.-gain-real-fans./presave-campaigns-what-to-do-and-what-not-to-do.md). # Presave Campaigns: What To Do & What Not To Do {% embed url="" %} **Forever Presave campaigns are important, but you need to be careful about what you offer. Don't just give away random prizes like an iPad just to get people to pre-save your song. In this video we’ll break down the do’s and don’ts when it comes to running a presave campaign and the types of offers you should incorporate.** Keep in mind that the goal of a pre-save campaign is to identify potential fans and turn them into loyal listeners and super fans, not to quickly build your email and text database. Don't show one thing on social media and then have a completely different look and feel on your pre-save page. This can be confusing and feel like a bait-and-switch. --- # 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/fast-track-your-spotify-rollout-boost-streams.-gain-real-fans./presave-campaigns-what-to-do-and-what-not-to-do.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.