Testing
Test requests
Section titled “Test requests”Set test to 1 in the bid request:
{ "id": "4f1c2b7e-9a3d-4c55-8e21-6b0f3a9d7c10", "test": 1, "imp": [ ... ]}Elo answers every test request with a bid for the same test ad, titled
“Test ad”, so you can check your integration before live demand. Test
requests get it before Elo turns bidding on for your key too. The bid’s price is the request’s imp.bidfloor, or
0.01 USD when the request has no floor. The request does not need keywords
or categories to get it.
The bid has the same fields and the same notice, pixel and click URLs as a
live bid. You can call every URL in a test bid. Elo stores those events as
test events and never bills a test bid, even when you call its burl.
Check a test bid
Section titled “Check a test bid”- Send the example bid request with your
publisher API key. It already has
"test": 1. - Expect
200and a bid like the example bid response, with the test ad. A204means no bid: the request hasregs.coppaset to 1, you are over your request rate limit, or the test ad lacks an asset you markedrequired. See No bid and errors. - Parse
admand check that each asset you markedrequiredis answered under itsid. - Call
nurl, thenburl, with${AUCTION_PRICE}replaced by a price at or below the bid. Each answers204. - Load the impression pixel. It answers
200with an image. - Open the click link in a browser. It redirects to an Elo docs page.
Request rate limit
Section titled “Request rate limit”Elo gives you a request rate limit, in requests per second, when it turns
bidding on. Requests above it get 204. Keep your traffic, test requests
included, under that limit. Before bidding is on, test requests have a limit
of 100 per second.