Google Groups Home Help | Sign in
The new Maps API ads layer: Released and ready for you to try
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  Messages 1 - 25 of 39 - Collapse all   Newer >
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
pamela (Google Employee)  
View profile
 More options Jul 27 2007, 2:58 pm
From: "pamela (Google Employee)" <api.pamela...@google.com>
Date: Fri, 27 Jul 2007 11:58:51 -0700
Local: Fri, Jul 27 2007 2:58 pm
Subject: The new Maps API ads layer: Released and ready for you to try
Hi developers,

At Developer Day in May, we previewed GAdsManager, a class that would
place contextual ad markers for local businesses in a special layer on
your map and help you monetize it. We've now released the ads layer
with the addition of GAdsManager in Maps API v2.85, and it's ready for
early testers. The reference for GAdsManager is available here:
http://www.google.com/apis/maps/documentation/reference.html#GAdsManager

I've put together a demo of the ads layer here:
http://imagine-it.org/google/gmaps-samples/adslayer/adslayer.html
(Note: This demo isn't in the usual gmaps-samples.googlecode.com
account due to the robots.txt being too restrictive there)

After loading that page and waiting for a few seconds, you should see
a white marker show up-this is an ad in the ads layer. If you click on
the marker, you should see the text and logo of this ad, for a hotel.
If you pan to New York City, you'll probably see another hotel ad show
up. Since this feature is in its very early stages, our local ad
inventory is small and you might notice that only a limited number of
ads show up. As we roll out this program to more advertisers, we
expect to see an increase in ad inventory and thus an increase in the
number of ads that show up in the ads layer on your map. Currently,
the feature only shows ads for businesses in US. Apologies to our
(many) international developers, who can, however, still implement the
ads layer in advance of international ad inventory becoming available.

Here are the steps you should take if you'd like to use the ads layer
on your maps:

1) Sign up for an AdSense account at adsense.google.com if you do not
already have one. Generally it takes a day or less for an account to
be approved.
2) You will need your AdSense for Content publisher ID to enable ads.
To find your unique AdSense for Content publisher ID number, log into
your AdSense account at adsense.google.com. On the My Account tab,
scroll down to the Property Information section. Your publisher ID for
AdSense for Content will be displayed in this section.
3) Make sure you're using v2.85 or later of the Maps API and put the
following code in your javascript (replacing the publisher ID, ca-pub-
xxxxxxxxxxxxxxxx, with your own):

        var adsManager = new GAdsManager(map, "ca-pub-
xxxxxxxxxxxxxxxx");
        adsManager.enable();

4) Visit your page now. If your page has never been crawled by the
Google bot before, this will force a crawl of your page. Make sure
your robots.txt allows crawling of the page (more info on that is
here: http://www.google.com/support/webmasters/bin/topic.py?topic=8843).
Wait 2-24 hours for the crawl to finish. After the crawl, AdSense will
understand the content of your page and be able to serve context-
sensitive ads (like the hotel ads for my demo page.)

You should now see ad markers from the ads layer show up on your map.
If you're having issues or have comments, please share them in this
thread. This is a new program and we'll definitely be working on
improving it to make it even better for you.

- pamela


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
TPKeller  
View profile
 More options Jul 27 2007, 4:43 pm
From: TPKeller <TPKel...@gmail.com>
Date: Fri, 27 Jul 2007 13:43:37 -0700
Local: Fri, Jul 27 2007 4:43 pm
Subject: Re: The new Maps API ads layer: Released and ready for you to try
On Jul 27, 2:58 pm, "pamela (Google Employee)"

Hmm... maybe this is a good sign that AdSense for Local Search is
closer?  :-)

Theron


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
singularity  
View profile
 More options Jul 28 2007, 2:30 am
From: singularity <tikut...@gmail.com>
Date: Sat, 28 Jul 2007 15:30:48 +0900
Local: Sat, Jul 28 2007 2:30 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try

I am an international developer, so I don't expect this to work, but it is a
minute's job to implement, so I did, on a test site.

I think the problem developers face with this is the same problem as they
face with ordinary google ads on the maps websites - how to show the
"context" to the googlebot to get the right ads. This is a general problem
with sites that are heavily ajax driven.

On your page, you have a whole load of text based guff about hotels - which
is necessary to force the context to show hotel adverts. In other words - to
make the fancy web 2 advert system work, you had to throw in a whole load of
"steam-web" text for the googlebot to crunch on. And that is a problem - it
means that to benefit from this, I have to abandon all my fancy web 2
overlays and so on - and put in a load of - essentially redundant - text on
each page, solely for the benefit of the googlebot.

Now - it is true I can do this between the noscript tags - the googlebot
will still see it, the ordinary user won't - but showing things to the
googlebot that one does not show to ordinary users of a site is generally
"frowned on".

Lets say I have data for transportation, for hotels, hot springs, shops,
restaurants - and that a user can overlay them onto a map for a whole
country. But the overlays are all done in .js,

How can I keep the site web2, while issuing the right context data to the
googlebot to ensure I get relevant ads?

In other words, your demo would have been far, far more impressive, had it
worked WITHOUT the steam-web text on the page about hotels.

V
http://diddlefinger.com

On 28/07/07, TPKeller <TPKel...@gmail.com> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
maps.huge.info  
View profile
 More options Jul 28 2007, 3:39 am
From: "maps.huge.info" <cor...@gmail.com>
Date: Sat, 28 Jul 2007 07:39:13 -0000
Local: Sat, Jul 28 2007 3:39 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
Pamela,

Thank everyone on the team for adding this. I'm sure this will be a
great addition for everyone who uses AdSense.

I'll be looking for local ads in Australia! I have a new mashup of
Australian postcodes coming online soon.

-John Coryat

http://maps.huge.info / http://www.usnaviguide.com


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Pil  
View profile
 More options Jul 28 2007, 4:05 am
From: Pil <wolf...@gmail.com>
Date: Sat, 28 Jul 2007 01:05:02 -0700
Local: Sat, Jul 28 2007 4:05 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
Google's original intention to display only relevant ads is great.

But meanwhile it is sometimes fooled by the advertisers themselves.
When loading this help page for example I often saw a link inside of
the column
'Sponsored Links' called 'Javascript jobs' or the like. Clicking on
this link revealed that the offering had nothing to do with javascript
at all.

I suppose there's nothing that can be done from Google side against
this misuse.

But if the user cannot trust in Googles original intention, and even
Google cannot
trust in it, then there's not very much left of the original purpose.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
maps.huge.info  
View profile
 More options Jul 28 2007, 4:24 am
From: "maps.huge.info" <cor...@gmail.com>
Date: Sat, 28 Jul 2007 08:24:30 -0000
Local: Sat, Jul 28 2007 4:24 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
On the positive side, with each ad group there is a link back to
Google with a way to easily report such ads. From what I understand,
Google takes problems such as this very seriously and will do
something about it if they are reported. I suggest you make sure to
report any such infractions as I do for the good of all involved.

-John Coryat

http://maps.huge.info / http://www.usnaviguide.com


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mike Williams  
View profile
 More options Jul 28 2007, 4:46 am
From: Mike Williams <nos...@econym.demon.co.uk>
Date: Sat, 28 Jul 2007 09:46:49 +0100
Local: Sat, Jul 28 2007 4:46 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
Wasn't it Pil who wrote:

>Google's original intention to display only relevant ads is great.

>But meanwhile it is sometimes fooled by the advertisers themselves.
>When loading this help page for example I often saw a link inside of
>the column
>'Sponsored Links' called 'Javascript jobs' or the like. Clicking on
>this link revealed that the offering had nothing to do with javascript
>at all.

>I suppose there's nothing that can be done from Google side against
>this misuse.

There's at least two things that help to reduce such misuse:

The Google AdWords system has a "quality score" calculation that, among
other things, attempts to calculate how relevant the advert is to the
landing page. (Advertisers can overcome a low quality score by paying
more per click.)

If you click on a sponsored link, and then find that the sponsor isn't
selling what you expected, then you're fairly unlikely to spend money
with them. The advertiser might eventually learn that they're paying
Google good money to attract people to visit their site, but not
converting many of those visits into sales. Google provide performance
analysis tools within the AdWords system which help the advertisers
detect such situations.

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
mctones@googlemail.com  
View profile
 More options Jul 28 2007, 6:27 am
From: "mcto...@googlemail.com" <mcto...@googlemail.com>
Date: Sat, 28 Jul 2007 10:27:27 -0000
Local: Sat, Jul 28 2007 6:27 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
Picking up on singularity's point, imho it would be good to dispense
with the googlebot altogether and implement a keyword parameter into
GAdsManager to decide which ads are displayed.

var adsManagerOptions = {
maxAdsOnMap: 10,
keywords: "hotels,restaurants,bars"

};

GAdsManager(map,  publisherId,  adsManagerOptions)

That way developers can have greater control over the ads, depending
on what the user is doing on their site. More targeted ads can only be
better for both parties as relevant links get clicked!

my $0.02, tones


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
the1geek  
View profile
 More options Jul 28 2007, 6:43 am
From: the1geek <the1g...@gmail.com>
Date: Sat, 28 Jul 2007 03:43:35 -0700
Local: Sat, Jul 28 2007 6:43 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
I like your idea McTone!

~newton

On Jul 28, 3:27 am, "mcto...@googlemail.com" <mcto...@googlemail.com>
wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
pamela (Google Employee)  
View profile
 More options Jul 28 2007, 11:19 am
From: "pamela (Google Employee)" <api.pamela...@google.com>
Date: Sat, 28 Jul 2007 08:19:03 -0700
Local: Sat, Jul 28 2007 11:19 am
Subject: Re: The new Maps API ads layer: Released and ready for you to try
Hi all-
Thanks for the input, please keep it coming. Let me clarify that I
haven't actually tried removing the extra hotels paragraph on my page
to see if I'll get the same ads. Another demo without the paragraph is
here: http://imagine-it.org/google/gmaps-samples/adslayer/adslayer_lesstext...
So far, I'm seeing the same ads. But I agree with you that there
should be a way to keep sites web2.0 and still informative to the
Googlebot. I'll try to get an answer for you on that issue.

If anyone tries this out and puts together a demo page (hopefully for
something other than hotels), please post a link so we can check out
what ads you're getting.

Thanks! - pamela

On Jul 28, 3:43 am, the1geek <the1g...@gmail.com> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
singularity  
View profile
 More options Jul 28 2007, 10:20 pm
From: singularity <tikut...@gmail.com>
Date: Sun, 29 Jul 2007 11:20:21 +0900
Local: Sat, Jul 28 2007 10:20 pm
Subject: Re: The new Maps API ads layer: Released and ready for you to try

Hi
First, my apologies if my original post seemed more than usually ungracious
- I certainly appreciate all the hard work that has gone into this. It could
transform the economics of mashups.

I have looked at the steam-web lite page you posted - and yes, you get the
same ad. But it still means that one would have to have a different 'page'
for every category one wants relevant ads for - each with a different title,
and snippet of text.

I think ultimately there is no other solution than to allow the developer to
control the Ad context - or - if not control - at least "hint". Undoubtedly
this would lead to abuse - but Adsense has to cope with heavy abuse in its
current steam-web incarnation - so the question is whether it would lead to
MORE abuse - and that I doubt.

It is a fundamental problem: ajax websites break the relationship between
content and a URL. Adsense relies on there being a direct relationship
between content and URL to establish context.  We try to hack our way around
it by doing page refreshes that are completely unnecessary except as a way
of giving the desired context to Adsense.

My website has about 10000 "pages" (as in 10,000 URLs) . 9999 of them are
completely unnecessary. I could do the same thing with ajax through one URL.
They are there - essentially - for the adsense crawler. (This is not to say
they are redundant - they are used heavily - just that they could have been
implemented through one URL)

I do look forward to any hints and tips about how to show context without
page refreshes to different URLs (with their different title tags)

V.

On 29/07/07, pamela (Google Employee) <api.pamela...@google.com> wrote: