GFY Bid — the OpenRTB 2.5 exchange for popunder traffic
Publishers send bid requests, advertisers answer with bids, and money moves only on confirmed impressions. One clean protocol, honest first-price auctions and billing records you can reconcile.
- Endpoint issued per partner
- Billing on burl only
- Servers in France
- OpenRTB 2.5
- JSON over HTTPS
- First-price auction
- USD CPM
- Popunder
- Reporting API
Monetize popunder traffic over a standard OpenRTB feed
Send us OpenRTB 2.5 bid requests and get first-price bids back. You are paid for impressions confirmed by our billing notice — nothing else is counted, nothing is counted twice.
Plain OpenRTB 2.5
JSON over HTTPS to your own endpoint. No SDK, no special fields: the request you already send to other buyers works.
First-price, in USD
The price in our bid is the final CPM — exactly what you bill. Your bidfloor is respected.
Paid on confirmed impressions
Fire our billing notice (burl) when the impression is shown. Each one is stored before we answer; a repeated call never counts twice.
Reporting API
Requests, bids, wins, impressions and money by day or hour, in your time zone, with your own API key.
QPS caps and filters per feed
We agree a requests-per-second cap for your feed and can filter traffic by country, OS and version, browser, device type, domain and site — so you only send what is bought.
Buy popunder traffic with a clean integration
We send you OpenRTB 2.5 bid requests for popunder impressions and you answer with bids, as usual. You pay only for impressions confirmed by your own billing notice.
- Requests as the publisher sent themSite, device, user and extensions are passed through; only the floor may be adjusted.
- Billing only on your burlNo burl call — no charge. Delivery is automatic, with retries for up to 5 minutes.
- Targeting filtersCountry, OS and version, browser, device type, domain and site — allow or block lists per feed.
- Your QPS cap, respectedWe never send more requests per second than agreed with you.
Statistics updated every minute
Requests sent to you, bids you returned, wins, billed impressions and spend — by day or hour, through the reporting API with your own key.
- Near real timeCounters are updated every minute.
- Your data onlyEach key sees only its own feed. Lost a key? We revoke it at once and issue a new one.
- Daily reconciliationGive us a read-only reporting key and we compare our numbers with yours every day.
From first message to live traffic in four steps
Tell us about you
Send the form below: publisher or advertiser, your traffic or budget, the geos you work with.
Get your endpoint
We issue a personal endpoint or set up yours, and agree the QPS cap, filters and billing notice domains.
Test and go live
We check requests and responses together on a small volume, then switch the feed on.
Track and reconcile
Follow your numbers in the reporting API; we reconcile with your reports every day.
Standard protocol, no surprises
The full field-by-field reference is in the documentation.
| Protocol | OpenRTB 2.5, JSON over HTTPS (POST) |
|---|---|
| Ad format | Popunder — adm is the landing URL |
| Auction | First price (at = 1) |
| Currency | USD, CPM |
| Time limit | tmax up to 250 ms |
| No bid | HTTP 204 |
| Billing | Billing notice (burl) only |
| Endpoint | Issued per partner |
| Reporting | API at api.gfybid.com, a key per partner |
{
"id": "6b0f3e2a9c1d4f7e8a5b2c3d4e5f6a7b",
"imp": [{
"id": "1",
"instl": 1,
"bidfloor": 0.01,
"bidfloorcur": "USD",
"secure": 1
}],
"site": {"id": "1001", "domain": "example.com"},
"device": {
"ua": "Mozilla/5.0 (Linux; Android 14)",
"ip": "203.0.113.10",
"geo": {"country": "DEU"}
},
"at": 1,
"tmax": 250,
"cur": ["USD"]
}{
"id": "6b0f3e2a9c1d4f7e8a5b2c3d4e5f6a7b",
"seatbid": [{"bid": [{
"impid": "1",
"price": 0.0388,
"adm": "https://go.example.net/r/…",
"burl": "https://burl.example.net/b/…"
}]}],
"cur": "USD"
}Built for speed — and for accurate billing
Every bid is answered in milliseconds, and every confirmed impression becomes a durable billing record before we say “OK”.
p99 response time at 15,000 requests per second in our load tests
Two relay instances behind a load balancer; releases without downtime
Billing notices are delivered automatically, with retries for up to 5 minutes
Dedicated servers in Europe
Our servers are in France, a short network hop from the main European ad-tech hubs.
Durable billing records
Each billing notice is written to the database before we answer it. A repeated notice is recognised and never billed twice.
Daily backups
The database is backed up every day, with continuous change archiving, and restores are tested.
Load-test figures were measured on our production hardware with simulated partners; real-world latency also depends on the network between you and us.
Ready to trade popunder traffic?
Tell us what you have or what you are looking for — we will get back to you.
Let’s talk
Prefer e-mail? Write to us directly:
manager@gfybid.com- 1You send the formA few lines about your traffic or your budget are enough.
- 2A manager repliesBy e-mail, or in Telegram / Skype if you leave a contact.
- 3We set up a testEndpoint, limits and filters — then a small test volume.