TinyTag Request / Ad Call
A TinyTag ID is associated to various static data in the Xandr database. Some of the parameters associated with the TinyTag can be dynamically added or overwritten at the time of the TinyTag Request, or ad call.
Identification either by ID or by member and code (see Calling TinyTags Via Codes instead of ID below) are required parameters in a TinyTag. Size is also required if it was not pre-associated with the TinyTag ID. All other parameters are optional.
The ID generated by the Tinytag Service.
Instead of ID, a TinyTag can be referenced by the member ID and "inv_code".
Same as "code" from the TinyTag Service. Can be used to reference a TinyTag along with "member".
Created via the Member Service, this is the default ID if the member is known but the "inv_code" is not. This parameter can also be used to override a preset default_tag_id.
Publisher-supplied URL for third-party click tracking.
If you include the
Used to run a debug impression. Note that in a debug impression, notify requests will not be sent and
Used to run a test auction. Xandr does not transaction the impression in a test auction and nothing is logged. The content of the ad is also ignored.
Used on a debug impression to direct the bid request to a specific bidder instance. Set debug_node to the id of the bidder instance from the Bidder Instance Service.
Required if not already set on the TinyTag. This parameter will NOT override a preset size format; widthXheight.
The URL of the page containing the TinyTag. Note: If Xandr detects that this URL misrepresents the inventory (i.e., it is not the actual URL for the impression), we may turn off this feature for the TinyTag. For more details about prohibited sell-side practices, see Policies for Selling.
Can pass numerical age, birth year, or hyphenated age range.
Possible values: m, f for male, female
The reserve price for this inventory. This parameter WILL override a preset price.
Arbitrary data that will be passed verbatim to the bidder (optional)
Does the user have flash installed? Possible values: 1 or 0.
Will this ad ever be served inside an iframe? Possible values: 1 or 0.
Maximum time (in milliseconds) that the impression bus will wait for bid responses after the bid request is sent. Bidders that do not respond within the timeout window will receive a "Connection throttled, failed, or timed out" error. The value used in production (and default in the sand environment) is 2000 ms, but may be overridden in the sand environment by passing in a different value for timeout. Note: The timeout override is only used when running a debug impression.
The position of the tag on the page. Possible values: 'above' (above the fold) or 'below'.
Indicates if non-deal RTB should be blocked. Possible values:
Indicates if all deals should be blocked. Possible values:
TinyTag using only ID:
TinyTag passing additional info:
Dynamic data: age=29, gender=male
TinyTag with query string data.
Note: If you're passing querystring variables into the qsdata parameter, be sure to encode the string of data as shown here.
Calling TinyTags Via Codes instead of ID
In situations where a TinyTag cannot be called via the TinyTag ID, you can call a TinyTag by a member-defined field called "inv_code". This alphanumeric code is with the TinyTag Service.
A sample TinyTag code call: