Page content here...
``` ## Targeting Keys When `setDisplayBids()` is called, the following targeting keys are set on each GPT slot: | Key | Description | Example Value | | ---------- | --------------------- | ---------------- | | n360\_bid | Unique bid identifier | `"abc123def456"` | | n360\_pb | Price bucket | `"2.50"` | | n360\_sz | Ad size | `"300x250"` | | n360\_crid | Creative ID | `"creative_789"` | | n360\_ssp | SSP identifier | `"appnexus"` | These keys are used by the line items in GAM to target winning bids and render the correct creative. See [Line Item Setup](/integration-methods/direct-integration-n360ortb/gam-integration/line-item-setup.md) for full details on price granularity and how line items are configured. ## Key Configuration Points ### 1. Disable Initial Load ```javascript googletag.pubads().disableInitialLoad(); ``` This is **essential**. It prevents GPT from loading ads before the header bidding auction completes. ### 2. Match divId to GPT Slot ID The `divId` in your n360ortb slot configuration must match the element ID used in `googletag.defineSlot()`: ```javascript // GPT slot definition googletag.defineSlot('/12345/my-unit', [[300, 250]], 'div-1'); // n360ortb slot - divId must match 'div-1' { tagId: 'my-tag', divId: 'div-1', // Must match GPT slot ID sizes: [[300, 250]] } ``` ### 3. Matching Sizes The sizes in your n360ortb configuration should match those in your GPT slot definition: ```javascript // GPT slot with sizes googletag.defineSlot('/12345/my-unit', [[300, 250], [300, 600]], 'div-1'); // n360ortb slot with matching sizes { tagId: 'my-tag', divId: 'div-1', sizes: [[300, 250], [300, 600]] // Should match GPT sizes } ``` ## Automatic Targeting Cleanup The `setDisplayBids()` method automatically registers an event listener on `slotRenderEnded` to clear n360ortb targeting after each slot renders. This prevents stale targeting from affecting subsequent ad refreshes. ## Refreshing Specific Slots To refresh only specific slots: ```javascript function refreshSlot(divId, tagId, sizes) { n360ortb.fetchBids({ slots: [ { tagId: tagId, divId: divId, sizes: sizes } ] }, function(bids) { n360ortb.setDisplayBids(); // Refresh only the specific slot googletag.cmd.push(function() { var slot = googletag.pubads().getSlots().find(function(s) { return s.getSlotElementId() === divId; }); if (slot) { googletag.pubads().refresh([slot]); } }); }); } // Usage refreshSlot('div-sidebar', 'sidebar-mpu-tag', [[300, 250], [300, 600]]); ``` ## Setup Requirements Before using the GAM integration, you need to: 1. [Connect your GAM account](/integration-methods/direct-integration-n360ortb/gam-integration/connect-your-gam-account.md) - Grant Nexx360 access to create line items 2. [Line Item Setup](/integration-methods/direct-integration-n360ortb/gam-integration/line-item-setup.md) - Understand how line items and price buckets work 3. [Set up GAM creatives](/integration-methods/direct-integration-n360ortb/gam-integration/gam-creative-setup.md) - Configure the creative template to render bids ## Next Steps * [Connect your GAM account](/integration-methods/direct-integration-n360ortb/gam-integration/connect-your-gam-account.md) * [Line Item Setup](/integration-methods/direct-integration-n360ortb/gam-integration/line-item-setup.md) * [GAM Creative Setup](/integration-methods/direct-integration-n360ortb/gam-integration/gam-creative-setup.md) * [API Reference](/integration-methods/direct-integration-n360ortb/api-reference.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developer.nexx360.io/integration-methods/direct-integration-n360ortb/gam-integration.md?ask=