Name the requested action
The word save can become ambiguous when a brief includes several kinds of music objects. Ask what item the service concerns and how the action is described. Use the listing’s actual definition rather than treating every library-related action as equivalent.
Select the matching target
Confirm whether the accepted input is an individual track, release or another specified object. Keep that address separate from any playlist used to promote the music. A playlist containing the track is not automatically a substitute for the track itself.
Choose observable evidence
Before ordering, ask how the requested action can be assessed with the reporting available to you. Do not infer a save action from a change in play count. If the relevant measurement is unavailable, acknowledge that limitation instead of claiming a result from another metric.
Decision checklist
| Decision | What to check |
|---|---|
| Action | The precise save-related deliverable |
| Object | Track, release or other accepted target |
| Evidence | A measurement relevant to that action |
Worked example
An illustrative campaign sheet contains an album link and a playlist link, but the intended purchase is described as track saves. The buyer needs the exact accepted track target and the service’s action definition before submission.
Example figures explain the decision; they are not current prices or promised results.