The network setup process
There are 4 major phases to get your DoubleClick for Publishers network up and running.
Learn and plan
Review this article and others in the "Set up DoubleClick for Publishers" topic.
Business requirements: Decide what features and use cases your business needs from DFP.
- Review your organization's targeting, trafficking, sales, forecasting, and reporting needs.
- Compile a list of both commonly sold ad products and edge cases. You'll use the list to validate your network design, develop functional requirements, and create a testing plan.
Technical requirements: Assess which teams will need to develop tagging and other integrations.
- Learn about the Google Publisher Tag and decide which GPT mode to use.
Review SDK integrations and additional tagging considerations for mobile and video. You can use the Google Mobile Ads SDK (Android and iOS only) to deliver directly sold ads into applications. The Google IMA SDK is needed for some video formats.
Review DoubleClick for Publishers API integrations with your order management system, billing integration, invoicing, or any custom APIs you use, based on any requirements you have that DFP can't handle through its user interface.
Learn about creative templates to see whether the system-defined templates will meet your needs, or whether you'll need to create custom templates that use your specific code modifications.
Decide on a DFP Network design
- Create a basic plan for how DFP inventory units, such as ad units and key-values, correspond to your website or mobile app inventory. The goal is to ensure that every sales scenario, targeting profile, and reporting requirement can be met through the proposed structure.
- Validate your network design by testing it against the targeting, reporting, and other business requirements you gathered.
Create a test and launch plan
Develop a thorough test plan to ensure that your technical and business requirements are met and validated. If necessary, build and configure a testing environment.
Develop a launch plan to transition your site to DFP tags. Decide whether you'll switch to DFP's forecasting immediately, which means using DFP for 28 days before forecasting has a complete data set, or whether to pre-tag your site to build forecasts before you launch.
Build and test
Set up the basics
- Configure your network settings, such as currency, time zone, and the network name.
- Create users and user roles
- Create companies
Set up inventory in DFP
Set up requests to DFP on your webpages or mobile app
Configure your content management system and your content to request ads from DFP.
- Use Google Publisher Tags for desktop and mobile web inventory.
- Use the Google Mobile Ads SDK for mobile apps.
- Use the Google IMA SDK for video players.
If needed, develop and test API utilities or API-integrated third-party software.
Test your network
Create an order and line item to use for testing.
- Tagging and delivery testing
Test Google Publisher Tags on your sites with each layout and page template. Use troubleshooting tools to resolve delivery problems and better understand of ad delivery patterns.
- Systems and user acceptance testing (UAT)
Test your end-to-end workflow with campaigns, using your test environment if that makes the most sense. Make sure that creatives, including custom templates, render correctly, that your sales lifecycle works the way it should, and that reports are providing the data you expect.
- Reports testing
Set up the standard DFP reports you will need most often.
Prepare your team and ad campaigns
- Encourage others who will be using DFP to complete the training materials in Publisher University and review this Help Center.
- Create new orders and line items for upcoming ad campaigns, or those you’re currently running.
Adjust delivery goals as needed in your current ad delivery system.For campaigns that bridge the launch date, make sure that the new DFP replacement is adjusted for the partial run that will be handled by DFP.
Launch your new DFP network
- Switch live content to use your new DFP ad requests.
- Test to ensure that everything is working correctly.