Parameters

lsid

Main user identifier for Triton Digital to use as the basis for measurements and frequency capping.

This parameter is recommended.

See Listener ID Management. for usage details.

String

Alpha-numeric characters, including the following list of special characters:

_ = * + . [ ] { } ( ) ~ -

ppid

Publisher provided listener ID. URL-encoded string.

As above.

idfa

Apple Identifier for Advertisers. (Only use if user has not enabled "Limit Ad Tracking.")

As above.

gaid

Android Advertising ID. (Only use if user has not enabled "Opt out of interest-based advertising.")

As above.

rida

Roku ID.

As above.

aifa

Amazon Advertising ID.

As above.

msai

Microsoft ID.

As above.

app

App-generated ID.

As above.

cookie

Cookie-based ID (server generated). This uses an HTTP cookie and doesn’t require specific support from the player.

As above.

<vendor>-uid

Extended identifier for company specified in <vendor>.
ttd: TheTradeDesk (Unified ID 1.0)
uid2: The TradeDesk (Unified ID 2.0)
ramp: Identity Link.
id5: ID5.
pbjs: PubCommon.
nsf: Neustar Fabrick ID.
ltmpan: Lotame Panorama.

As above.

lat

Latitude of the listener's current location.

See Note 1, below.

Floating-point value: -90.0 to 90.0

long

Longitude of the listener's current location.

See Note 1, below.

Floating-point value: -180.0 to 180.0

age

Age of the listener, based on information obtained through listener registration.

Integer value: 1 to 125

gender

Gender of the listener, based on information obtained through listener registration.

“m” or “f” or “o” for male, female, or other (case-sensitive)

postalcode

Postal/ZIP code of the listener's home location, based on information obtained through listener registration. See Note 2, below.

Valid postal or ZIP code. E.g., 91403 or H3G 1R8

country

Country Code of the listener's home location, based on information obtained through listener registration. See Note 2, below.

ISO 3166-1 alpha-2 two-letter country code (e.g., US)

gpp *

X-gpp

GPP string allowing the transmission of privacy, consent, and consumer choice signals. The string must comply with the IAB Tech Lab Global Privacy Platform specification.

Url-safe base64-encoded GPP string.

gpp_sid *

X-gpp-sid

Section ID to indicates which legislation (i.e., section of the GPP string) is considered “in force”.

Integer

gdpr ^*

Flag indicating if General Data Protection Regulation (GDPR) regulations apply. GDPR was established by the European Parliament and the Council of the European Union.

0 = GDPR does not apply

1 = GDPR applies

gdpr_consent ^*

X-gdpr-consent

GDPR transparency and consent string encapsulating relevant details about how transparency and consent was established. The string must comply with the IAB Transparency and Consent Framework specifications.

URL-safe base64-encoded GDPR consent string.

us_privacy

U.S. Privacy String that signals whether or not the U.S. Privacy Regulations apply to the consumer, if an “explicit notice” legal disclosure has been established with a consumer, and if the consumer has chosen to opt out of the sale of their personal data. Version 1 only supports signals pertaining to the California Consumer Privacy Act (CCPA). The string must comply with the U.S. Privacy String format.

String

coppa

Flag indicating if Children's Online Privacy Protection Act (COPPA) regulations apply. COPPA was established by the U.S. Federal Trade Commission.

0 = COPPA restrictions do not apply

1 = COPPA restrictions apply

dist

This parameter is used to identify the distribution channel. (I.e., digital property where the listener accesses the audio content.)

String. Any string can be entered. Character limit is 50.

banners

Banner capabilities flags.

This item is currently used for statistical analysis by Triton Digital but is expected to assume a more direct role in the future.

String: comma-separated list of supported banner sizes. For example: banners=728x90,300x250

omid

Flag indicating if player supports the Open Measurement Interface Definition API (usually via the OMSDK), and which version. This parameter can only be provided via the partner token.

0 = OMID is not supported

1 = OMID 1.0 is supported

store-id

Only for mobile app inventory.

App store identifier for an installed app, used to locate the app within the specific store.

Example for iTunes:

store-id=726533955

Example for Google Play:

store-id=com.tritondigital.tritonradio

This parameter is required by programmatic buyers to verify Triton Digital is allowed to sell your inventory using the app-ads.txt framework.

String

bundle-id

Only used for mobile app inventory, where it is required.

Application identifier intended to be unique to the app and independent of the app store where it was distributed.

On Android and iOS, this should be a package name (e.g., com.tritondigital.tritonradio).

String

store-url

Only for mobile app inventory.

App store URL for an installed app making the ad request/stream connection.

The string must be URL encoded.

Example:

store-url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3F1d%3Dcom.tritondigital.tritonradio

This parameter is required by programmatic buyers to verify Triton Digital is allowed to sell your inventory using the app-ads.txt framework.

URL encoded string of a URL.

agent

The specific agent/player (software) that is used to play the audio stream/file.

String. To obtain valid values for your agent/player, contact your Triton Digital account manager.

agent-family

The type/family that best describes a specific agent/player.

String. Valid values are:

browser
monitoring
player-custom
player-generic
podcast

agent-device

The specific device (hardware) that is used to play the audio stream/file. Although this is optional, Triton Digital recommends using it, since the device can’t always be derived properly from the default "user agent" header.

String.

agent-device-family

The type/family that best describes a specific device.

String.

agent-os

The Operating System that is used to play the audio stream/file. Although this is optional, Triton Digital recommends using it, since the operating system can’t always be derived properly from the default "user agent" header.

String.

csegid

Custom Segment ID.

Before implementing this, contact Triton Digital Customer Support to enable Custom Segment ID Targeting in your account. Currently, Custom Segment ID Targeting only works with Tap advertising (it is not supported by Yield-Op).

Integer value: 1 to 1000000

ttag

X-ttag

Custom targeting tags that you can match independently in TAP or Yield-Op.

A suggested practice is to send a comma-separated list of tags, using a format such as <key>:<value> for each tag.

Example: ttag=vehicle:ford,vehicle:suv

Note that the use of a comma-separated tag list and key:value pairs based on a colon separator ( : ) is just a suggestion; other characters will also work, although some special characters might cause problems and spaces should not be used. Also, commas ( , ) are not a good choice within each tag because the TAP user inteface where TTags are entered for flight targeting interprets commas as tag separators, making it difficult for traffickers to enter a tag such as vehicle,ford (it would be interpreted as two separate tags; vehicle and ford).

See TTags Usage Example.

Alphanumeric characters plus UTF-8 symbols. Note that "&" and "=" are not valid characters.

dmp-segments

X-dmp-segments

Identifiers for third-party DMP segments which the listeners belong to.

CSV list of segment IDs. For example:
dmp-segments=46,47,48,49,50,52,53,54,55

N/A.

X-DMP-Segment-IDs

Identifiers for third-party DMP segments which the listeners belong to.

This version of the segments parameter is only used for specific DMP integrations that leverage the player and/or SDK. For more information about when and how to use this feature, speak with your Triton Digital Client Success Manager.

This parameter is not supported in partner token or HTTP query string.

DMP name (e.g., "dmp_1_name") and comma-separated segment IDs (e.g., 123,234,345).

Example for the DMP Blork Audience with segment IDs 1234 and 5678: and DMP ACME Segmenter with segment IDs 4321 and 8765:

{"blork_audience":[1234,5678], "acme_segmenter":[4321,8765]}