faq - Unity-Technologies/unity-ads GitHub Wiki
/* Title: Frequently asked questions Description: Frequently asked Unified Auction questions Sort: 9 */
Unity recommends but does not require obfuscation for integration with the exchange. Price obfuscation ensures a secure method of passing sensitive price information back to the partner, but omitting it will not impede the integration process.
All global traffic is routed to a US-EAST data center located in Virginia.
Unity counts impressions when the ad is rendered. Unity pre-caches, then fires the nURL
and impression pixel at the same time the ad renders.
Unity’s time to live (TTL) is 120 minutes for all formats.
Yes. For more information, see the Loss notifications section of the Optimization features documentation.
The default threshold is 200 ms, though Unity is able to extend that in certain circumstances (for more information, contact your account manager).
Yes. All URLs that Unity is expected to fire must be TLS-compliant and have an https://
prefix.
Yes, Unity is able to send GZIP requests, and by default requires partners to send GZIP responses back. This helps with bandwidth and optimizing costs.