Back to Bidders
Kidoz
Features
Bidder Code |
kidoz |
Prebid.org Member |
no |
Media Types |
display |
GDPR TCF Support |
yes |
User IDs |
none |
USP/CCPA Support |
no |
Supply Chain Support |
no |
COPPA Support |
yes |
Demand Chain Support |
no |
GPP Support |
no |
Supports Deals |
check with bidder |
Prebid.js Adapter |
no |
IAB GVL ID |
check with bidder |
Prebid Server Adapter |
yes |
Floors Module Support |
no |
First Party Data Support |
check with bidder |
Multi Format Support |
check with bidder |
ORTB Blocking Support |
check with bidder |
Safeframes OK |
check with bidder |
|
|
"Send All Bids" Ad Server Keys
These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_kidoz |
hb_bidder_kidoz |
hb_adid_kidoz |
hb_size_kidoz |
hb_source_kidoz |
hb_format_kidoz |
hb_cache_host_kidoz |
hb_cache_id_kidoz |
hb_uuid_kidoz |
hb_cache_path_kidoz |
hb_deal_kidoz |
|
Registration
Kidoz is exclusively for Mobile app COPPA compatible ads, 100% kid relevant and appropriate.
In order for a company to receive bids from Kidoz, they must first open a publisher account at Kidoz.net
(https://accounts.kidoz.net/publishers/register) and accept the Kidoz Terms and Conditions and Privacy Policy.
Kidoz publishers must confirm that all of their content properties are COPPA and GDPR compliant and perform no monitoring
or tracking of U13 users in their operations. New publishers are provided a Publisher ID and AccessToken, this can also
be used to login to their dashboard at the Kidoz.net portal to monitor their account activity.
Bid Params
Name |
Scope |
Description |
Example |
Type |
access_token |
required |
Kidoz access_token |
‘123abc’ |
string |
publisher_id |
required |
Kidoz publisher_id |
‘44444’ |
string |
Back to Bidders