הדף שביקשת עדיין לא זמין בשפה שלך. אפשר לבחור שפה אחרת בחלק התחתון של הדף, או להיעזר בתכונת התרגום המובנית של Google Chrome לצורך תרגום מיידי של כל דף אינטרנט לשפה שבוחרים.

Real-time bidder integration for mobile apps

If you use real-time bidder (RTB) and want to target ads to mobile applications, ensure you're developing your bidder using the latest protocol buffer, along with the following requirements.

Pre-requisites for RTB buyers

The existing RTB protocol and trading locations are used to send in-app and mobile-web traffic. There is no need to change your bidder URL.

If you're already an RTB buyer, update your protocol buffer to the latest version and implement the related fields outlined in the RTB developer documentation. For further information and support please contact your Authorized Buyers representative.

Set up pretargeting

To receive mobile app inventory, set up a pretargeting group with a placement-holder ad in the mobile ad size and update your RTB settings to confirm you can send big requests.

  1. Sign in to Authorized Buyers.

  2. Create a new pretargeting group.
  3. In the Environment section, all settings are automatically included. Select whether to: include all, exclude all, or target specific mobile apps.
  4. In Settings, by default all operating systems are included. Click Platform and then Mobile to include mobile platform and exclude other platforms.
  5. Click Bidder settings and then RTB settings.
  6. If not already enabled, turn on "Real-time feedback for bid requests".

App targeting selections have an OR relationship with each other and an AND relationship with all other pretargeting configurations.

Once you've implemented the mobile-related fields in your bidder and set up a pretargeting group, you'll start receiving mobile traffic.

For additional support please contact your Authorized Buyers representative.

Track impressions

To minimize reporting discrepancies, app ads (banners, interstitials, and native) should be tracked with impression_tracking_url. App video impressions should still be tracked with VAST XML.

Ad buyers should remove impression tracking pixels from the creative (ad markup), and instead include the impression_tracking_url field in the bid response. Impression_tracking_url fires when the impression is considered billable. This is more accurate than tracking pixels, which can track impressions that (because of prefetching) were fetched by the app, but never rendered.

impression_tracking_url Proto example

// The URLs to call when the impression is rendered. This is supported for
// all inventory types and all formats except for VAST video.
repeated string impression_tracking_url = 19;

impression_tracking_url is also available as an extension for bidders that use OpenRTB:

// Ad Exchange extensions for the Bid object.
  message BidExt {
// [AdX: BidResponse.Ad.impression_tracking_url]
  repeated string impression_tracking_url = 1;
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

חיפוש
ניקוי החיפוש
סגירת החיפוש
אפליקציות Google
תפריט ראשי
Search Help Center
true
71030
false