Before day 1: define the campaign and record a baseline
Confirm the public Spotify track link, artist profile, artwork, rights, campaign budget, countries, and the one action the ad asks people to take. Open every destination on a phone. If the release identity changes between ad and Spotify, fix that confusion before buying attention.
Record the starting Spotify for Artists data: listeners, streams, followers, saves, top countries, and source of streams. Note current playlists, organic posts, press, collaborations, and other activity that may affect the same period. A baseline turns the final review into analysis instead of memory.
- Final Spotify song link and current artist profile.
- Rights to promote the recording, composition where applicable, artwork, footage, and likenesses.
- One total 30-day budget that does not depend on a guaranteed return.
- One primary listener hypothesis and a documented outbound event.
Days 1-3: build the listener journey
Create a mobile-first vertical ad around the song's clearest emotional or musical moment. The first frame should make sense without sound, while the audio supplies the payoff. Keep the artist name, song title, and Listen now action clear and away from placement interface overlays.
If the ad uses a song landing page, keep it fast and focused. Match the artwork and language from the ad, make the Spotify action obvious, and remove distractions. Add consistent campaign parameters to the landing URL and verify that the outbound Spotify button produces the event used in reporting.
Days 4-7: launch and perform technical quality control
Submit the campaign, allow for platform review, and confirm that it is approved, spending, and reaching the intended destination. Check the creative crop, sound, title, call to action, country controls, and mobile page. Fix a broken link or rejected asset immediately.
Do not declare success or failure from a few early clicks. Meta's pricing guidance recommends enough budget across at least seven days for its system to learn. The ad auction assesses the objective, audience, budget, duration, and creative, then adjusts delivery as it observes response.
Days 8-14: read the funnel before making changes
Review spend, impressions, reach, outbound response, landing-page visits if applicable, Spotify-button clicks, and cost per outbound visit. Look for the weakest transition. A delivery problem, a creative problem, and a landing-page problem require different responses.
Keep an issue log. If a major edit is necessary, record the time and reason so the before-and-after periods are not blended. Avoid changing audience, creative, placement, and destination at once; that may alter delivery without revealing which decision mattered.
Days 15-21: improve one meaningful variable
By the middle of the campaign, choose whether the evidence supports staying steady or testing one substantial improvement. A new hook, different opening scene, clearer title treatment, or faster landing page can teach more than a microscopic color adjustment.
Do not scale only because one day was unusually cheap. Review a multi-day range, frequency, market distribution, and the amount of evidence behind the result. A larger budget creates more delivery opportunity but cannot guarantee proportional Spotify listeners or streams.
Days 22-30: finish the planned window and capture context
Keep technical monitoring active while allowing the campaign to complete its planned window. Save the final creative, dates, audience setup, country distribution, spend, reach, impressions, outbound visits, and event definition. Export or screenshot source reports before account settings change.
Review Spotify for Artists for listeners, followers, saves, release engagement, countries, and source-of-stream movement. Spotify distinguishes active sources, where people intentionally seek music, from programmed sources. That context is more informative than a single monthly-listener total.
After day 30: separate campaign facts from interpretation
Campaign facts include how much was spent, what the ad platform delivered, how many outbound visits were tracked, and which setup was used. Spotify facts include the behavior reported inside Spotify. The interpretation is whether the combined evidence supports keeping, changing, or retiring the campaign approach.
Schedule a later check around day 60 or 90 to see whether active listening, follows, saves, or catalog exploration held after paid delivery ended. The final output should be a short learning memo for the next release, not a promise that every click became a fan.
The 30-day operating rhythm
A professional campaign is calm and documented: prepare the destination, launch with a clear hypothesis, verify delivery, review meaningful windows, change one important variable when justified, and preserve the result. The schedule prevents both neglect and frantic daily optimization.
MetaSongPromo campaigns use this 30-day frame for managed advertising. Artists approve the advertising budget at launch, while the campaign team handles creative support, setup, delivery, reporting, and status communication. Outbound Spotify visits remain clicks, not guaranteed listeners or streams.
Frequently asked questions
Why run music promotion for 30 days?
A month provides more context than a release-day burst and supports preparation, quality control, observation, and a documented review. It does not guarantee better Spotify outcomes.
How often should I check a live campaign?
Check technical status early, then review meaningful multi-day windows. Daily monitoring can catch broken links or rejected ads, but constant edits make the result harder to interpret.
What should change halfway through the campaign?
Only change something when the evidence identifies a likely problem. Prefer one meaningful variable, such as the opening creative hook or landing-page clarity, and document the edit.
What belongs in the final report?
Include spend, dates, creative, audience setup, countries, reach, impressions, outbound visits, cost per visit, event definitions, Spotify for Artists changes, and other promotion that overlapped.
Primary sources and further reading
Platform features and policies can change. These primary sources were reviewed on , when this article was last updated.