Getting startedIntegration Preview
Introduction
Learn how the ReinoAds rule-based ad decision engine works, its core concepts, and how to read this documentation.
Integration Preview
This documentation is an Integration Preview. Endpoints, field names and SDK package names are illustrative; integration documentation tailored to your account is shared once your account is approved.
ReinoAds is an ad decisioning platform where publishers define the rules and every ad request is evaluated against them. When your app, game or website requests an ad for a slot, the ReinoAds Decision Engine runs the request through a sequence of checks and only serves an ad that passes all of them.
The decision pipeline
- Policy check: the request is matched against the publisher rules you defined for the placement and audience.
- Commercial check: sponsor conflicts and competitor restrictions are evaluated, so a club sponsor's competitor never appears in the same slot.
- Brand safety: category rules, advertiser approval and creative approval are enforced.
- Source eligibility: controlled inventory (direct deals, sponsorships) is tried first, then only the restricted programmatic demand sources the publisher has allowed.
- Outcome: an ad is served, a house ad is shown, or no ad is shown. The engine fails closed: when in doubt, nothing is served.
| Concept | Description |
|---|---|
| Placement | The slot where an ad is shown. Formats, policy and allowed sources are configured per placement. |
| Decision | The result the Decision Engine produces for a single ad request, together with its reason. |
| Policy | A named rule set made up of category, advertiser, creative and source rules. |
| Audience signal | Segment IDs the publisher derives from permissioned first-party data. |
| House ad | The publisher's own promotional content, shown when no eligible ad is available. |
| Kill switch | An emergency stop that instantly disables a source, advertiser or placement. |
Who this is for
Mobile, web and game developers responsible for ad integration, and backend teams building server-side decisioning, reporting and webhook handling.