> ## Documentation Index
> Fetch the complete documentation index at: https://help.fanaura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pre-Save Pages

> How Fanaura pre-save smart links work. What fans see, native notification pre-save, data collection, and the fan experience from click to release day.

Pre-save pages let fans commit to your music before release day and give you their contact information, platform preference, and consent to hear from you.

<Note>Every presave is a new fan in your database. Every presave page is a growth engine.</Note>

***

## What Is a Presave?

When a fan pre-saves your song, they tell Fanaura they want to hear it on release day and choose a preferred streaming platform. Fanaura records that commitment in your fan database.

**Fanaura uses native notification pre-save.** Fans are not sent through Spotify OAuth to save the track to their library automatically. On release day, Fanaura sends them an email or SMS with a direct link to stream the song, and your presave page converts to a stream page.

**Why presaves matter:**

<CardGroup cols={2}>
  <Card title="Release-day engagement" icon="play">
    Fans who pre-save are primed to stream on day one when they receive your release notification.
  </Card>

  <Card title="Owned fan data" icon="database">
    Every presave captures a real contact with consent.
  </Card>

  <Card title="Campaign targeting" icon="bullseye">
    Presavers are your most engaged fans for this release cycle.
  </Card>

  <Card title="Momentum measurement" icon="chart-line">
    Presave counts show anticipation building before the drop.
  </Card>
</CardGroup>

***

## The Presave Page URL

Your presave page lives at:

```
fan.fanaura.com/link/presave/[slug]
```

<Tip>The slug is generated from your release title (e.g., `midnight-drive`). You can customize it in the asset settings.</Tip>

***

## What Fans See

<Steps>
  <Step title="Fan authentication (first visit)">
    If the fan is not signed in, they complete a short signup flow (email and optional phone) through the data wrapper. Returning fans skip this step.
  </Step>

  <Step title="The presave page">
    After authentication, fans see:

    * **Album artwork**
    * **Song title** and **artist name**
    * **Release date** or countdown
    * **Platform buttons** for each enabled platform (Spotify, Apple Music, YouTube Music, and others)
  </Step>

  <Step title="Platform selection">
    When a fan clicks a platform button, Fanaura records a **native pre-save** for that platform. There is no Spotify OAuth redirect and no automatic library save on Spotify.

    The fan sees a confirmation that they are set for release day.
  </Step>

  <Step title="Release day notification">
    On release day, Fanaura sends the fan an **email or SMS with a direct streaming link** for their chosen platform. They tap the link and start listening.

    The presave page also converts to a **stream page** with live platform links.
  </Step>
</Steps>

***

## Native Notification Pre-Save (Not Spotify OAuth)

This is the most important detail to understand about Fanaura pre-saves.

| What fans might expect | What Fanaura actually does |
| - | - |
| Spotify OAuth login | No OAuth. Fan selects Spotify as their preferred platform. |
| Song auto-added to Spotify library on release day | Fan receives an email or SMS with a direct link on release day. |
| Fanaura accesses their Spotify account | Fanaura records the presave internally and notifies them at release. |

**Why native notification pre-save:**

* Fans opt in through Fanaura's own signup flow, so you capture email and SMS consent.
* Release-day messages drive immediate streams through a link you control.
* No dependency on third-party OAuth tokens that can expire or be revoked.

<Info>Spotify integration in Fanaura is read-only for artist search and metadata lookup during onboarding. It is not used for pre-save authorization.</Info>

***

## Fan Data Captured

| Data point | How it is captured |
| - | - |
| **Email** | Fan authentication / data wrapper |
| **Phone number** | Optional in data wrapper |
| **First and last name** | If requested in wrapper settings |
| **Platform preference** | Which platform button the fan selected |
| **Location** | Auto-detected from IP (city, state, country) |
| **Email and SMS opt-in** | Consent checkboxes |
| **Consent timestamp** | Recorded at signup |
| **Presave timestamp** | Recorded when platform is selected |
| **Referral source** | UTM parameters when present |

***

## Mobile Optimization

<Info>Most presave traffic comes from mobile (Instagram stories, TikTok bios, and link-in-bio pages). Fanaura presave pages are mobile-first.</Info>

* Large artwork optimized for phone screens
* Big, tappable platform buttons
* Single-column layout
* Fast load times

<Tip>Test your presave page on your phone before sharing it publicly.</Tip>

***

## What Happens After Presaving

<Steps>
  <Step title="Fan added to database">
    The fan appears in **Fans** with contact info, location, platform preference, and a presave record linked to the release.
  </Step>

  <Step title="Flow triggers activate">
    If you set up a presave flow (e.g., "When someone presaves, send a thank-you email"), it fires immediately.
  </Step>

  <Step title="Presave count updates">
    Your release dashboard shows real-time presave counts.
  </Step>

  <Step title="Release day">
    Fanaura sends release notifications to presavers and converts the page to a stream page automatically.
  </Step>
</Steps>

***

## Best Practices

<Tip>**Share the link everywhere.** Instagram stories, TikTok bio, email blasts, and show screens.</Tip>

<Tip>**Create urgency.** "Presave by Friday for an exclusive bonus" drives more action than a generic ask.</Tip>

<Tip>**Use high-quality artwork.** Cover art is the visual centerpiece of the page.</Tip>

<Tip>**Open presaves 2–4 weeks before release.** Enough time to promote without losing momentum.</Tip>

<Tip>**Set up a presave flow.** Send an immediate thank-you message after every presave.</Tip>

***

## Common Questions

<AccordionGroup>
  <Accordion title="Can fans switch platforms after presaving?">
    Yes. If a fan selects a different platform button, Fanaura updates their presave to the new platform preference.
  </Accordion>

  <Accordion title="What if a fan does not complete platform selection?">
    They can still be in your database from the authentication step. Encourage them to tap a platform button to complete the presave.
  </Accordion>

  <Accordion title="Does Fanaura save the song to Spotify automatically?">
    No. Fanaura uses native notification pre-save. Fans receive a direct link on release day. This is not Spotify OAuth library save.
  </Accordion>

  <Accordion title="Can I see who presaved?">
    Yes. Your release dashboard shows total presave count and individual fan records with platform preference.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.