Route placement traffic safely
Use the placement-scoped redirect contract while preserving replay protection and transparent traffic sourcing.
Built forPublisher developers
Smartlink request
The implemented path is GET /r/:placement_id. A valid request receives an HTTP 302 to an eligible campaign or the configured safe fallback.
Example URL
https://redirect.example.invalid/r/placement_example?publisher_id=publisher_example&request_id=request_unique_10001&visitor_id=session_scoped_value&country=US&device_type=mobileRequest context
- placement_id identifies approved inventory and is part of the path.
- publisher_id scopes the publisher context.
- request_id should be unique for each routing attempt; reuse returns the cached decision during the duplicate window.
- visitor_id should be purpose-limited and placement/session scoped. It is hashed before event storage.
- Country, device, operating-system, browser, and telemetry context are optional and must not be fabricated.