To help keep track of the ROI of holiday shopping campaigns, DoubleClick Search is rolling out to all advertisers over the next few weeks, a new functionality -- "instant Floodlight conversion data in all its reports."
In addition to the engine performance data already update in near-real time -- now, "reporting on conversion data in DoubleClick Search will also be updated automatically throughout the day, minutes after a conversion happens," the DS team stated.
"With this enhancement, get immediate feedback on how your campaigns are performing, given specific changes to creative ad text, bids, keywords, or external factors."
For example, "if you're launching a new holiday campaign, DoubleClick Search reporting will now start recording any conversions as soon as the campaign is live. Within moments of any event that impacts your campaign (a snowstorm, airing of a TV ad, or bid changes, to name a few), you can view the impact of that event on your overall campaign performance, without having to wait for the typical 24-hour data delays from nightly data transfer," explains the DS team.
In addition, if you're looking at stats from 'Today' for any of your campaigns, you can see your conversion stats update in real time.
Google just shared a video of recently held webinar introducing users to Google Tag Manager, "a free tool that helps marketers and IT departments manage their marketing and measurement tags quickly and easily."
In the video below, you will learn about: "Overall benefits and features of using Google Tag Manager; A quick demonstration of how to deploy a new tracking tag; and Tips for getting your company started with Google Tag Manager."
How would you migrate a tag? Follow these steps to migrate tags -- whether it's a single tag or all the tags on your site. If you're just getting started, take a look at our Before you Begin article.
- Create a Google Tag Manager Account and a Container associated with that account.
- Install that Container code snippet on every page of your website (so that it appears immediately after the opening <body> tag). The container should be empty.
- Map your site - thinking about what data you want to collect, what events you want to track, and which tags you want to use to track that data. You should think about where your current tags are implemented, but now is a great time to rethink your overall data collection goals and start fresh.
- (Optional) If you would like to make use of the Data Layer functionality, create a data layer on the pages where you wish to pass information or fire tags
- Create Tags, Rules and Macros within the Google Tag Manager interface according to the map you just created. Make sure to apply the correct Rules to your Tags to make sure they fire in the right place.
- Test the changes you've made in Google Tag Manager using debug and preview mode.
- Then push a version of your site live that has removed the hard-coded tags from within the page. At this time, also Publish your changes using the Publishing feature of Google Tag Manager, which pushes the changes live to the site.
For more precise details on these steps, read our developer documents about migration.
Where can I find out more about the core concepts described in the webinar?
To learn more about the Google Tag Manager management interface, please visit our Help Center -- you may want to start with our Before you Begin article. There you can find more information about key concepts like Tags, Rules, and Macros. For developers interested in how to implement Google Tag Manager, please visit our developer documentation. Or if you'd like help with implementation, you can contact one of our Partners. You can also ask questions (and find responses to questions from others) on the Google Tag Manager product forum.
Update: A security bug in Google Webmaster Tools that has given users access to old accounts and websites that they're no longer supposed to be able to access has now been fixed.
According to reports some "Webmaster Tools accounts users started finding themselves with sudden access to accounts that they once had access to, but no longer do; i.e., former clients, employers and the like. That bug is presumably giving a lot of power to individuals that shouldn't have it -- power to deindex, disavow links, unverify the current/legitimate webmaster's access, and even redirect sites to other verified domains in the user's account. It also reveals a lot of link, search, index/crawl and other data to users that should't be able to see those things."
Several hours after the breach, Google has fixed the bug, and issued the following statement:
For several hours yesterday a small set of Webmaster Tools accounts were incorrectly re-verified for people who previously had access. We've reverted these accounts and are investigating ways to prevent this issue from recurring.