On this page, you will find frequently asked questions about Smaato and the Smaato Exchange.
How can I integrate with Smaato?
OpenRTB is the main integration process for working with the Smaato Exchange:
- If you are a demand-side platform (DSP), Please visit our OpenRTB Getting Started page here in the developer documentation.
- If you are an ad network please contact our Support Team for further integration assistance.
I am neither an ad network, nor a DSP. How can I work with Smaato?
If you are a brand, ad agency, advertiser, media buyer, trading desk, or any other buy-side entity, please note that we do have a dedicated team to assist you with buying on the Smaato Exchange through your preferred bidders or DSP.
What is Smaato’s timeout setting?
The Smaato auction timeout rate for DSPs is 250 ms for US and EMEA auctions. For APAC and CN the timeout rate is 650 ms for auctions.
We recommend demand partners to optimize their response time to 100 ms. This increases the efficiency of the partnership and provides access to our latency-sensitive inventory.
Where are Smaato’s servers based?
- North Virginia (US)
- Ireland (EMEA)
- Singapore (APAC)
- China North (CN)
Why can’t I ping Smaato’s servers?
Smaato is set behind a load balancer which disables pinging. We can, however, ping you in order to test server latency if you provide us your bidding URL.
What’s the standard Bid Response size limit?
6144 bytes is the current limit. Please reach out to your Smaato Account Manager if you need the limit to be increased.
What does QPS stand for?
Queries per second; this integer defines the amount of traffic queries (ad requests, bid requests) a demand partner receives per second. By default, QPS values are not limited; limiting QPS may reduce Smaato’s infrastructure burden and increase a DSPs effectivity.
How frequently is data updated in reporting?
Every hour; currently the data is available with a delay of roughly 3 hours, which will decrease in the future.
Modified: July 15, 2019 at 11:23 am