Post-bid Parameters

Pinokio’s detection tags carry data about each impression as URL parameters. Most of them you populate from your ad server when you serve the tag; a few are detected automatically by the tag itself.

The reference below covers every parameter the tag accepts. Where a parameter has the same meaning in Pre-bid, the names are aligned so you can populate both calls from the same source.

Parameter string format

The tag URL accepts parameters as a standard query string — key=value pairs separated by &:

p={p}&pub={pub}&k={k}&node={node}&uid={uid}&ifa={ifa}&app={app}&dmn={dmn}
  &ref={ref}&sid={sid}&adt={adt}&dvt={dvt}&rat={rat}
  &aap={aap}&aar={aar}&acp={acp}&apd={apd}
  &cmp={cmp}&adv={adv}&plc={plc}&cre={cre}&cb={cb}&dim={dim}&aid={aid}
  &geo={geo}&ip={ip}&ua={ua}
  &p1={p1}&p2={p2}&p3={p3}&p4={p4}&p5={p5}

Note

For any parameter where no value is available — null, unknown, not applicable — pass an empty string. For example, &apd=&geo=US is correct when apd is unknown.

Identification

Parameter	Required	Description
p	Yes	Pinokio Partner ID. The unique ID of your Pinokio account.
pub	Yes	Publisher ID of the traffic source. Matches the OpenRTB Publisher ID and field #2 in ads.txt.
k	Yes	API key.
node	Yes	Server ID — identifier for the bidder or prebid instance serving the impression.

User and device

Parameter	Required	Description
ua	Yes	User agent string. URL-encoded.
ip	Yes	IP address of the user.
uid	Yes	Unique user identifier. For web, the cookie or other user ID. For mobile and CTV use ifa instead.
ifa	Conditional	Device ID — IDFA on iOS, AAID on Android, RIDA on Roku, and so on. Required for mobile and CTV traffic.

Source

Parameter	Required	Description
dmn	Conditional	Domain where the impression occurred. Required for web traffic. Full domain including TLD; exclude the protocol and path.
app	Conditional	App ID / bundle ID. Required for in-app mobile and CTV traffic.
ref	No	Referring URL, when available.
sid	Yes	Supplier ID — domain of the supplier, seller, or exchange. Matches field #1 in ads.txt.

Inventory

Parameter	Required	Description
adt	Yes	Ad type. Integer: 1 Banner, 2 Video, 3 Audio, 4 Native.
dvt	Yes	Device type. See device type values.
rat	No	Rendered ad type. See rendered ad type values.

Video / audio specifics

These apply only to video and audio inventory. Pass an empty string for non-video, non-audio impressions.

Parameter	Required	Description
aap	No	Auto-play. Whether the ad started playing without user interaction. 0 no, 1 yes, empty string unknown.
aar	No	Auto-refresh interval, in seconds. How long the ad plays before auto-refreshing to another ad. Includes pause time. Examples: 5, 7.5, 15, 30, 60.
acp	No	Continuous play. Whether the next clip plays automatically after the current one ends. 0 no, 1 yes, empty string unknown.
apd	No	Forced duration, in seconds. How long the ad plays before the user can skip. Use 0 if the ad is immediately skippable. Examples: 0, 5, 15, 30.

Campaign and creative

Parameter	Required	Description
cmp	No	Campaign ID. Your campaign identifier — any format your tracking system uses.
adv	No	Advertiser ID. The advertiser that bought the traffic.
plc	No	Placement ID.
cre	No	Creative ID.
cb	No	Cache buster. Random value generated per request to force the browser to load the tag fresh instead of from cache. Regenerate on every call.
dim	No	Creative dimensions, in pixels. Format: {Width}x{Height}. Example: 300x250.
aid	No	Ad ID. Unique identifier for the creative.

Geo

Parameter	Required	Description
geo	Yes	ISO 3166-1 alpha-2 country code where the impression originated. Examples: US, GB, JP.

Custom reporting dimensions

Parameter	Required	Description
p1–p5	No	Custom reporting dimensions. Pass whatever values you want to group reports by, for example your internal Endpoint IDs.

Caution

p1–p5 are reporting dimensions, not unique identifiers. Do not pass a value that is unique per request (like a UUID or transaction ID) — that defeats the grouping and will inflate report cardinality. Use them for low-cardinality dimensions you actually want to slice on.

---

Reference tables

Device type values

Used by dvt. Aligned with OpenRTB 2.6 / AdCOM 1.0.

Value	Meaning
1	Mobile / tablet (legacy combined category)
2	Personal computer (desktop / laptop)
3	Connected TV
4	Phone
5	Tablet
6	Connected device (Roku, Apple TV, Fire TV, consoles)
7	Set-top box
8	Digital out-of-home (DOOH)

Rendered ad type values

Used by rat. Interpretation depends on the media type (adt).

Value	Display	Video	Audio	Native
0	Unknown	Unknown	Unknown	Unknown
1	Rich media	—	—	Rich media
2	Static	—	—	Static
3	—	Skippable in-stream	Skippable in-stream	—
4	—	Non-skippable in-stream	Non-skippable in-stream	—
5	—	Video discovery	—	—
6	—	Bumper	—	—
7	—	Outstream	—	—
8	—	Masthead	—	—

For example, a rich-media display unit is adt=1, rat=1. A non-skippable in-stream video is adt=2, rat=4.