This repo should provide comprehensive documentation about our DFP implementation, including examples and an FAQ. Unless otherwise noted this documentation was compiled by Rob Denton, just after implementing DFP in December 2016. I will include all information that I think someone would need to have to walk in from the street to fully understand how DFP works with our multiple sites. That said, things change, especially when it comes to Google. Always double check with DFP's most recent documentation.
For more, see this Tracker issue I used while implementing.
Copy of the demos file I used to test and set up tagging for the main site as of 1/3/17. Here are some big differences between this file and what's live (although I may miss some):
- #(dfp("adunit"))# includes network ID and RGM in live version
- mapping vars have different names
- slider02.csp is slightly different
- site skin and expanding billboard are different, see other files
- Up on uploads, used for testing
- Up on uploads
- Used to test mobile banner responsiveness
- Ultimately, I was not able to make the iframe responsive but I was able to adjust padding so it goes all the way across on 320px devices
- Up on uploads
- Used to test if DFP & OpenX could run in parallel w/o conflict, which they can be. We ran in parallel during implementation so there was no lose in ads
- Up on uploads
- Initial test page generated by YourBow for early testing
- demos.dfp.csp is a heavily modified version of this file with additional sizes and DT functionality.
OS4 > YB > DFP
In order to have a DFP premium account you have to have 2 million pageviews a day, which we do not have. In order to access the benefits of DFP premium, we have employed a company called OS4 to reach that threshold with a co-op of other mid-sized newspapers. OS4 provides a single DFP account for all of their clients and then divvy up seats to publications and limit their permissions to only their ad units. This causes some issues, which I will discuss later with taxonomy and KVP.
It's my understanding that OS4 contracts with a company called YourBow which provides technical assistance in setting up the DFP system and some custom code support. I'll discuss this later on when I talk about custom creative templates.
So, we're basically going through OS4 who contracts YB to get to DFP. These layers of abstraction provide support but also constricts some things that would be easy to change if we had an independent account. It's my understanding that being part of the co-op also provides us opportunities to leverage a common marketplace with other mid-sized publications.
- Dick van Halsema [OS4 rep] - email@example.com
- Danijela (Daca) Nenadovic [YourBow implementation consultant] - firstname.lastname@example.org
- Marko Petkovic [YourBow code consultant] - email@example.com
Prior to launch, all communication went through a Basecamp project, which got very confusing at times. There are several threads, some overlapping and some topics jump back and forth between different threads. There is a lot of good info in here, but would be very hard to follow for anyone without knowledge of the process. Everything post-launch uses the OS4 support portal.
There are two ways to target ads in DFP. The primary way is via taxonomy, which roughly aligns with our site's nav. If we were to upgrade the CMS, the DFP taxo should also be changed. In fact, we implemented DFP with a very minimal taxo in favor of relying more heavily on subcategories/key-value pairs. This is not ideal. Given the opportunity, the KVPs should be left behind in favor of a proper taxo.
Our taxo is always prefixed by RGM, OS4/YB require a three-letter code for each publication in the network. Ours is RGM. So, you can target run-of-site ads by simply targeting RGM, or you can target something like Healthy Families by targeting RGM > life > healthyfamilies. These parent-child relationships cascade, so anything targeting RGM > sports will also apply to all of the children of sports (football, trackandfield, basketball, outdoors).
You can explore the full taxonomy by logging into DFP and going to Inventory > Ad Units > Ad Units.
There are some non-nav taxo items to make targeting easier for Melissa and Michelle. These include the four Marketplace sub-sites, the three newsletters, etc.
KVPs are the second way to target in DFP. As I said earlier, we're using KVPs in a way other than recommended. I'm confident that the KVPs will work as expected but it's certainly working against the system, which I am not a fan of.
There are several OS4 keys that are consistant across different publishers. The one we use most heavily is
pos for position. There are
atf & btf (above & below the fold) as well as some custom rgm ones. We use rgm_one, rgm_two, rgm_three to target different medium rectangles on the homepage. Above and below are used for leaderboards.
There are two custom keys made for the RG, both are free-from, instead of predefined. For more on this, you can read more here.
rgm_subcat is a way to target multiple subcategories from DT. This is helpful when all football subcats need to be targeted.
rgm_article_id is a way to target specific CMS IDs from DT. These are used with sponsored content posts or to exclude ads from certain stories.
You can explore all the KVPs by logging into DFP and going to Inventory > Key-values.
There was more than 40 template files that had to be touched to roll out DFP. I defined them into these piles:
- Primary - DT (main news website)
- Secondary - Low traffic RG sites like go, projects and marketplace (In the tracker issues, I may have described these as tertiary)
- Third parties
John handled a lot of the secondary and third parties while I nailed down expanding billboards and site skins with YB. Bishop took care of NIE and Marketplace. I did the rest.
Thankfully, DFP tagging allowed for a lot of simplification in the main news site. There's still a lot of logic but it's about half as bad as it was. See example files for more.
Other issues of note
I took the image expanding billboards that OS4 gave us and created custom HTML5 expanding billboards. There are two elements.
- Adobe Animate templates that Melissa created and are used to create independent collapsed and expanded billboards
- DFP custom creative template that basically just takes two iframe src paths and toggles between the two.
See /expanding-html5-billboard/README.md or the original issue for more.
Ugh. These are turning out to be a real pain. You can read the full story here: https://github.com/registerguard/tracker/issues/618#issuecomment-271989015
The short version is that MailChimp and DFP don't play well with each other.
I tried several things to try and get the ad URLs to click through successfully but had little luck. I currently have open support tickets with MailChimp and OS4 but I'm not confident they will return anything worthwhile. If worse comes to worst, I may try a really hacky solution I saw on a Google Group and a related StackOverflow answer. Instead of having the href go to DFP, have it go to a PHP page hosted by us that redirects to the DFP page from a URL param. I know, janky at best, but it may be our last chance. Also, THIS WILL ONLY WORK IF THE ADS ARE CONSISTANT AND DO NO CHANGE.
More to come...