--- title: "Edit Station Configuration" slug: "edit-station-configuration" updated: 2026-03-23T18:09:32Z published: 2026-03-23T18:09:32Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.tritondigital.com/llms.txt > Use this file to discover all available pages before exploring further. # Edit Station Configuration If you have **Broadcast Administrator** or **Broadcast Manager** privileges, you can edit a station’s information by clicking on the **Edit** **Selected Station** button in the **Station Information** section. ![Station-Information](https://cdn.document360.io/7124b381-0a94-401a-abbd-9df9c4ea5dff/Images/Documentation/c397b501-df55-480c-8369-d32f6ec2f0b3.png) The station configuration window appears, where you can change your station details. Note that you will not be able to change certain information, such as the station’s name, password, language, and time zone. To change this information, please contact [Triton Digital Customer Support](/user/docs/contact-support). > [!NOTE] > **Note for Omny Studio users**: *Do not change your show's****URL****on this page*. The URL field, while editable, is populated from your Omny Studio settings via the Omny API. Any change you make to the URL here is non-permanent and can be overwritten from your Omny Studio settings at any time. If your show's URL needs to be added or edited, do so from your Omny Studio **Program settings**, in the **Social links > Show website** field. ![Station-Configuration-window](https://cdn.document360.io/7124b381-0a94-401a-abbd-9df9c4ea5dff/Images/Documentation/a6ea0d5b-e449-4e43-9757-aeec1020c668.png) ## Market Coverage **Market targeting** (*In- and out-of-market*) is an optional feature that works with TAP and TAP Programmatic. It only works if your podcasts/stations have a **defined geographical coverage area** within your Triton Digital publisher configuration that specifies your **market coverage area** based on either country, DMA or MSA (U.S. only) or a latitude/longitude with a defined radius. To **verify** if your stations have defined geographical coverage area, or to set it up if they don't, [contact Customer Support](/user/docs/contact-support). ## Monitoring Configuration > [!NOTE] > Enable cue point monitoring so you can view cue point activity in the Triton Digital Console and receive alerts if cue point activity drops below your defined threshold. Enable cue point monitoring in the Monitoring Configuration section of the Station Configuration window. With cue point monitoring enabled, you (or someone at your station) can receive email alerts whenever cue point activity drops below the threshold (Max Delay) that you set. This is useful, for example, to ensure ad breaks are occurring as expected; if your station breaks every 60 minutes or less and you set a 75 minute Max Delay threshold, you get an alert if 75 minutes pass without receiving a break cue point. Enabling cue point monitoring also activates the Cue Point status indicators on the [Station Monitoring page](/v1/docs/monitoring) of the Streaming menu. You can choose to monitor *all* cue points, or just the ad-related cue points (**break** and **endbreak**). - Select the **Enable (All)** checkbox and enter an alert threshold (**Max Delay**) in minutes to get alerts if this number of minutes pass without any cue point activity. - Select the **Enable (Ad only)** checkbox and enter an alert threshold (**Max Delay**) in minutes to get alerts if this number of minutes pass without any ad-specific cue point activity. ![Cuepoint-monitor-enable](https://cdn.document360.io/7124b381-0a94-401a-abbd-9df9c4ea5dff/Images/Documentation/00083ced-6fa8-4c42-bb67-feda493a080f.png) 1. Monitoring email address (see notes, below). 2. All cue points. 3. Ad-only cue points. > [!WARNING] > Select BOTH **Enable (All)** and **Enable (Ad only)** if you want to monitor for both total cue point silence and ad-specific cue point silence. If you only select **Enable All** you could have a situation where track cue points are being passed but not ad cue points, but you will not be alerted because it is only monitoring for total cue point silence. ### Cue point monitoring notes - Triton Digital recommends you set the **Max Delay** threshold to a level that you never expect to be exceeded unless something has gone wrong. In the example above, you would set your Max Delay at **75 minutes** if your station *always* breaks every 60 minutes or less. *The objective is to trigger alerts only when there is a problem*. - As a best practice, use your email application to create a **distribution list** of people who should be alerted if monitoring triggers an email alert. **Use the distribution list's email address in the Monitoring email field**. This ensures alerts are seen by multiple people, and it makes it easier for you to revise the list as people come and go in your organization. ## Station Break-end Grace Period Override With Triton Digital's TAP advertising platform, industry separation and frequency capping for live streams is handled differently than it was previously. One of the differences is how the system determines when the stream is in a **break**, and when that break is over. In some cases the pattern of cue points sent by your RAS might cause the ad server to think a break has finished when in fact it has not, result in the same (or similar) ads playing in close succession. Also, very brief content segments between breaks can cause the separation and capping system to return the same or similar ads as were played just before the brief content segment. The **Break-end grace period** is the time that must elapse after the **endbreak** cue point before the break is considered to be truly ended. If another ad cue point arrives before the grace period has elapsed, the system assumes the same break is still active. The **Default Break-end grace period** (which applies to all of your stations) is **one second*** which in most cases is sufficient. However, if you hear the same or similar ads playing during a break, or after a brief content segment between breaks, then it indicates that the system thinks the break is over before it actually is. If so, you can usually fix the problem by overriding the station's Break-end Grace Period with a longer period. ******While the Default Break-end Grace Period is set at one second, you can request a custom Default Break-end Grace Period setting (such as "30 seconds"). See below*. ### Custom Default Break-end Grace Period You can request a *custom* Default Break-end Grace Period setting (such as "30 seconds") by [contacting Customer Support](/user/docs/contact-support) and asking for a *global change to the default Break-end grace period*. Be aware that this changes the default for **all of your stations**. However, you can still go to the Station Configuration in the Triton Console and override that custom default setting on a station-by-station basis. Therefore: - To create a *custom Default Break-end Grace Period for all stations*: Contact Customer Support. - To *override the Default Break-end Grace Period for a specific station*: use the station configuration section of the Triton Console. **To override the default Break-end grace period:** 1. Go to your station's **stream configuration**. 2. In the **Station Break Management** section, click **Settings**. 3. Enter a value in the **Station Break-end grace period override** field (in seconds). 4. Click **Save**. ![Stream-Configuration-break-end-grace](https://cdn.document360.io/7124b381-0a94-401a-abbd-9df9c4ea5dff/Images/Documentation/4d408902-b533-4f21-8393-4878af255262.png) For more information on ad delimiters, refer to the [Advertising Technical Specification](/v1/docs/advertising-specification-ad-delimiters) and topics on [Frequency Caps](/v1/docs/flights-frequency-caps) and [Ad Separation](/v1/docs/ad-separation).