In this article

You'll learn how to:

• mark sent playlists with Client Version as the first line of defence for reporting
• set up a Pitch Log Channel to organize sent playlists
• use playlist tags to add reporting context
• build useful reports from those habits
• avoid common pitch-tracking mistakes

Build tracking into your sharing workflow from the start

The most common pitch-tracking problem is trying to reconstruct activity after the fact. The habits in this article work best when they run alongside sharing - so that every time a playlist goes out, it is already marked, filed, and tagged correctly. Think of it as two things happening at the same time: you share the playlist, and you record that share in a way that makes it reportable later.

Mark sent playlists with Client Version as you save them

The first and most important habit is turning on the Client Version toggle when you save a playlist that is being sent externally. This is applied in the Save Playlist settings and acts as the foundation of all pitch reporting - it creates a filter that separates playlists that were actually sent from internal shortlists, research playlists, and works in progress.

Without this toggle applied consistently, reports become much harder to interpret because there is no reliable way to distinguish outbound activity from everything else. Every time a playlist goes out, turn it on before you share.

Set up a Pitch Log Channel

Create a dedicated Channel called Pitch Log and use it as the one clear place where sent playlists live. Inside it, add folders for each month, each company, or another structure that makes sense for how you pitch.

For many teams, monthly folders are the easiest starting point because they keep activity moving in a clear timeline. Others prefer to break things out by client group or project type. The exact structure matters less than the consistency.

The important thing is that sent playlists live somewhere intentional - rather than only floating free with all the other playlists in Browse, which is where they will always appear regardless of whether they have been filed into a Channel.

Save sent playlists consistently

When you save or file a pitched playlist, try to do it consistently - adding it to the Pitch Log Channel, placing it in the correct folder, applying the right playlist tags, and marking it as Client Version if it was actually sent externally.

A simple repeatable workflow is usually better than an elaborate one. Every outgoing client playlist might follow this pattern: save the playlist, turn on Client Version, add relevant playlist tags, add it to the Pitch Log.

Use playlist tags to add reporting context

Playlist tags are one of the most useful tools for pitch tracking because they let you describe the context around a playlist without changing where it lives. Useful tags for pitch tracking include company or client name, project name, media type, territory, internal campaign name, and department or team.

If your team is pitching to a specific client, tag all relevant playlists with that client's name. If the work relates to advertising, also apply an Advertising tag. Later, those tags make it much easier to see every playlist connected to that client or media type - even if the playlists live in different folders or were created at different times.

Consistently tagging playlists by media type - Film, TV, Advertising, Radio - also makes reports much more meaningful. Rather than just seeing a long list of playlists, you can filter outbound work by the kind of opportunity it supported, making it easier to answer questions like how many film pitches went out this quarter, or how much TV-related pitching a specific artist received.

Build reports from those habits

When you open Reports in DISCO, start with a clear question - all playlists sent to one company, all client playlists from the last 30 days, all playlists sent for film, or all playlists containing a specific artist that were sent externally.

Some of the most useful reporting filters are time period, Channel, playlist tag, artist metadata, Clients lists only, and include tags in output.

Report on playlists sent to one client - tag playlists with the company name, mark them as Client Version, then filter by that playlist tag with Clients lists only set to Yes.

Report on work by media type - filter by your media type tag, set Clients lists only to Yes, and include tags in the output.

Report on a specific artist in pitched playlists - use the artist metadata filter, combine with Clients lists only, and include tags so you can also see the media type, project, or client context.

Always include tags in exported CSVs when the report is meant to be shared or reviewed by others. Without tags, a report shows what playlists existed. With tags, it shows why those playlists existed - which client, which project, which media type.

Common mistakes to avoid

Relying on memory instead of building a real pitch log is the most common problem. Creating playlists for external pitching without turning on Client Version, filing them in the Pitch Log, or tagging them properly makes reporting much weaker later.

The other extreme is over-tagging - building a structure so complex that no one wants to maintain it. A cleaner approach is one Pitch Log Channel, a simple folder structure, a manageable set of playlist tags, and consistent use of Client Version.

Wrap up

Pitch tracking works best when it is part of the sharing workflow from the start. Mark every externally sent playlist with Client Version as you save it. Use a Pitch Log Channel to keep sent playlists organized. Apply playlist tags to add context such as client, project, and media type. Use Reports to filter and review that activity over time. When those pieces work together, DISCO becomes a clear record of what your team has pitched, where it went, and how to make sense of it later.