Table of contents
Notifications
Any time an auction is held, a server-to-server call should be sent back to Criteo to report results (win/loss and reason). This allows Criteo to achieve three goals:
Identify the reason why the auction has been lost and take this information into account in the upcoming bids
Detect in real-time any issues that may occur and react quickly to resolve them.
Be able to monitor the spend in real-time.
For analysis purposes, a client-side or server-side call can be done using Billing URL.
Notifications - Implementation of burl (Billing Notifications)
Notifications - Implementation of nurl (Win Notifications)
Win notifications must be triggered server-side to notify Criteo of a win.
For information, if necessary, the notification of a win can also be done using lurl
with the ${AUCTION_LOSS}
macro replaced by 0
.
Notifications - Implementation of lurl (Bid Loss Notifications)
For a better flexibility, Criteo supports two ways of implementing bid loss notifications:
HTTP GET CALL
For each impression, Criteo can send an optional field lurl
in the bid response which contains a bid loss URL with all the required parameters. Then you just need to call this url after replacing the following macros:
The status macro
${AUCTION_LOSS}
The winning bid macro:
${WINNING_BID}
The clearing price macro:
${CLEARING_PRICE}
Notifications - Latency
As mentioned earlier, one of the goals of bid loss notifications is to help in real time monitoring and quickly detect creative or technical issues when they occur. This is why we require that the latency between a bid request and its corresponding notifications to be less than 60 seconds
Notifications - Aggregation
In some cases it might be more convenient for our partners to send us bid loss notifications in buckets, which means using one notification request to send the loss notifications of several bid requests. This can be achieved using the HTTP POST implementation.
Please contact us if you would like to implement this feature.
Notifications - Status List
Status List
Status | Description |
---|---|
0 | Bid Won |
1 | Internal Error |
2 | Impression Opportunity Expired |
3 | Invalid Bid Response |
4 | Invalid Deal ID |
5 | Invalid Auction ID |
6 | Invalid Advertiser Domain |
7 | Missing Markup |
8 | Missing Creative ID |
9 | Missing Bid Price |
10 | Missing Minimum Creative Approval Data |
100 | Bid was Below Auction Floor |
101 | Bid was Below Deal Floor |
102 | Lost to Higher Bid |
103 | Lost to a Bid for a PMP Deal |
104 | Buyer Seat Blocked |
200 | Creative Filtered - General; reason unknown. |
201 | Creative Filtered - Pending processing by Exchange (e.g., approval, transcoding, etc.) |
202 | Creative Filtered - Disapproved by Exchange |
203 | Creative Filtered - Size Not Allowed |
204 | Creative Filtered - Incorrect Creative Format |
205 | Creative Filtered - Advertiser Exclusions |
206 | Creative Filtered – App Bundle Exclusions |
207 | Creative Filtered - Not Secure |
208 | Creative Filtered - Language Exclusions |
209 | Creative Filtered - Category Exclusions |
210 | Creative Filtered - Creative Attribute Exclusion |
211 | Creative Filtered - Ad Type Exclusions |
212 | Creative Filtered - Animation Too Long |
213 | Creative Filtered - Not Allowed in PMP Deal |
1000 | Criteo Specific - Assetsurl Timeout |