Automatic Release Emails: Why Epitrite Starts With a No-Send Baseline
Dantós built Epitrite around the release workflows he uses as an independent artist.
Begin with the listener decision you want to understand, then work backward to the smallest creative change. Compare Treat every item in an existing catalog as newly released with Confirm the Apple Music artist and save the current catalog as baseline, then follow the listener from Reel to page, signup, and release email.
Use the Instagram Reels lyric video guide and the manual release-email hub. Keep the song and destination steady. Decide before publishing that only releases newer than the established baseline enter the send workflow.
Key takeaways - Compare Treat every item in an existing catalog as newly released with Confirm the Apple Music artist and save the current catalog as baseline. - Review verified new-release detection and absence of false historical sends and the downstream fan action separately. - Make the public page deliver match the confirmed catalog identity and current release links before showing the signup form.
Test a no-send baseline for automatic release detection
Use Treat every item in an existing catalog as newly released as the baseline and Confirm the Apple Music artist and save the current catalog as baseline as the alternative. Track verified new-release detection and absence of false historical sends, public-page visits, and completed forms. Instagram Insights distinguishes views from unique accounts reached, so repeat viewing is not new audience growth.
Evidence: Instagram Help: Insights.
Separate what attracted attention from what persuaded someone to continue beyond Instagram. Save the Insights window and unusual distribution. Instagram supports preset or custom periods within the past 90 days.
| Test item | Baseline | Alternative |
|---|---|---|
| Creative | Treat every item in an existing catalog as newly released | Confirm the Apple Music artist and save the current catalog as baseline |
| Evidence | verified new-release detection and absence of false historical sends | Same measures and window |
| Next run | Keep if stronger | only releases newer than the established baseline enter the send workflow |
Align the artist page for a no-send baseline for automatic release detection
The page must match the confirmed catalog identity and current release links. Epitrite public artist pages need no visitor account and can show music, links, and selected Queue videos. Match the release name and first destination, then test the published route on a phone.
Evidence: Spotify for Artists: Artist profiles; Epitrite FAQ: creator-scoped fan lists.
The FTC requires honest headers and subjects, a postal address, and a working opt-out for commercial mail. Google also publishes authentication and unsubscribe rules, so announce a newly verified catalog addition, not old music discovered by setup needs a recognizable sender and direct destination. Align the name and artwork with the social audience growth guide.
- Repeat the release name used in a no-send baseline for automatic release detection.
- Put match the confirmed catalog identity and current release links first.
- Test links on a phone.
Write consent for automatic email only for genuinely new releases from this artist
Make automatic email only for genuinely new releases from this artist visible. The ICO says marketing consent needs a specific, informed promise and positive action. A follow, scraped address, or hidden policy is not an email choice.
Evidence: UK ICO: Email marketing guidance; Epitrite FAQ: creator-scoped fan lists.
Epitrite's public form needs no fan account and the artist can export the list as CSV. A fan can stop one artist's release mail without changing unrelated Epitrite messages. Keep that scope when announce a newly verified catalog addition, not old music discovered by setup.
- State this promise beside the field: automatic email only for genuinely new releases from this artist.
- Name the artist who will send the message.
- Test the completed form state.
- Protect CSV exports and unsubscribe suppression.
Sequence the email for announce a newly verified catalog addition, not old music discovered by setup
Use this angle: announce a newly verified catalog addition, not old music discovered by setup. Name the same release in the subject, button, and destination. The FTC calls for accurate sender details, honest subjects, a postal address, and clear opt-out. Never disguise promotion as an account notice.
Evidence: FTC: CAN-SPAM compliance guide; Google: Sender guidelines; Epitrite pricing and fan-email limits.
Epitrite Free supports one manual campaign per UTC month for up to 250 eligible fans. Pro adds confirmed Apple Music catalog checks and three manual campaigns per rolling 24 hours, up to 5,000 recipients total. Use the release-day checklist.
| Moment | Fan-facing message | Destination |
|---|---|---|
| Release live | announce a newly verified catalog addition, not old music discovered by setup | Direct release link |
| Page visit | match the confirmed catalog identity and current release links | Public artist page |
| Later value | review the confirmed artist whenever catalog identity changes | Relevant next action |
Review after a no-send baseline for automatic release detection
Make the next move review the confirmed artist whenever catalog identity changes. It must fit automatic email only for genuinely new releases from this artist. Instagram says recommendation eligibility does not guarantee recommendation. A creator-owned list offers another route, but permission still limits the message.
Evidence: Instagram Help: Recommendation eligibility; UK ICO: Email marketing guidance.
Separate what attracted attention from what persuaded someone to continue beyond Instagram. Repeat the variant when only releases newer than the established baseline enter the send workflow. Otherwise revise or return to the baseline for this release phase.
- Log verified new-release detection and absence of false historical sends without collapsing unlike actions into one score.
- Retire it when downstream action weakens.
- Suppress unsubscribed addresses.
- Check Epitrite pricing against the real eligible list size.
Questions artists ask
When should an artist compare Treat every item in an existing catalog as newly released and Confirm the Apple Music artist and save the current catalog as baseline?
Use the same window for Treat every item in an existing catalog as newly released and Confirm the Apple Music artist and save the current catalog as baseline. Record post time and unusual distribution. Instagram permits preset or custom Insights periods within the past 90 days. The goal is a fair comparison, not a universal timing rule.
Can Epitrite Free support automatic email only for genuinely new releases from this artist?
Yes. Free includes the public page, creator-owned list, CSV export, email design, and one monthly manual campaign for up to 250 eligible fans. For a no-send baseline for automatic release detection, use that path to match the confirmed catalog identity and current release links. Pro adds automation and higher limits; fan signup itself needs no Epitrite account.
Which result proves a no-send baseline for automatic release detection led to a fan relationship?
Here, conversion is a voluntary signup for automatic email only for genuinely new releases from this artist. Treat verified new-release detection and absence of false historical sends as diagnostic evidence. Release clicks and replies add context, but social interaction alone never grants permission to email that viewer later.
Send the release email for a no-send baseline for automatic release detection
Build both versions, publish the page, and state automatic email only for genuinely new releases from this artist. Choose the plan whose real campaign limits fit the eligible list.
Sources and methodology
This guide separates external authoritative evidence from Epitrite's first-party product documentation. Platform rules and product limits can change, so check the linked source before a time-sensitive campaign.
External authoritative sources
- FTC: CAN-SPAM compliance guide (2026)
- Google: Sender guidelines (2026)
- UK ICO: Email marketing guidance (2026)
