Also see: Understanding Flight Targeting Rules.
You can create targeting rules in the Targeting section of the Flight page. You can create these types of flight targeting rules:
Content targeting: targets specific content such as stations or podcasts, genres, podcast episodes, or content tags.
Listener targeting: targets listeners based on criteria such as the listener's device, platform, age, gender, or location. Can also target custom parameters, DMP segments, TTags, or distributors.
Time targeting: targets specific times, such as days of the week and/or hour of the day. Time targeting is based on the timezone of the station, as defined in the station's configuration at Triton Digital.
Tutorial: Targeting in TAP
To open a targeting rule’s creation panel, select Ad targeting. See Understanding Flight Targeting Rules for details about Match/Not match, And vs. Or, "all" vs. "any" and so on.
This warning appears when you have selected Only targeted stations/podcasts but have not defined any content targeting rules. For more information, see Content Targeting and Content Access.
Select to add one or more content targeting rules.
Select to add one or more listener targeting rules.
Select to add one or more time targeting rules.
Select a ttargeting type's options menu to switch to the JSON editor.
Use the descriptions of the targeting parameters below to determine how your targeting rules should be made. Be sure to check the Targeting Rules Usage Notes.
Targeting Content
Content targeting lets you create rules that are specific to the content, such as the genre, market, or station. For podcasts, you can target episodes, publish date, content tags, and so on. The table below describes the content targeting options.
Also see Content Targeting and Content Access.
Rule Type | Usage Description |
|---|---|
Reach Extension | |
Reseller contracts | Only available to inventory resellers using Reach Extension. For specific usage details, see Reach Extension for Resellers. |
Stations/podcasts | |
Station/podcast | Target one or more specific stations or podcasts. If the station or podcast has a display name set in your publisher configuration at Triton Digital, then both the display name and the station/podcast name are shown in the selection list. If a display name is not configured, then only the station/podcast name is shown. In the example below, the first two stations have display names configured and the third station has no display name configured. |
Station/podcast genre | Target one or more station or podcast formats (genres), such as "talk radio," "sports," or "true crime." Note that this only works if your stations/podcasts have their genres defined in your Triton Digital publisher profile. |
Station/podcast market | Target one or more station or podcast markets. |
Station/podcast sub-publisher | Target one or more station or podcast sub-publishers (as defined in your publisher configuration at Triton Digital). Not all publishers have sub-publishers defined. |
Episodes (only applies to podcasts) | |
Episode ID | Target one or more podcast episodes based on episode ID. For Omny Studio users, this is the Clip ID:
The Omny podcast can be targeted as soon as the Clip ID is created. However, ads will not deliver until the podcast is published as either "unlisted" or "public." ("Private" podcasts cannot be targeted by Episode ID.) The episode ID for podcasts from other platforms is the GUID, which can be derived from the podcast's RSS feed. Open the RSS feed URL in a web browser and search for the episode you wish to target. The episode ID can be found between the <guid> tags in the RSS file:
|
Episode publish date | Target all podcast episodes based on the date they were published. The date can be exact ("Is"), or based on "On or before/On or after" or between specific dates. Can be set as include or exclude. |
Episode publish age | Target all podcast episodes based on the number of days since they were published. The date can be exact ("Is"), or based on "On or before/On or after" or between specific dates. Can be set as include or exclude. |
Other | |
Content tag | Free-form tag matching, such as for station tags. Note that limited content access users cannot use content tags. For more information, see ‘Content Tag’ Targeting Notes. |
Contextual tag | See Contextual Targeting. |
Position in break | Target the position in an ad break as First or Last. "Last" can only be used with the Podcast and/or On-Demand delivery methods. See ‘Position in Break: Last’ Targeting Notes, below. |
Targeting Content Tags
The all content delivery indicator must be enabled in order to use Content tags.
If you target a station tag but no stations are assigned to that tag, the flight will not deliver.
See the Advertising Knowledge Base for articles on using content tags, such as:
How to use content targeting cue points to target a livestream show. This requires access to your radio automation system.
Targeting Omny Studio Podcast Mid-roll Ad Marker Tags in TAP and TAP Programmatic.
See Use Cases (Ad Quality/Exclusivity) for information on a suggested method for 100% SOV involving the use of content tags.
See the Omny Studio User Guide for an article on using content tags to target Omny ad break markers for podcasts.
Targeting Position in Break: Last
You can only use Position in Break: Last with the Podcast or On-Demand delivery methods.
Targeting the last position is a delicate balance between several factors. Specifically, it targets the final position in a podcast or on-demand ad marker, but successful targeting depends on whether or not there are ads available for other positions in the break.
If there are no other non-last ads available for the break, the last position will not be filled. In other words, the break no longer has a "last" position, so no ads can be placed as last.
Example of how Position in Break: Last can fail
You have a flight that targets FIRST position in break.
You have a flight that targets LAST position in break.
You have an ad break with three positions.
You can fill the FIRST position but you don't have an ad for the MIDDLE position. Since the middle position is not filled, the system reverts to content, and as such the LAST position is no longer available to be filled.
Recommendation
Use Position in Break: Last with caution. Flights with this targeting option will only deliver when you have sold all other ad positions within the break.
Targeting Listeners
Rule Type | Usage Description |
|---|---|
Player | |
User agent | The specific agent/player (software) that is used to play the audio stream/file. |
User agent family | The type/family that best describes a specific agent/player, such as browser, monitoring, player-custom, player-generic, or podcast. |
User agent device | The specific device (hardware) that is used to play the audio stream/file. |
User agent device family | The type/family that best describes a specific device. |
User agent OS | The Operating System that is used to play the audio stream/file. |
User agent platform | The platform of the listener's player, such as "desktop," "mobileapp," or "smartspeaker." Tutorial: Targeting Smart Speakers (Dur: 1:10) |
OMID capability | (On-demand delivery method only.) Players that are enabled with the IAB’s Open Measurement Interface Definition API, usually via the Open Measurement SDK. To be used in conjunction with the on-demand Partner Token and omid parameter. Options are:
Note: support for forecasting and reporting against OMID capability will be available in a future release of TAP. |
Demography | |
Age | The age, in years. You can enter a specific age ("is") or choose "less than or equal to" or greater than or equal to" a specific age. You can also enter an age range (e.g., "between 18-34"). See the Demographic Targeting Note below. |
Gender | Options include Male, Female, or Other. As with all selectable targeting options, including one (e.g., "Male") means the other options are not included. See the Demographic Targeting Note below. For more information about including and excluding, see Targeting: Targeting: Include and Exclude and Targeting Rules Usage Notes. |
Geography | |
Market targeting | Select either In-market or Out-of-market. See In-market and Out-of-market Targeting. |
Location | Select the location. The top level of the location list is the country, but you can click through to select regions and territories, including DMA and MSA areas (U.S.A. only). Tutorial: Targeting a Single Geographic Area (Dur: 3:15) Tutorial: Targeting a DMA (Dur: 2:13) |
IP | Include or exclude specific IPv4 addresses. Use commas to separate multiple entries. Note: IP address targeting is intended for test purposes only. Maximum 100 IP addresses. |
Latitude and longitude | Enter a latitude and longitude in degrees (and optionally, minutes/seconds), plus a radius in kilometers or miles from that point to create a geographic targeting circle. Alternatively, use the map to create a targeting circle:
Map definition color codes:
Watch: Note: do not create overlapping include and exclude zones. Results for the overlap area are unpredictable. |
Postcode | ZIP or postal code. Tips:
Tutorial: Targeting by Postal Code (Dur: 2:24) |
| |
Custom parameter | Parameters reserved for custom development programs with Triton Digital. (Similar to TTags but requires custom co-development between publisher and Triton Digital.) |
DMP segment | |
TTag | Custom Targeting Tags (TTags) in TAP work in conjunction with custom tags that are declared by your player. When there is a match, targeting is achieved and the campaign can deliver to that player. Note that TTags should be used for listener context, not content context. For more information, see Custom TTag Targeting. |
Distributor | The distribution channel (i.e., digital property where the listener accesses the audio content). |
Demographic Targeting Note: demographic targeting (age/gender) only works if the player passes demographic data to TAP. For more information, see the "Parameters" section of the Advertising Technical Specification,
Targeting Demographics
Demographic targeting (age/gender) only works if the player passes demographic data to TAP. For more information, see the "Parameters" section of the Advertising Technical Specification,
Targeting In-market and Out-of-market
Market targeting applies to podcasts, on-demand stations, and live-streaming stations that have defined geographical markets using location data from the player. This is a Listener targeting option found here: Listener targeting > Geography > Market targeting
In-market (targets in-market listeners).
Out-of-market (targets out-of-market listeners).
Market targeting and measurement (In- and out-of-market) only works if your podcasts/stations have a defined geographical coverage area and you are set up to receive location data (latitude/longitude) from the player, and the player sends this data. These are optional settings within your Triton Digital publisher configuration.
The defined geographical coverage area specifies your market coverage area based on country, state, DMA or MSA (U.S. only), or a latitude/longitude with a defined radius.
Receiving location data from the player, including GPS data from mobile devices, is simply an on-off service toggle that can be set in your Triton Digital publisher configuration.
To verify or set up these settings, or to modify them, such as changing your coverage area or switching from DMA to MSA, speak with your Triton Customer Success Manager.
You only need to select one item; for example, when you include In-market, excluding Out-of-market is implied, so you don't need to explicitly create an exclude Out-of-market rule (and vice-versa).
Targeting Time
Time targeting is based on the timezone of the station, as defined in the station's configuration at Triton Digital.
Combining trend-based pacing with time targeting essentially disables the trend-based algorithm. The TAP UI will still show Trend-based as the selected pacing option, but the pacing within the defined time targeting window will behave as Even paced. For more information, see Pacing Tips.
Rule Type | Usage Description |
|---|---|
Day of week | Select one or more days of the week. Can be combined with Hour of the day to create targeted dayparts. |
Hour of day | Select an hour of day rule and and an hour of day value:
|