diff --git a/_data/sidebar.yml b/_data/sidebar.yml index 75b1560aec..251b00300a 100644 --- a/_data/sidebar.yml +++ b/_data/sidebar.yml @@ -85,7 +85,7 @@ - sbSecId: 0 title: Contributing - link: /contributing/contribute.html + link: /policies/contribute.html isHeader: 0 isSectionHeader: 0 sectionTitle: @@ -93,7 +93,7 @@ - sbSecId: 0 title: Prebid.org IP Policy - link: /overview/ip-policy.html + link: /policies/ip-policy.html isHeader: 0 isSectionHeader: 0 sectionTitle: @@ -101,7 +101,15 @@ - sbSecId: 0 title: Privacy Policy - link: /privacy.html + link: /policies/privacy.html + isHeader: 0 + isSectionHeader: 0 + sectionTitle: + subgroup: 2 + +- sbSecId: 0 + title: Antitrust Policy + link: /policies/antitrust.html isHeader: 0 isSectionHeader: 0 sectionTitle: @@ -109,7 +117,7 @@ - sbSecId: 0 title: Cookies - link: /cookies.html + link: /policies/cookies.html isHeader: 0 isSectionHeader: 0 subgroup: 2 @@ -146,7 +154,7 @@ subgroup: 0 - sbSecId: 1 - title: Getting Started + title: Getting Started for Developers link: /dev-docs/getting-started.html isHeader: 0 isSectionHeader: 0 @@ -210,6 +218,14 @@ sectionTitle: subgroup: 1 +- sbSecId: 1 + title: Running without an ad server + link: /dev-docs/examples/no-adserver.html + isHeader: 0 + isSectionHeader: 0 + sectionTitle: + subgroup: 1 + - sbSecId: 1 title: Legacy Browser Example link: /dev-docs/examples/legacy-browser-example.html @@ -1324,7 +1340,7 @@ subgroup: 2 - sbSecId: 3 - title: 'Guide to Prebid in Ad Manager' + title: 'Line Item Setup' link: /adops/step-by-step.html isHeader: 0 isSectionHeader: 0 @@ -1332,55 +1348,48 @@ subgroup: 2 - sbSecId: 3 - title: 'Ad Manager Send All Bids' - link: /adops/send-all-bids-adops.html + title: 'Creative Setup: Banner/Outstream/AMP' + link: /adops/gam-creative-banner-sbs.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: 'Setting up for AMP in GAM' - link: /adops/setting-up-prebid-for-amp-in-dfp.html - isHeader: 0 - isSectionHeader: 0 - sectionTitle: - subgroup: 2 - -- sbSecId: 3 - title: 'Setting up Multi-Format in GAM' - link: /adops/setting-up-prebid-multi-format-in-dfp.html + title: 'Creative Setup: Native' + link: /adops/gam-native.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: 'Setting up Native in GAM' - link: /adops/gam-native.html + title: 'Creative Setup: Video' + link: /adops/setting-up-prebid-video-in-dfp.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: 'Setting up Video in GAM' - link: /adops/setting-up-prebid-video-in-dfp.html + title: "Freewheel" + link: isHeader: 0 isSectionHeader: 0 + isCatHeader: 1 sectionTitle: subgroup: 2 - sbSecId: 3 - title: 'Setting up Long-Form Video in GAM' - link: /adops/setting-up-prebid-ott-video-in-gam.html + title: 'Setting up Long-Form Video' + link: /adops/setting-up-prebid-video-in-freewheel.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: "Freewheel" + title: "AppNexus Publisher" link: isHeader: 0 isSectionHeader: 0 @@ -1389,15 +1398,15 @@ subgroup: 2 - sbSecId: 3 - title: 'Setting up Long-Form Video' - link: /adops/setting-up-prebid-video-in-freewheel.html + title: 'Setting up Prebid' + link: /adops/setting-up-prebid-with-the-appnexus-ad-server.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: "AppNexus Publisher" + title: "Smart Ad Server" link: isHeader: 0 isSectionHeader: 0 @@ -1407,14 +1416,14 @@ - sbSecId: 3 title: 'Setting up Prebid' - link: /adops/setting-up-prebid-with-the-appnexus-ad-server.html + link: /adops/setting-up-prebidjs-with-Smart-Ad-Server.html isHeader: 0 isSectionHeader: 0 sectionTitle: subgroup: 2 - sbSecId: 3 - title: "Smart Ad Server" + title: "Other Ad Servers" link: isHeader: 0 isSectionHeader: 0 @@ -1423,8 +1432,8 @@ subgroup: 2 - sbSecId: 3 - title: 'Setting up Prebid' - link: /adops/setting-up-prebidjs-with-Smart-Ad-Server.html + title: 'General Ad Server Setup' + link: /adops/adops-general-sbs.html isHeader: 0 isSectionHeader: 0 sectionTitle: @@ -1455,14 +1464,6 @@ sectionTitle: subgroup: 3 -- sbSecId: 3 - title: Reduce Header Bidding Latency With Prebid.js - link: /overview/how-to-reduce-latency-of-header-bidding.html - isHeader: 0 - isSectionHeader: 0 - sectionTitle: - subgroup: 3 - #--------------Prebid Video--------------| - sbSecId: 4 @@ -1804,14 +1805,6 @@ sectionTitle: subgroup: 2 -- sbSecId: 4 - title: 'Radiant' - link: /examples/video/outstream/pb-ve-outstream-radiant.html - isHeader: 0 - isSectionHeader: 0 - sectionTitle: - subgroup: 2 - - sbSecId: 4 title: 'No Server' link: /examples/video/outstream/pb-ve-outstream-no-server.html diff --git a/_includes/adops/adops-creative-declaration.html b/_includes/adops/adops-creative-declaration.html index e7fcc0d2a8..f4bd582cc2 100644 --- a/_includes/adops/adops-creative-declaration.html +++ b/_includes/adops/adops-creative-declaration.html @@ -1,10 +1,9 @@ As of August 2020, privacy regulations have changed such that new creatives entered in GAM may require a declaration of the ad technology provider. The first step is to note the domain you serve the creative from. The examples above offer the -use of the jsdelvr.com CDN. However, you may obtain the creative from a managed +use of the jsdelvr CDN. However, you may obtain the creative from a managed service or you may host it yourself. If you receive a warning from ad manager about "declaring self-created ad technology", you should be able to work around -this by editing the creative and filling out the "Associated Ad Technology Provid -ers" section as shown in this screen capture: +this by editing the creative and filling out the "Associated ad technology providers" section as shown in this screen capture:

Creative Declaration

diff --git a/_includes/adops/adops-gam-setup.html b/_includes/adops/adops-gam-setup.html deleted file mode 100644 index a3413c86c6..0000000000 --- a/_includes/adops/adops-gam-setup.html +++ /dev/null @@ -1,190 +0,0 @@ -
- -

Step By Step Guide to Google Ad Manager Setup

- -
-

(Sorry, YouTube videos aren't available with your cookie privacy settings.)

-

Cookie Settings


-
- - - - - - - - - -

Step 1. Add a line item

- -

In Google Ad Manager, create a new order with a $0.50 line item.

- -

Enter all of the inventory sizes that your website has.

- -

Inventory Sizes

- -

Because header bidding partners return prices, set the Line Item Type to Price priority to enable them to compete on price.

- -

Price Priority

- -


- -

Set the Rate to $0.50 so that this line item will compete with your other demand sources at $0.50 ECPM.

- -

Rate

- -


- -

Set Display Creatives to One or More since we’ll have one or more creatives attached to this line item.

- -

Set Rotate Creatives to Evenly.

- -

Display and Rotation

- -

Choose the inventory that you want to run header bidding on.

- -

By default, prebid.js will send the highest bid price to Google Ad Manager using the keyword hb_pb.

- -

This line item will capture the bids in the range from $0.50 to $1 by targeting the keyword hb_pb set to 0.50 in the Key-values section.

- -

You must enter the value to two decimal places, e.g., 1.50. If you don’t use two decimal places, header bidding will not work.

- -

Key-values

- -


- -

Step 2. Add a Creative

- -

Next, add a creative to this $0.50 line item; we will duplicate the creative later.

- -

Choose the same advertiser we’ve assigned the line item to.

- -

Note that this has to be a Third party creative. The “Serve into a Safeframe” box can be UNCHECKED or CHECKED (Prebid universal creative is SafeFrame compatible).

- -

Copy this creative code snippet and paste it into the Code snippet box.

- - - -
<script src = "https://cdn.jsdelivr.net/npm/prebid-universal-creative@latest/dist/creative.js"></script>
-<script>
-  var ucTagData = {};
-  ucTagData.adServerDomain = "";
-  ucTagData.pubUrl = "%%PATTERN:url%%";
-  ucTagData.targetingMap = %%PATTERN:TARGETINGMAP%%;
-  ucTagData.hbPb = "%%PATTERN:hb_pb%%";
-
-  try {
-    ucTag.renderAd(document, ucTagData);
-  } catch (e) {
-    console.log(e);
-  }
-</script>
-
- -

New creative

- -

Make sure the creative size is set to 1x1. This allows us to set up size override, which allows this creative to serve on all inventory sizes.

- -

Note that safeframes don’t work with older versions of Prebid.js (v1.23 and before) in combination with recent versions of Prebid Universal Creative.

- -As of August 2020, privacy regulations have changed such that new creatives entered -in GAM may require a [declaration of the ad technology provider](https://support.google.com/admanager/answer/9972771?hl=en). The first step -is to note the domain you serve the creative from. The examples above offer the -use of the jsdelvr.com CDN. However, you may obtain the creative from a managed -service or you may host it yourself. If you receive a warning from ad manager -about "declaring self-created ad technology", you should be able to work around -this by editing the creative and filling out the "Associated Ad Technology Providers" section as shown in this screen capture: - -

Creative Declaration

- -

Step 3. Attach the Creative to the Line Item

- -

Next, let’s attach the creative to the $0.50 line item you just created. Click into the Line Item, then the Creatives tab.

- -

There will be yellow box showing each ad spot that you haven’t uploaded creatives for yet. Since you’ve already made the creatives, click use existing creatives next to each size.

- -

Use existing creatives list

- -

In the pop-up dialog that appears, click Show All to remove the default size filters and see the 1x1 creatives. Include the prebid creative and click Save.

- -

Use existing creatives dialog

- -

Back in the line item, go into the Creatives tab again, and click into the creative you just added.

- -

Then, in the creative’s Settings tab, enable the Size overrides field and set all your line item’s potential sizes.

- -

Save the creative and go back to the line item.

- -


- -

Step 4. Duplicate Creatives

- -

Google Ad Manager has a constraint that one creative can be served to at most one ad unit in a page under GPT’s single request mode.

- -

Let’s say your page has 4 ad slots. We need to have at least 4 creatives attached to the line item in case more than 2 bids are within the $0.50 range.

- -

Therefore, we need to duplicate our Prebid creative 4 times.

- -

Once that’s done, we have a fully functioning line item with 4 creatives attached that can potentially fill 4 ad slots of varying sizes during a single pageview.

- -


- -

Step 5. Duplicate Line Items

- -

Now let’s duplicate our line item for bids above $0.50.

- -

In the Prebid order page, copy the line item with shared creatives.

- -

This way you only have 4 creatives to maintain, and any updates to those creatives are applied to all pre-bid line items.

- -

For example, we can duplicate 3 more line items:

- - - -

Let’s go into each of them to update some settings. For each duplicated line item:

- -
    -
  1. -

    Change the name to reflect the price, e.g., “Prebid_1.00”, “Prebid_1.50”

    -
  2. -
  3. -

    Change the Rate to match the new price of the line item.

    -
  4. -
  5. -

    In Key-values, make sure to target hb_pb at the new price, e.g., $1.00. Again, be sure to use 2 decimal places.

    -
  6. -
  7. -

    (Optional) Set the start time to Immediate so you don’t have to wait.

    -
  8. -
- -

Repeat for your other line items until you have the pricing granularity level you want.

- -
diff --git a/_includes/adops/adops-gam-video-setup.html b/_includes/adops/adops-gam-video-setup.html deleted file mode 100644 index 1825186ccd..0000000000 --- a/_includes/adops/adops-gam-video-setup.html +++ /dev/null @@ -1,133 +0,0 @@ -
- -

Setting up Prebid Video in Google Ad Manager

- -

This page describes how to set up video creatives in Google Ad Manager for use with Prebid.js.

- -

For general Google Ad Manager line item setup instructions, see the other pages in this section.

- -

For engineering setup instructions, see -Show Video Ads with a Google Ad Manager Video Tag.

- - - - - -

Line Item Setup

- -
    -
  1. In the New line item dialog, choose "Video".
  2. -
  3. Select the appropriate Line Item Type, etc.
  4. -
  5. In the Expected creatives section, choose your video size, e.g., 640x480v.
  6. -
  7. Set the dates, rate, limit, and targeting as desired. For example, for SendAllBids include targeting for "hb_bidder_rubicon=rubicon" as well as the hb_pb_rubicon targeting. This isn't needed if only creating one set of orders for all bidders.
  8. -
  9. Remember to set the hb_pb=BUCKET targeting for each line item, or hb_pb_BIDDER=BUCKET if using separate line items for each bidder.
  10. -
  11. Save the line item.
  12. -
-

Be sure to duplicate your line item and video creative for each Prebid price bucket you intend to create.

-

By default, Prebid.js caps all CPMs at $20. As a video seller, you may expect to see CPMs higher than $20. In order to receive those bids, you’ll need to make sure your dev team implements custom price buckets as described in the engineering setup instructions. Once those changes are made on the engineering side, there should be no changes required from the ad ops side to support CPMs over $20.

- -

Creative Setup

- -When setting up video creatives, it's important to understand where the VAST XML is stored for each of your bidders. The most common place to store VAST XML is AppNexus' cache, but some bidders (such as RubiconProject and SpotX) use their own cache services. To support such -bidders, see the Multiple Cache Locations instructions below. - -

Single Cache Location

- -If you only use bidders that provide full VAST responses, do the following: - -

1. For each line item you create, click on the Creatives tab, click the ADD CREATIVE button, and choose the size you're entering.

- -

2. In the dialog that appears, choose Redirect.

- -

3. Set the VAST tag URL to the cache location. - -

If you’re using a single order for all bidders, then the VAST URL will be the same for each bidder:

- -
   https://prebid.adnxs.com/pbc/v1/cache?uuid=%%PATTERN:hb_uuid%%
-or
-   [other bidder cache location]
- -

If you’re using different orders for each bidder, the VAST URL for each will include the bidder-specific targeting variable:

- -
   https://prebid.adnxs.com/pbc/v1/cache?uuid=%%PATTERN:hb_uuid_BIDDERCODE%%
-or
-   [other bidder cache location]
- -

This VAST tag URL is required in order to show video ads. It points to a server-side cache hosted by your Prebid Server provider.

- -

Prebid Cache and the VAST creative URL warning
- Google Ad Manager will show you a warning stating that fetching VAST from the creative - URL failed. This is expected, since the creative URL above points - to a server-side asset cache hosted by Prebid Server.

- -

4. Set the Duration to the max length of video ads you serve. If you don't know what the max length is, set it to 30.

- -

In the past Prebid used to recommend setting duration to 0 or 1, but GAM now requires that this field reflect the actual video ad length. Since ads flowing through header bidding are going to differ in length, choose a value that matches a common ad length like 15 or 30.

- -

The resulting creative should look something like the following:

- -

Google Ad Manager Video Creative Setup

- - -

Multiple Cache Locations

- -If you're utilizing any bidders that cache their own VAST, you have two options: - -
- -To set up multiple video creatives in the same line item (i.e., to run AppNexus, Rubicon, and SpotX all together in the same video line item), you can utilize creative targeting. -
-
-

-1. In the line item's Expected creatives box, choose Creative Targeting and "Add New Targeting". - -

-2. Give the targeting set a name like "Prebid Default Video Cache URL" and set Custom Targeting as appropriate, e.g., "hb_bidder is none of rubicon, spotx". Save the targeting. - -

-3. For each bidder that uses their own cache, click ADD SIZE in the "Expected creatives" section. Again, choose Creative Targeting and "Add New Targeting". - -

-4. Give the targeting a name like "Prebid Rubicon Video Cache URL". Set Custom Targeting appropriately, e.g., "hb_bidder is any of rubicon". Save the targeting. - -

-5. Save the line item. - -

Now that the targeting is defined, we're going to add the creatives.

- -

-6. Go to the line item's Creatives tab. - -

-7. Make one creative for each of the targets. There are a couple of ways to do this on the GAM UI, but each approach will result in a creative entry screen similar to the screenshot above for the "Single Cache Location" process. Enter a name (e.g. "AppNexus VAST tag") and the VAST URL as described above. - -

-8. The end result should look something like this: - -

Google Ad Manager Video Creative Setup

- -

That’s it as far as Prebid setup is concerned. At this point you can add any other options you would normally use, such as labels or tracking URLs.

- -

Further Reading

- - diff --git a/_includes/dev-docs/build-from-source-warning.md b/_includes/dev-docs/build-from-source-warning.md index 29b8d3700d..a05f683ee5 100644 --- a/_includes/dev-docs/build-from-source-warning.md +++ b/_includes/dev-docs/build-from-source-warning.md @@ -1,4 +1 @@ - -
-This example uses a test version of Prebid.js hosted on our CDN that is not recommended for production use. It includes all available adapters. Production implementations should build from source or customize the build using the Download page to make sure only the necessary bidder adapters are included. -
+
This example includes all available adapters and modules. Production implementations should build from source or customize the build using the Download page to make sure only the necessary bidder adapters and modules are included.
diff --git a/_includes/dev-docs/not-for-production-warning.md b/_includes/dev-docs/not-for-production-warning.md new file mode 100644 index 0000000000..6a6837a7dc --- /dev/null +++ b/_includes/dev-docs/not-for-production-warning.md @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/_includes/head--common.html b/_includes/head--common.html index c5cdec7209..92d292a4dc 100644 --- a/_includes/head--common.html +++ b/_includes/head--common.html @@ -6,7 +6,7 @@ - + {% if page.head_title %} diff --git a/_includes/left_nav.html b/_includes/left_nav.html index edaa1e4548..5101e4ca63 100644 --- a/_includes/left_nav.html +++ b/_includes/left_nav.html @@ -72,6 +72,10 @@ {% for thisSubItem in arrSubItems %} {% if thisSubItem.link == page.url %} {% assign isOpen = 1 %} + {% elsif page.layout == "api_prebidjs" and thisSubItem.link == "/dev-docs/publisher-api-reference.html" %} + {% assign isOpen = 1 %} + {% elsif page.layout == "bidder" and thisSubItem.link == "/dev-docs/bidders.html" %} + {% assign isOpen = 1 %} {% endif %} {% endfor %} @@ -98,6 +102,10 @@ {% assign isPage = 0 %} {% if thisSubItem.link == page.url %} {% assign isPage = 1 %} + {% elsif page.layout == "api_prebidjs" and thisSubItem.link == "/dev-docs/publisher-api-reference.html" %} + {% assign isPage = 1 %} + {% elsif page.layout == "bidder" and thisSubItem.link == "/dev-docs/bidders.html" %} + {% assign isPage = 1 %} {% endif %} {% assign item_classes = base_item_classes | push: 'list-group-item--level-2' %} @@ -107,6 +115,7 @@ {% if subsectionIdx == 0 % || thisSubItem.isCatHeader == 1 %} + {% if thisSubItem.isCatHeader == 1 %} diff --git a/_layouts/bidder.html b/_layouts/bidder.html index a0a05bbe35..d7d5f72ba8 100644 --- a/_layouts/bidder.html +++ b/_layouts/bidder.html @@ -77,8 +77,8 @@

Features

Demand Chain Support {% if page.dchain_supported == true %}yes{% else %}no{% endif %} - Safeframes OK - {% if page.safeframes_ok == false %}no{% elsif page.safeframes_ok == true %}yes{% else %}check with bidder{% endif %} + GPP Support + {% if page.gpp_supported == true %}yes{% else %}no{% endif %} Supports Deals @@ -104,6 +104,12 @@

Features

ORTB Blocking Support {% if page.ortb_blocking_supported == true %}yes{% elsif page.ortb_blocking_supported == false %}no{% elsif page.ortb_blocking_supported == 'partial' %}partial{% else %}check with bidder{% endif %} + + Safeframes OK + {% if page.safeframes_ok == false %}no{% elsif page.safeframes_ok == true %}yes{% else %}check with bidder{% endif %} + + +

"Send All Bids" Ad Server Keys

diff --git a/_layouts/example.html b/_layouts/example.html index c917458838..c86ea1d509 100644 --- a/_layouts/example.html +++ b/_layouts/example.html @@ -33,7 +33,7 @@

Who should use this example:

{% endif %} -

This page contains:

+

About this example:

-

- For tips and troubleshooting info, see: -

-

-
- {% include dev-docs/build-from-source-warning.md %} + {% include dev-docs/not-for-production-warning.md %}

- On the JSFiddle example below: -

+ In the JSFiddle example below: +

-

(Sorry, jsfiddle code examples aren't available with your cookie privacy settings.)

+

(Sorry, JSFiddle code examples aren't available with your cookie privacy settings.)

Cookie Settings


-
+
+ +
+ {% include dev-docs/build-from-source-warning.md %} +
+
+ +

Further Reading

+

+

+

+ + + + diff --git a/_layouts/home.html b/_layouts/home.html index f4c9540d73..30db9fa9cb 100644 --- a/_layouts/home.html +++ b/_layouts/home.html @@ -138,7 +138,7 @@

Prebid is Completely Open Source! Join our Community

Subscribe for Updates

-

Please review our privacy policy

+

Please review our privacy policy

+ +``` + +{: .alert.alert-warning :} +- Replace `%%MACRO%%` with the appropriate macro for your ad server. (Refer to your ad server’s documentation or consult with a representative for specific details regarding the proper macros and how to use them.) +- Replace BIDDERCODE with the appropriate code for the bidder your line item is targeting. For example, if you’re targeting BidderA, the macro variable for adId might look like `ucTagData.adId = "%%PATTERN:hb_adid_BidderA%%";`. + +The example above uses the jsdelvr CDN as the domain from which the creative will serve. However, you may obtain the creative from a managed service or host it yourself. You might need to edit the creative and make adjustments to your creative settings depending on the CDN you're using. + +## Additional Steps + +The final steps in configuring Prebid on your ad server are to do the following: + +1. Duplicate your creatives as needed. If you’re using the Prebid Universal Creative, the body of your creatives for each format will be the same. Duplicate and rename the creative to create as many as you’ll need to attach to the line item. +2. Associate the creatives with the line item. +3. Duplicate the line item. You’ll need one line item per price bucket. If you’re sending all bids, you’ll need one line item per price bucket and per bidder. For each line item you duplicate, edit the line item to have the correct name, price bucket, and bidder code. + +## Further Reading + +- [Ad Ops Planning Guide](/adops/adops-planning-guide.html) +- [Ad Ops and Prebid Overview](/adops/before-you-start.html) + diff --git a/adops/adops-planning-guide.md b/adops/adops-planning-guide.md index ce1e45e6ae..65d6c7d262 100644 --- a/adops/adops-planning-guide.md +++ b/adops/adops-planning-guide.md @@ -1,7 +1,7 @@ --- layout: page_v2 title: Ad Operations Planning -head_title: Getting Started with Prebid for Header Bidding +head_title: Ad Operations Planning sidebarType: 3 sbUUID: 3.2 --- diff --git a/adops/gam-creative-banner-sbs.md b/adops/gam-creative-banner-sbs.md new file mode 100644 index 0000000000..542f8a8419 --- /dev/null +++ b/adops/gam-creative-banner-sbs.md @@ -0,0 +1,120 @@ +--- +layout: page_v2 +title: GAM Step by Step - Banner/Outstream/AMP Creatives +head_title: GAM Step by Step - Banner/Outstream/AMP Creatives +description: Set up banner and outstream creatives for Prebid in Google Ad Manager. +pid: 2 +sidebarType: 3 +--- + + +# GAM Step by Step - Banner/Outstream/AMP Creatives + +This page walks you through the steps required to create banner and outstream creatives to attach to your Prebid line items in Google Ad Manager (GAM). + +{: .alert.alert-success :} +For complete instructions on setting up Prebid line items in Google Ad Manager, see [Google Ad Manager with Prebid Step by Step](/adops/step-by-step.html). + + +1. In GAM, select **Delivery** > **Creatives**. +2. Under the **Display creatives** tab, click **New Creative**. +3. Select your advertiser, then click **Third party**. +4. Enter a **Name** for your creative. For example, `Prebid – banner – 1x1 - 1`. +5. Enter a **Target ad unit size** of `1x1`. This allows the creative to serve on all inventory sizes. + +{: .alert.alert-info :} +These instructions assume you're using the Prebid Universal Creative (PUC). See the [Prebid Universal Creative](/overview/prebid-universal-creative.html) documentation for alternate approaches. + +{: .alert.alert-danger :} +**AMP**: If you choose to bypass the PUC for AMP, Prebid Server events will not work. + +{:start="6"} +6. Select **Standard** as the **Code type**. + +{: .alert.alert-info :} +**AMP**: If you are using AMP, you should still select **Standard** as the code type. The “AMP” option is for AMPHTML hosted by a 3rd party. + +{:start="7"} +7. Enter one of the scripts shown below, depending on whether Prebid is configured to send all bids or only the top price bid. + +**Send All Bids Configuration** + +{: .alert.alert-warning :} +Be sure to replace BIDDERCODE with the appropriate bidder. For example, if the bidder code is `PBbidder`, the `adid` would be `%%PATTERN:hb_adid_PBbidder%%`. + +``` + + +``` + +{: .alert.alert-danger :} +Warning: Be sure none of the attribute names are longer than 20 characters. See [Send All Bids Key Value Pairs](/adops/send-all-vs-top-price.html#key-value-pairs) for more information. + +**Send Top Price Bid Configuration** + +In top-price mode, you can make use of the GAM `TARGETINGMAP` feature instead of listing out each attribute. + +``` + + +``` + +{:start="8"} +8. Select whether to **Serve into a SafeFrame**. See [Creative Considerations](/adops/creative-considerations.html) for more on using SafeFrames. + +{: .alert.alert-info :} +**AMP**: For AMP, you must select **Serve into a SafeFrame**. + +Your creative settings will look something like this. In this example we're assuming a Send All Bids configuration, and we’ve replaced BIDDERCODE with the code for our bidder, PBbidder. (Notice that some of the key names have been truncated to adhere to the GAM 20-character key length limit.) + +![Banner creative settings](/assets/images/ad-ops/gam-sbs/banner-creative-settings.png) + +{: .alert.alert-info :} +Note: You can ignore the “Sorry, we don’t recognize this tag” warning. GAM doesn’t have built-in macros for Prebid and so doesn’t recognize them. The ad tag will still work correctly. + +{:start="9"} +9. If you're using jsdelivr, set your **Associated ad technology provider**: + +{% include /adops/adops-creative-declaration.html %} + +{:start="10"} +10. Click **Save and preview**. + +## Further Reading + +- [Google Ad Manager with Prebid Step by Step](/adops/step-by-step.html) +- [Send All Bids vs Top Price](/adops/send-all-vs-top-price.html) +- [Prebid Universal Creatives](/overview/prebid-universal-creative.html) +- [Creative Considerations](/adops/creative-considerations.html) +- [Ad Ops Planning Guide](/adops/adops-planning-guide.html) diff --git a/adops/gam-native.md b/adops/gam-native.md index f8e81e65cd..0c9de220ec 100644 --- a/adops/gam-native.md +++ b/adops/gam-native.md @@ -1,89 +1,92 @@ --- layout: page_v2 -title: Setting up Prebid Native in Google Ad Manager -head_title: Setting up Prebid Native in Google Ad Manager -description: Setting up Prebid Native in Google Ad Manager +title: GAM Step by Step - Native Creatives +head_title: GAM Step by Step - Native Creatives +description: Set up native creatives for Prebid in Google Ad Manager. sidebarType: 3 --- -# Setting up Prebid Native in Google Ad Manager +# GAM Step by Step - Native Creatives {: .no_toc} -This page describes how to set up native creatives in Google Ad Manager for use with Prebid.js. - -For more information about Google Ad Manager native ad setup, see the [Google Ad Manager native ads documentation](https://support.google.com/admanager/answer/6366845). - -{% capture version2 %} -This document replaces the [original documentation](/adops/setting-up-prebid-native-in-dfp.html) that described how to set up Prebid.js native for GAM. That documentation is still valid, but the approach described here is better in every way, so we recommend that all new and revised implementations follow this approach. Here are the key differences between the original approach and the preferred approach described in this document: -{::nomarkdown} -