Sunday, August 5, 2012
Wednesday, August 1, 2012
Join Learn with Google at SES in San Francisco!
If you're planning on attending Search Engine Strategies San Francisco in August, stop by our in-conference Learn with Google event, Search and Beyond with Google AdWords and DoubleClick, to learn how Google makes the web work for you. We'll have speakers across Google Search, the Google Display Network, and DoubleClick Search, with question and answer sessions following each presentation.
Tuesday, August 14
- Hear about recent enhancements to Google AdWords, Google Display Network and DoubleClick Search, as well as real-world examples of how these new solutions are already helping business solve some of their biggest challenges, presented by Ariel Bardin, Product Management Director - Google Search Ads
- Dive deep on how you can win the moments that matter with effective AdWords social, mobile and local solutions to reach your users, presented by Shannon Snow, Head of Industry - Education
- Learn about how DoubleClick Search helps marketers and agencies running some of the world's largest search campaigns more efficiently and effectitvely with Anthony Chavez, Senior Product Manager - DoubleClick Search
- Close the day with David Monsees, Product Manager - Google Display Network, to hear about how you can use the power of display advertising to extend the impact of your search campaigns with remarketing and contextual targeting
Wednesday, August 15
- During How to Win with Google & Bing, Ryan Gibson, Manager on the Agency business Development Team, will join the discussion on best practices for optimizing your campaigns, keywords, match-types, ads, bids, targeting, landing pages and quality scores for each network and highlight the most important differences that can make all the difference in highly-competitive markets
- Learn about Better SEM in a Cross-Channel World with Head of Emerging Products & Markets Stephen Yap, who will explore what marketers and agencies should expect from the next generation of search management platforms
The full SES agenda can be found here.
Additionally, we'll be offering 20-minute account optimization sessions with Google AdWords specialists, and 20-minute product demonstrations with DoubleClick Search specialists. If you’re interested in learning more about new features or best practices, let us know by filling out the form here. The deadline to sign up is Wednesday, August 8, 2012.
Still haven’t registered? We're happy to offer advertisers a promotional code for 20% off when you buy a Conference pass to SES SF. Reference our discount code 20GOOG upon registration.
If past conferences are anything to go by, this should be a fun and educational event, with lots of folks to meet, contacts to make, and tips and tricks to learn. We hope to see you there!
Posted by the DoubleClick Search team
Use any credit or debit card with Google Wallet
(cross-posted from the Google Commerce Blog)
Since we released the first version of Google Wallet, the app that makes your phone your wallet, we’ve made it available on six phones from Sprint and Virgin Mobile, as well as the new Nexus 7 tablet. We’ve also partnered with more than 25 national retailers, and thanks to MasterCard PayPass, you can pay with your phone at more than 200,000 retail locations across the U.S.
Today we’re releasing a new, cloud-based version of the Google Wallet app that supports all credit and debit cards from Visa, MasterCard, American Express, and Discover. Now, you can use any card when you shop in-store or online with Google Wallet. With the new version, you can also remotely disable your mobile wallet app from your Google Wallet account on the web.
A wallet with all your credit and debit cards
To save a card to Google Wallet, just enter the number into the mobile app, online wallet, or Google Play when making purchases. When you shop in-store, you can use Google Wallet in conjunction with your selected credit or debit card for purchases (more info here). Shortly after making a payment, you’ll see a transaction record on the phone with the merchant name and dollar amount. You can now view a history of all your in-store and online purchases from the online wallet.
To support all credit and debit cards, we changed our technical approach to storing payment cards. The Google Wallet app now stores your payment cards on highly secure Google servers, instead of in the secure storage area on your phone. A wallet ID (virtual card number) is stored in the secure storage area of the phone, and this is used to facilitate transactions at the point of sale. Google instantly charges your selected credit or debit card. This new approach speeds up the integration process for banks so they can add their cards to the Wallet app in just a few weeks. Banks that want to help their customers save cards to Google Wallet, including their custom card art, can apply here — there is no cost.
A wallet you can lock — and remotely disable
We take security very seriously and have always had a dedicated Google Wallet PIN to prevent others from making payments with your Google Wallet. And as always, we encourage Google Wallet customers to set up the phone’s screen lock -- as an extra layer of protection.
Today, we’re adding a Google Wallet security feature that makes it possible for you to remotely disable your mobile wallet on a lost phone. It’s easy. If you lose your phone, just visit the ‘Devices’ section in the online wallet and select the phone with the mobile wallet you wish to disable. When you successfully disable your wallet on a device, Google Wallet will not authorize any transactions attempted with that device*. If the Google Wallet online service can establish a connection to your device, it will remotely reset your mobile wallet, clearing it of card and transaction data. There is no way you can do that with your leather wallet.
The new Google Wallet app is available now on Google Play, and if you have a supported NFC device and are in the United States, we encourage you to give it a try.
Posted by Robin Dua, Head of Product Management, Google Wallet
* For now, Google Prepaid Cards and some Citi MasterCard cards will remain active until Google Wallet can remotely connect and reset your mobile wallet.
Since we released the first version of Google Wallet, the app that makes your phone your wallet, we’ve made it available on six phones from Sprint and Virgin Mobile, as well as the new Nexus 7 tablet. We’ve also partnered with more than 25 national retailers, and thanks to MasterCard PayPass, you can pay with your phone at more than 200,000 retail locations across the U.S.
Today we’re releasing a new, cloud-based version of the Google Wallet app that supports all credit and debit cards from Visa, MasterCard, American Express, and Discover. Now, you can use any card when you shop in-store or online with Google Wallet. With the new version, you can also remotely disable your mobile wallet app from your Google Wallet account on the web.
A wallet with all your credit and debit cards
To save a card to Google Wallet, just enter the number into the mobile app, online wallet, or Google Play when making purchases. When you shop in-store, you can use Google Wallet in conjunction with your selected credit or debit card for purchases (more info here). Shortly after making a payment, you’ll see a transaction record on the phone with the merchant name and dollar amount. You can now view a history of all your in-store and online purchases from the online wallet.
To support all credit and debit cards, we changed our technical approach to storing payment cards. The Google Wallet app now stores your payment cards on highly secure Google servers, instead of in the secure storage area on your phone. A wallet ID (virtual card number) is stored in the secure storage area of the phone, and this is used to facilitate transactions at the point of sale. Google instantly charges your selected credit or debit card. This new approach speeds up the integration process for banks so they can add their cards to the Wallet app in just a few weeks. Banks that want to help their customers save cards to Google Wallet, including their custom card art, can apply here — there is no cost.
A wallet you can lock — and remotely disable
We take security very seriously and have always had a dedicated Google Wallet PIN to prevent others from making payments with your Google Wallet. And as always, we encourage Google Wallet customers to set up the phone’s screen lock -- as an extra layer of protection.
Today, we’re adding a Google Wallet security feature that makes it possible for you to remotely disable your mobile wallet on a lost phone. It’s easy. If you lose your phone, just visit the ‘Devices’ section in the online wallet and select the phone with the mobile wallet you wish to disable. When you successfully disable your wallet on a device, Google Wallet will not authorize any transactions attempted with that device*. If the Google Wallet online service can establish a connection to your device, it will remotely reset your mobile wallet, clearing it of card and transaction data. There is no way you can do that with your leather wallet.
The new Google Wallet app is available now on Google Play, and if you have a supported NFC device and are in the United States, we encourage you to give it a try.
Posted by Robin Dua, Head of Product Management, Google Wallet
* For now, Google Prepaid Cards and some Citi MasterCard cards will remain active until Google Wallet can remotely connect and reset your mobile wallet.
Use any credit or debit card with Google Wallet
(cross-posted from the Google Commerce Blog)
Since we released the first version of Google Wallet, the app that makes your phone your wallet, we’ve made it available on six phones from Sprint and Virgin Mobile, as well as the new Nexus 7 tablet. We’ve also partnered with more than 25 national retailers, and thanks to MasterCard PayPass, you can pay with your phone at more than 200,000 retail locations across the U.S.
Today we’re releasing a new, cloud-based version of the Google Wallet app that supports all credit and debit cards from Visa, MasterCard, American Express, and Discover. Now, you can use any card when you shop in-store or online with Google Wallet. With the new version, you can also remotely disable your mobile wallet app from your Google Wallet account on the web.
A wallet with all your credit and debit cards
To save a card to Google Wallet, just enter the number into the mobile app, online wallet, or Google Play when making purchases. When you shop in-store, you can use Google Wallet in conjunction with your selected credit or debit card for purchases (more info here). Shortly after making a payment, you’ll see a transaction record on the phone with the merchant name and dollar amount. You can now view a history of all your in-store and online purchases from the online wallet.
To support all credit and debit cards, we changed our technical approach to storing payment cards. The Google Wallet app now stores your payment cards on highly secure Google servers, instead of in the secure storage area on your phone. A wallet ID (virtual card number) is stored in the secure storage area of the phone, and this is used to facilitate transactions at the point of sale. Google instantly charges your selected credit or debit card. This new approach speeds up the integration process for banks so they can add their cards to the Wallet app in just a few weeks. Banks that want to help their customers save cards to Google Wallet, including their custom card art, can apply here — there is no cost.
A wallet you can lock — and remotely disable
We take security very seriously and have always had a dedicated Google Wallet PIN to prevent others from making payments with your Google Wallet. And as always, we encourage Google Wallet customers to set up the phone’s screen lock -- as an extra layer of protection.
Today, we’re adding a Google Wallet security feature that makes it possible for you to remotely disable your mobile wallet on a lost phone. It’s easy. If you lose your phone, just visit the ‘Devices’ section in the online wallet and select the phone with the mobile wallet you wish to disable. When you successfully disable your wallet on a device, Google Wallet will not authorize any transactions attempted with that device*. If the Google Wallet online service can establish a connection to your device, it will remotely reset your mobile wallet, clearing it of card and transaction data. There is no way you can do that with your leather wallet.
The new Google Wallet app is available now on Google Play, and if you have a supported NFC device and are in the United States, we encourage you to give it a try.
Posted by Robin Dua, Head of Product Management, Google Wallet
* For now, Google Prepaid Cards and some Citi MasterCard cards will remain active until Google Wallet can remotely connect and reset your mobile wallet.
Since we released the first version of Google Wallet, the app that makes your phone your wallet, we’ve made it available on six phones from Sprint and Virgin Mobile, as well as the new Nexus 7 tablet. We’ve also partnered with more than 25 national retailers, and thanks to MasterCard PayPass, you can pay with your phone at more than 200,000 retail locations across the U.S.
Today we’re releasing a new, cloud-based version of the Google Wallet app that supports all credit and debit cards from Visa, MasterCard, American Express, and Discover. Now, you can use any card when you shop in-store or online with Google Wallet. With the new version, you can also remotely disable your mobile wallet app from your Google Wallet account on the web.
A wallet with all your credit and debit cards
To save a card to Google Wallet, just enter the number into the mobile app, online wallet, or Google Play when making purchases. When you shop in-store, you can use Google Wallet in conjunction with your selected credit or debit card for purchases (more info here). Shortly after making a payment, you’ll see a transaction record on the phone with the merchant name and dollar amount. You can now view a history of all your in-store and online purchases from the online wallet.
To support all credit and debit cards, we changed our technical approach to storing payment cards. The Google Wallet app now stores your payment cards on highly secure Google servers, instead of in the secure storage area on your phone. A wallet ID (virtual card number) is stored in the secure storage area of the phone, and this is used to facilitate transactions at the point of sale. Google instantly charges your selected credit or debit card. This new approach speeds up the integration process for banks so they can add their cards to the Wallet app in just a few weeks. Banks that want to help their customers save cards to Google Wallet, including their custom card art, can apply here — there is no cost.
A wallet you can lock — and remotely disable
We take security very seriously and have always had a dedicated Google Wallet PIN to prevent others from making payments with your Google Wallet. And as always, we encourage Google Wallet customers to set up the phone’s screen lock -- as an extra layer of protection.
Today, we’re adding a Google Wallet security feature that makes it possible for you to remotely disable your mobile wallet on a lost phone. It’s easy. If you lose your phone, just visit the ‘Devices’ section in the online wallet and select the phone with the mobile wallet you wish to disable. When you successfully disable your wallet on a device, Google Wallet will not authorize any transactions attempted with that device*. If the Google Wallet online service can establish a connection to your device, it will remotely reset your mobile wallet, clearing it of card and transaction data. There is no way you can do that with your leather wallet.
The new Google Wallet app is available now on Google Play, and if you have a supported NFC device and are in the United States, we encourage you to give it a try.
Posted by Robin Dua, Head of Product Management, Google Wallet
* For now, Google Prepaid Cards and some Citi MasterCard cards will remain active until Google Wallet can remotely connect and reset your mobile wallet.
The power of places and big data for good: Google Places API Developer Challenge 2012
How would you make your community or local government run better? In our first Google Places API Developer Challenge, we’re inviting developers around the world to make something that improves their communities or governments by using the Google Places API and its database of places and tools. The developers of the winning applications will receive a VIP experience at Google I/O 2013.
You might create an app or site that solves health problems, understands crime patterns, or improves commerce. You can use any platform as long as you build with the Google Places API and it benefits your community or government. We’re looking for your best and most innovative ideas.
Built on the comprehensive global database of more than 95 million places that powers Google Maps, the Google Places API enables you to search for information about a variety of nearby places such as establishments, geographic locations and prominent points of interest. You can re-rank place results based on user check-ins, and create new places specific to your app.
To help you develop your ideas and build better apps, we’ve been working with local government officials in Austin, Boston, Chicago, London, Louisville, New York City, Philadelphia, Portland (Ore.), San Francisco, and Seattle along with the White House to surface a wide variety of data sets for your apps. You can find these data sets and more on the Google Places API Challenge site at http://developers.google.com/challenge and hear more about what cities have to say about the challenge here. You can also follow updates and hangouts about the challenge on +Google Maps API.
The submission window opens on August 15th and closes on October 31st, 2012.
We look forward to seeing what can happen when your imagination and the Google Places API come together!
You might create an app or site that solves health problems, understands crime patterns, or improves commerce. You can use any platform as long as you build with the Google Places API and it benefits your community or government. We’re looking for your best and most innovative ideas.
Built on the comprehensive global database of more than 95 million places that powers Google Maps, the Google Places API enables you to search for information about a variety of nearby places such as establishments, geographic locations and prominent points of interest. You can re-rank place results based on user check-ins, and create new places specific to your app.
To help you develop your ideas and build better apps, we’ve been working with local government officials in Austin, Boston, Chicago, London, Louisville, New York City, Philadelphia, Portland (Ore.), San Francisco, and Seattle along with the White House to surface a wide variety of data sets for your apps. You can find these data sets and more on the Google Places API Challenge site at http://developers.google.com/challenge and hear more about what cities have to say about the challenge here. You can also follow updates and hangouts about the challenge on +Google Maps API.
The submission window opens on August 15th and closes on October 31st, 2012.
We look forward to seeing what can happen when your imagination and the Google Places API come together!
Getting AdMob ads to work with cocos2D Part 2: Handling Autorotation
In the first part of this series, we talked about integrating AdMob ads in a cocos2d application without diminishing performance. However, we conveniently overlooked how you’d go about handling device reorientation. This blog post will outline the two steps necessary for getting autorotation to work using v0.99.5b3 or higher of the cocos2d framework.
Step One: Setting UIKit Autorotation
cocos2d allows you to handle autorotation in two different ways (UIKit and cocos2d). Since we’re working with both UIKit views as well as Open GL views, we want to rely on UIKit autorotation. If not, we’d have to transform our GADBannerView manually. To make sure you’re using UIKit autorotation, set the GAME_AUTOROTATION directive on your platform of choice to kGameAutorotationUIViewController.
Once you’ve done this, check RootViewController.m to make sure shouldAutorotateToInterfaceOrientation: returns YES for all of the orientations that you support. cocos2d produces skeleton code that handles this method differently depending on the autorotation method you’re using, so make sure that you modify the code block where GAME_AUTOROTATION == kGameAutorotationUIViewController.
Step Two: Modifying View Layout
The final step is to modify our resizeViews: method so that it takes the orientation of the device into account when laying out the views. Rewrite resizeViews: as resizeViewForOrientation:, using the orientation parameter to lay out your GADBannerView. The code below, similar to the first blog post, assumes you’re laying out your banner at the top of the screen.
- (void)resizeViewsForOrientation:(UIInterfaceOrientation)toInt {
// If the banner hasn't been created yet, no need for resizing views.
if (!bannerView_) {
return;
}
BOOL adIsShowing = [self.view.subviews containsObject:bannerView_];
if (!adIsShowing) {
return;
}
// Frame of the main RootViewController which we call the root view.
CGRect rootViewFrame = self.view.frame;
// Frame of the main RootViewController view that holds the cocos2d view.
CGRect glViewFrame = [[CCDirector sharedDirector] openGLView].frame;
CGRect bannerViewFrame = bannerView_.frame;
CGRect frame = bannerViewFrame;
// The updated x and y coordinates for the origin of the banner.
CGFloat yLocation = 0.0;
CGFloat xLocation = 0.0;
// Move the root view underneath the ad banner.
glViewFrame.origin.y = bannerViewFrame.size.height;
// Center the banner using the value of the origin.
if (UIInterfaceOrientationIsLandscape(toInt)) {
// The superView has not had its width and height updated yet so
// use those values for the x and y of the new origin respectively.
xLocation = (rootViewFrame.size.height -
bannerViewFrame.size.width) / 2.0;
} else {
xLocation = (rootViewFrame.size.width -
bannerViewFrame.size.width) / 2.0;
}
frame.origin = CGPointMake(xLocation, yLocation);
bannerView_.frame = frame;
if (UIInterfaceOrientationIsLandscape(toInt)) {
// The super view's frame hasn't been updated so use its width
// as the height.
glViewFrame.size.height = rootViewFrame.size.width -
bannerViewFrame.size.height;
glViewFrame.size.width = rootViewFrame.size.height;
} else {
glViewFrame.size.height = rootViewFrame.size.height -
bannerViewFrame.size.height;
}
[[CCDirector sharedDirector] openGLView].frame = glViewFrame;
}
Now that you’re handling rotation, you’re going to have to resize your views in two different places. We’ve already covered this in initGADBanner: in the first post (simply use the interfaceOrientation property of UIViewController to call resizeViewsForOrientation: instead of resizeViews:). Here, we also have to call resizeviewsForOrientation: in willRotateToInterfaceOrientation:duration: as well. You can add this call after the skeleton code that cocos2d provides.
Ads inside your cocos2d application should now stay docked in place whenever device rotations occur. You can check out a full example from this blog post here. As always, feel free to direct any questions you have to our forum or join us for our upcoming hangout.
- Raj Parameswaran, AdMob Team
Custom color picker in Google Calendar
Google Calendar users have had the ability to change the colors of specific events or calendars from a default color palette. Users can now choose a custom color if the default palette does not meet their needs.
Release track:
Rapid
Editions included:
Google Apps, Google Apps for Business, Government and Education
How to access what's new:
Click on "Choose custom color" on the bottom of the existing color picker.
For more information:
http://support.google.com/calendar/bin/answer.py?hl=en&answer=37227
whatsnew.googleapps.com
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Subscribe to:
Posts (Atom)