Name the intended object
A playlist contains tracks, but a track-related service may require a single upload address. Read the accepted input and verify whether playlist-level requests are supported. Do not assume a provider will infer which track matters most from its position in the list.
Specify the distribution
If the offer accepts a playlist, ask which tracks receive the action and whether the quantity is per track or shared. Save an explicit allocation when several tracks are included. A playlist-wide label is not a substitute for those details.
Review edits before submission
Check that the relevant tracks are still present and accessible. If the list has changed since the brief was prepared, update the plan before paying. Keep the submitted selection with the request rather than relying on the current playlist view later.
Decision checklist
| Decision | What to check |
|---|---|
| Input | Track address or supported playlist address |
| Allocation | Which tracks and how much each receives |
| Version | Playlist selection at the time of submission |
Worked example
Suppose a hypothetical playlist contains six tracks but the campaign concerns only the opening single. Use the accepted single-track target unless the chosen package explicitly defines a different playlist allocation.
Example figures explain the decision; they are not current prices or promised results.