| 1:47 am on Oct 27, 2011 (gmt 0)|
Thanks levo! This should help quite a bit.
| 7:12 am on Oct 28, 2011 (gmt 0)|
I was looking for this so long.
Will switch this weekend.
| 1:16 pm on Oct 28, 2011 (gmt 0)|
Yes, it definitely makes DFP look like a good way to go. Also other improvements:
|Google Publisher Console - The tag comes with a built-in debugging and support tool called the Google Publisher Console, which is enabled on all pages containing the Google Publisher Tag. ... |
The console provides checks for common tagging errors, visual highlights of all ad units and creatives on the page to help with debugging, and an alternative point of entry into the DFP front-end.
Single request mode - Single request mode means that instead of sending individual ad requests to DoubleClick servers, the browser is able to send one request notifying the server of all ad units on the page. This enables advanced roadblocking and improves page load time. ...
Though it does require the replacement of old Ad Manager tags with the new Google Publisher Tags.
| 1:22 pm on Oct 28, 2011 (gmt 0)|
So does this mean that pages will load faster with DFP than without it (assuming you are running adsense of course)?
| 7:38 pm on Oct 28, 2011 (gmt 0)|
No, pages with the new Ad Tag will load faster then with the old Ad Tag ;)
| 7:58 pm on Oct 28, 2011 (gmt 0)|
@denisl were you asking if your pages will run better with the new DFP async tags than with AdSense alone?
I suspect that will be the case but won't know until I implement the tags sometime next week. I will post back here once I do.
| 8:11 pm on Oct 28, 2011 (gmt 0)|
Since both Adsense and the new DFP are asynchronous, there shouldn't be any delay in rendering the page using either.
Non-asynchronous ads will delay the page from rendering until the ads are fetched.
Determining which of the two, Adsense or the new DFP, would be faster to deliver the ads would be difficult to determine. Times would vary on a case by case basis.
| 8:25 pm on Oct 28, 2011 (gmt 0)|
Thanks Leonard0. I forgot about the AdSense async update. I don't think the new DFP tags will have much impact, if any, if using AdSense exclusively.
| 1:21 am on Oct 29, 2011 (gmt 0)|
|Since both Adsense and the new DFP are asynchronous, there shouldn't be any delay in rendering the page using either. |
AFAIK new Adsense code is fast, but it is not an async js implementation, the new adsense method (blocks page load until the script is loaded, creates an iframe and moves on), is same as the DFP's old iFrame tagging.
Adsense js is cached for 1 hour, if there is a problem on their servers, or your visitor has a high latency, Adsense code would still hang/stall your page, new Google Publisher Tag won't.
| 12:08 pm on Oct 31, 2011 (gmt 0)|
Thank you for the feedback.
Trying DFP is one of those things I intend to do when I have the time.
| 12:56 pm on Oct 31, 2011 (gmt 0)|
So, I made the switch two days ago and I must say I am very pleased.
Speed is great :)
| 12:20 pm on Nov 4, 2011 (gmt 0)|
Does it work for you? For me it's a mess! Page impressions nearly doubled, one adslot doesn't counting and adimpressions clicks (cost me a lot of money). No idea what's going on. It's fast, indeed.
| 3:44 pm on Nov 4, 2011 (gmt 0)|
Currently I run AdSense as Line Items and the Impressions are the same as in AdSense.
Next week I will switch to the build in AdSense Option to make AdSense compete with my direct Ad Sales.
Did you try the new debug console that comes with the new Google Publisher Tags?
For example go to the website where your ad unit is not counting (use chrome) and then press F10.
| 6:32 pm on Nov 4, 2011 (gmt 0)|
I tried switching and had one/two ad networks seeing terrible fill rates. As soon as I switched back the fill rates went back to normal.
| 6:42 pm on Nov 4, 2011 (gmt 0)|
@DaStarBug Please post back with your results on using the built in AdSense with DFP. I am running AdSense as line items per some of your past blog posts and am interested to see how your upcoming change will perform.
| 7:44 pm on Nov 4, 2011 (gmt 0)|
I updated my tutorial on how to use the Async version with the build in AdSense option in case you missed it ;)
| 10:17 pm on Feb 2, 2012 (gmt 0)|
DaStarBuG, I am considering moving over to using the AdSense built into DFP. Any tips or tricks before I make the decision to move ahead?
| 9:42 am on Feb 3, 2012 (gmt 0)|
Attach your channel IDs to your dfp ad units to keep tracking your ads in AdSense.
If you don't know how, you know where to go :)
| 1:29 pm on Feb 3, 2012 (gmt 0)|
I know how to do that, thanks though. I was referring to earlier in this thread where I said:
|@DaStarBug Please post back with your results on using the built in AdSense with DFP. I am running AdSense as line items per some of your past blog posts and am interested to see how your upcoming change will perform. |
and you responded:
I was just wondering if you had some thoughts to share based on your experience. Namely, did the CPM stay the same, get worse, or improve and was there a period of volatility before things returned to normal again?
| 3:33 pm on Feb 7, 2012 (gmt 0)|
There was no dip in CPM after switching to the build in AdSense option.
I currently run third party advertising and competing it with AdSense to maximize revenue.
That is the good part of using DFP. :)
| 4:10 pm on Feb 16, 2012 (gmt 0)|
The new Google Publisher Tag (GPT) in async and single request mode works fine in ie but the resource [pubads.g.doubleclick.net...] blocks the page load until the script is loaded in both chrome and firefox.
Is there anyway to load this resource in parallel and improve the page load of the new tag in chrome and firefox?