![](data:image/svg+xml,<svg display="block" id="3173472232" role="presentation" viewBox="0 0 32 32" xmlns="http://www.w3.org/2000/svg"><g fill="transparent" height="25px" id="NifBl5lNk" transform="translate(3 3)" width="26px"><path d="M 4.951 0 L 0 0 L 0 14.974 C 0 15.634 0.128 16.287 0.377 16.897 C 0.626 17.507 0.991 18.061 1.45 18.528 C 2.379 19.471 3.639 20 4.951 20 C 4.951 21.327 5.47 22.599 6.394 23.536 C 7.318 24.474 8.571 25 9.876 25 L 19.805 25 L 19.805 20 L 4.951 20 Z" fill="rgba(238, 238, 238, 0.93)" height="25px" id="qjLpusG8R" width="19.8046875px"/><path d="M 19.703 10.028 C 19.703 7.25 17.498 5 14.777 5 C 14.778 3.675 14.262 2.403 13.342 1.464 C 12.425 0.527 11.178 0 9.877 0 L 0 0 L 0 5 L 14.777 5 L 14.776 25 L 19.703 25 Z" fill="rgba(238, 238, 238, 0.93)" height="25px" id="Vk5eH6tpr" transform="translate(6.297 0)" width="19.703125px"/></g></svg>)
Changelog
v1.0.0
OpenAI Ads Support
NEW
Gateway now supports OpenAI Ads as a conversion destination. Conversions attributed to OpenAI can be sent server-side with the identifiers, attribution, and consent matched by Radar and Hub.
OpenAI Ads is now part of the same conversion workflow as our existing destinations, including attribution-aware routing, validation, response tracking, deduplication, and automatic retries.
Updates on new features and releases.
