Publishers that are looking for consolidated reporting across Native and Display within Google Ad Manager (GAM) and to leverage existing processes for forecasting and targeting may opt to use Nativo's GAM integration.
GAM Integration Benefits
The GAM Integration allows you to traffic campaigns within GAM while using Nativo for all advanced native functionality.
Flexible and beautiful Native rendering
Nativo creative optimization
Content engagement measurement
Extended Native ad formats, featuring Native Article
Integration Step-By-Step
Getting started with Nativo using the GAM integration involves 4 important steps:
Set up GAM Ad Unit - 1 day
Style the Nativo In-Feed Unit - 2 days
Create a Content Landing Page template - 5 days
Update your ADS.TXT entries (for monetization) - 1 day
Final tests and approval for go-live - 1 day
Step 1. Set up GAM Ad Unit
A. Provide URL and Ad Unit Path
Provide URL and Ad Unit Path1 (ad unit ID + name) for the ad unit served into.
B. Traffic the integration test campaign
Nativo will provide a test campaign to traffic as a third-party fixed size creative with any placeholder size2 (1x1, 300x250, etc). Make sure to uncheck the "serve into SafeFrame" option.3
C. Set up a preview for testing
After trafficking the test creative, provide either a GAM preview link or a KVP test parameter (such as ?test=nativo) that forces the test creative to render.
Once the above is implemented correctly, a blue box will populate saying "GAM targeting success".
REFERENCES
1Default GAM Macro of %%ADUNIT%%
2Creative size must match ad unit/line item sizes to serve
3SafeFrames prevent Nativo code from firing properly and limit your ability to monetize
Step 2. Style the Nativo In-Feed Unit
The GAM placement is ready for styling by the Nativo design team. Please send design specs and mocks (if available) for design direction.
Step 3. Create a Content Landing Page template
Adding a content landing page ensures that you can receive all of Nativo demand as well as take advantage of all of the direct selling tools in the platform.
See Content Landing Page Integration for details.
🚧IMPORTANT
Skipping this step will significantly reduce Nativo demand and limit functionality for direct sales. Learn more about the benefits of a content landing page.
Step 4. Update your ADS.TXT entries (for monetization)
Keep your ADS.TXT file updated to make sure you have access to all of Nativo's programmatic demand channels. Learn more about ADS.TXT And APP-ADS.TXT.
Step 5. Final tests and approval for go-live
Nativo will provide links for placement approval, platform training, and a live demand creative to traffic.
🚧Troubleshooting
Please send Nativo test links or screenshots to facilitate troubleshooting.
Passback Setup
Creative Selection:
Nativo demand creative offers versions with and without passback enabled. The version without passback will make a single call to the Nativo ad server and demand options; including a backfill House Ad option. Ask AM for details. The version with passback will recall GAM for other eligible creatives to be served if Nativo does not have fill availability.
Key Value Pairs:
By default, Nativo places a KVP of "passback:nativo" when the ad server recalls GM+AM for passback. Multiple KVPs can be used as needed. Ensure KVP is included within GAM setup.
Demand Line Item:
To prevent infinite looping, set up negative KVP targeting of "passback is none of nativo" for the line item with Nativo demand creative.
Passback Line Item:
To ensure that the line item serves directly after the Nativo demand creative, if fill is not availabe, be sure to include positive KVP targeting "Passback is any of nativo" for the line item containing the creative to pass back to.
Reporting Discrepancy:
Passbacks will cause double calls through the GAM/NTV setup. Break out GAM reporting by KVP to separate the Nativo impressions/ad calls versus passback.