QORA receives traffic from connected publishers, matches it against active campaigns, and decides in real time where each impression or click should go. This page explains what happens along the way.
A publisher's zone, tag or RTB endpoint sends the request with its format, GEO and device.
Traffic quality rules and source controls decide whether the request is eligible at all.
Eligible campaigns are selected by format, targeting and remaining budget.
Bids and campaign pacing determine which campaign is served and at what price.
Impressions, clicks and conversions are recorded and reported back to both sides.
Every campaign and every traffic source runs through the same four layers.
Each request is routed to the campaign that fits its format, GEO and targeting, within that campaign's budget. Advertisers set the requirements; publishers' traffic is matched against them without manual placement by placement work.
Bids and daily budgets are managed per campaign, with pacing that spreads spend across the day instead of exhausting it early. Automatic bid optimization works toward the campaign's cost-per-action goal on CPA campaigns.
Traffic filtering runs before a request is matched, and advertisers control which sources their campaigns run on through source-level allow and block lists. Publishers see which of their sources are delivering.
Impressions, clicks and conversions are tracked per campaign and per source. Conversions arrive through server-to-server postbacks from the advertiser's tracker; reports are available to both sides in the platform.
How traffic enters and how results leave the platform.
app.qoraplatform.com. New accounts are reviewed before the first campaign or source goes live.Create an account to set up your first campaign or connect your first source. Questions about an integration go straight to the team.