Digest for seo-professionals@googlegroups.com - 3 Messages in 1 Topic

  Today's Topic Summary

Group: http://groups.google.com/group/seo-professionals/topics

• Google Algorithm update??? [3 Updates]

 Google Algorithm update???

Kunal Pawar <kunal4uonly@gmail.com> Dec 07 11:36AM +0530  

Hello Friends,
 
Any idea whether there has been any change in Google Algorithm recently?
 
Observing fluctuations with few of my keyword rankings. Hence, thought to
check on the same.
 
Thanks in advance.
 
Kunal.


 

"cybercrafts.india@gmail.com" <cybercrafts.india@gmail.com> Dec 07 11:50AM +0530  

Some of our websites are observing more traffic from the past month
though there was hardly any SEO work done on them.
 
Regards
Khan
 
On 07-Dec-12 11:36 AM, Kunal Pawar wrote:


 

Raviraj Tak <smile4ursmile@gmail.com> Dec 07 12:34PM +0530  

Hey Friends,
 
I have also seen some changes in my website keyword position..
 
But not sure if there is any updates, Also google rolls out many algorithms
in the back-end for every-month.
 
Lets see for more 2 to 3 days and make a report.
 
Regards,
Raviraj
 
On Fri, Dec 7, 2012 at 11:50 AM, cybercrafts.india@gmail.com <
>> check on the same.
 
>> Thanks in advance.
 
>> Kunal.
 
--
*
(¨`•.•´¨) Always
`•.¸(¨`•.•´¨) Keep
(¨`•.•´¨)¸.•´ Smiling!
`•.¸.•´
(
 
 
Every One has a ' Best Friend ' during each Stage of Life.......!
Only Lucky Ones have the Same Friend in all Stages of Life...!*


 

You received this message because you are subscribed to the Google Group seo-professionals.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

Digest for adsense-api@googlegroups.com - 9 Messages in 4 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• v4 add url channel, client id not acknowledged as valid [3 Updates]
• AdSense Host API v4.1 has launched! [4 Updates]
• Force ads to display [1 Update]
• [0-59714289] AdSense Host API Access [1 Update]

 v4 add url channel, client id not acknowledged as valid

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Dec 06 05:34AM -0800  

---
Jose Alcérreca
Developer Relations
Hi!
 
Publisher channels will not be accessible from v4.1, I'm afraid. You will
be able to access the same data, but not with the old channels. You can
create new ones when generating ad code and they will start collecting data
from that point.
 
Cheers,
Jose
 
 
---
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* | developers
.google.com/adsense <https://developers.google.com/adsense/>
 
On Thursday, 6 December 2012 01:55:22 UTC, Group Participant wrote:


 

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Dec 06 05:36AM -0800  

Hi!
 
Publisher channels will not be accessible from v4.1, I'm afraid. You will
be able to access the same data, but not with the old channels. You can
create new ones when generating ad code and they will start collecting data
from that point.
 
Cheers,
Jose
 
---
Jose Alcérreca
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* | developers
.google.com/adsense <https://developers.google.com/adsense/>
 
On Thursday, 6 December 2012 01:55:22 UTC, Group Participant wrote:


 

Group Participant <genieejeenee@gmail.com> Dec 07 12:41AM -0800  

Is the following correct?
 
Given:
1. Publisher channel p1 is associated with adunit a1.
2. a1 contains data; let's give the data the label d1.
 
With v3 I called ReportService.generate with p1 to get d1. With v4.1,
accessing p1 is no longer possible, and so d1 cannot be accessed in the
same manner as v3.
 
In order to access d1 via v4.1:
1. A host channel h1 is created.
2. h1 is set to be associated with a1.
3. Calling Reports.generate with CUSTOM_CHANNEL_ID==h1 as a filter will
return d1.
 
2012年12月6日木曜日 22時36分41秒 UTC+9 Jose Alcérreca (AdSense API Team):


 

 AdSense Host API v4.1 has launched!

Ashbey <ppashesh@gmail.com> Dec 06 03:32AM -0800  

Thanks for the helpful video https://www.youtube.com/watch?v=x71eomcpcdw . I
suspect you did not get any viewer questions because everything was so well
explained.

I am stuck at API console still showing "Request access" link against
"AdSense Host API". I have already filled and submitted the form few times
and did it again just now.

Can you please help me with this?

 
On Wednesday, September 26, 2012 9:24:00 PM UTC+5:30, Ashesh Bharadwaj
wrote:
 


 

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 06 06:05AM -0800  

Hi there,
 
Thank you, good to hear the video was helpful! :)
 
Your entry only seems to have come in today, I'm afraid. We'll be setting
you up with your new sandbox account early next week, hope that works for
you.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Thursday, 6 December 2012 11:32:03 UTC, Ashbey wrote:


 

Ashesh Bharadwaj <ashesh@paradisepublishers.com> Dec 06 07:45PM +0530  

Thanks Sérgio for the prompt reply. Not an issue.
 
I am still struggling to get a working example for AdSense publisher
signup. Instead of going through the REST implementation directly I was
inclidned using the Google client library but it seems the library
http://code.google.com/p/google-api-php-client/downloads/detail?name=google-api-php-client-0.6.0.tar.gz&can=2&q=
is still not functional.
 
Is it possible to have a working example for the following page:
 
https://developers.google.com/adsense/host/signup
 
 
On Thu, Dec 6, 2012 at 7:35 PM, Sérgio Gomes (AdSense API Team) <
 
--
Regards,
 
Ashesh Bharadwaj


 

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 06 09:35AM -0800  

Hi there,
 
The PHP client library hasn't done a release since adding support for the
AdSense Host API, but it is there; you'll just need to check out the
current version of the repository instead of downloading a package. Here
are some details on how to do
it: http://code.google.com/p/google-api-php-client/source/checkout
 
Hope this helps!
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Thursday, 6 December 2012 14:15:01 UTC, Ashesh Bharadwaj wrote:


 

 Force ads to display

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 06 05:59AM -0800  

Hi!
 
I just wanted to jump in and say that by authenticating with your live
account you're not displaying banners with the sandbox account; in fact
you're fully using your live account and any ads that get shown on it will
be counted towards your stats there. Any modifications you make will also
affect your live account.
 
I would therefore advise caution in testing things out this way; it's a
good idea to stick to read-only calls, for example.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Thursday, 6 December 2012 02:48:56 UTC, Group Participant wrote:


 

 [0-59714289] AdSense Host API Access

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 06 05:56AM -0800  

Hi Nicolas,
 
We seem to have only received your submission earlier today. There seems to
have been an earlier one, but it was incomplete, so it got rejected,
apologies for that.
 
We should be able to get your sandbox account sorted out early next week.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Wednesday, 5 December 2012 17:05:02 UTC, Nicolas Gremion wrote:


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

Digest for adsense-api@googlegroups.com - 7 Messages in 5 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• Force ads to display [2 Updates]
• v4 add url channel, client id not acknowledged as valid [2 Updates]
• [0-59714289] AdSense Host API Access [1 Update]
• Do I Need The Adsense API? [1 Update]
• Migrating v3.0 generateAdCode to 4.1 [1 Update]

 Force ads to display

Darian Shimy <dshimy@weebly.com> Dec 05 09:24AM -0800  

> While I'm at it here, could you share in a nutshell how you're doing the
> live account authentication/sandbox account API calls?
 
For the API calls we are using the PHP library
http://code.google.com/p/google-api-php-client/
 
The examples for the Adsense Host API seemed out of date with the version
we were using so I followed this link for the authorization:
 

http://code.google.com/p/google-api-php-client/source/browse/trunk/examples/userinfo/index.php
 
After that we just added the start association.


 

Group Participant <genieejeenee@gmail.com> Dec 05 06:48PM -0800  

Wait a second; if you aren't seeing banners that means you aren't being
authenticated with your live account. I was told that authenticating using
your live account is the way to display banners using the sandbox account.
 
2012年12月6日木曜日 2時24分30秒 UTC+9 Darian Shimy:


 

 v4 add url channel, client id not acknowledged as valid

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Dec 05 05:21AM -0800  

Hi,
 
What specific data do you need to access? Host data from the publishers'
channels or publisher data?
 
Cheers,
Jose
 
---
Jose Alcérreca
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* | developers
.google.com/adsense <https://developers.google.com/adsense/>
 
On Monday, 3 December 2012 23:15:16 UTC, Group Participant wrote:


 

Group Participant <genieejeenee@gmail.com> Dec 05 05:55PM -0800  

In the current v3 application, the channels for which reports are being
generated correspond with client ids. That is, channels are retrieved for
a given client id and reports are generated for those channels. The
specific data I need to access is that of client channels.
 
I assume that clients are associated with publishers but not hosts. If
that is correct, then I also assume that the client data is considered
publisher data.
 
2012年12月5日水曜日 22時21分39秒 UTC+9 Jose Alcérreca (AdSense API Team):


 

 [0-59714289] AdSense Host API Access

"Nicolas Gremion" <nic@paradisepublishers.com> Dec 05 11:05AM -0600  

Hi Sérgio,
 

 
Any news on the sandbox accounts? Thanks,
 

 
Nicolas Gremion
 
www.ParadisePublishers.com <http://www.paradisepublishers.com/>
 

 
"We are what we repeatedly do. Excellence, then, is not an act, but a habit" Aristotle
 

 
INADVERTENT DISCLOSURE: The information contained herein is confidential information intended only for the use of the addressee(s). If you received this email and you are not in the "to" or "cc" line, it means that this is an inadvertent disclosure, and you are hereby notified that I am invoking the "inadvertent disclosure rule". You now have an ethical duty (i) to immediately delete the email without reading it, or (ii) to notify the sender and return it. If you are not the intended recipient of this email, you have no right to the contents of it. Information included in this email does not constitute a trade confirmation or an offer or solicitation of an offer to buy/sell securities. Past performance is not indicative of future returns.
 

 
Some of the information in this email contains forward-looking statements within the meaning of the federal securities laws. Forward-looking statements typically are identified by use of terms such as "anticipate," "believe," "plan," "expect," "future," "intend," "may," "will," "should," "estimate," "predict," "potential," "continue," and similar words, although some forward-looking statements address matters that involve risk and uncertainties, and there are many important risks, uncertainties and other factors that could cause the Company's actual results, as well as those of the markets the Company serves, levels of activity, performance, achievements and prospects to differ materially from the forward-looking statements contained in this email. The Company undertakes no obligation to publicly update or review any forward-looking statements, whether as a result of a new information, future developments or otherwise.
 

 
##
 

 
From: adsense-api@googlegroups.com [mailto:adsense-api@googlegroups.com]
Sent: Wednesday, October 03, 2012 9:51 AM
To: nic@paradisepublishers.com
Subject: RE: [0-59714289] AdSense Host API Access
 

 
Yes, that email address doesn't seem to be connected to any AdSense account, so it will work nicely.
 

 
I'll get in touch with you once we have your sandbox account set up!
 

 
Cheers,
 
Sérgio
 

 
---
 
Sérgio Gomes
 
Developer Relations
 

 
Google UK Limited
 
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ
 
Registered in England Number: 3977902
 

 
Google Inc.| Developer Relations | AdSense API Team | <https://developers.google.com/adsense/> developers.google.com/adsense
 
Follow us on our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer page on Google+ and our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer Blog to learn more about the different Ads APIs at Google.
 

 
 
On 10/03/12 15:57:51 "Nicolas Gremion" <nic@paradisepublishers.com> wrote:
 
Thanks for your quick reply Sérgio! Can you use our developer's email which is ppashesh@gmail.com for the sandbox account?
 

 

 
Nicolas Gremion
 
www.ParadisePublishers.com <http://www.paradisepublishers.com/>
 

 
"We are what we repeatedly do. Excellence, then, is not an act, but a habit" Aristotle
 

 
INADVERTENT DISCLOSURE: The information contained herein is confidential information intended only for the use of the addressee(s). If you received this email and you are not in the "to" or "cc" line, it means that this is an inadvertent disclosure, and you are hereby notified that I am invoking the "inadvertent disclosure rule". You now have an ethical duty (i) to immediately delete the email without reading it, or (ii) to notify the sender and return it. If you are not the intended recipient of this email, you have no right to the contents of it. Information included in this email does not constitute a trade confirmation or an offer or solicitation of an offer to buy/sell securities. Past performance is not indicative of future returns.
 

 
Some of the information in this email contains forward-looking statements within the meaning of the federal securities laws. Forward-looking statements typically are identified by use of terms such as "anticipate," "believe," "plan," "expect," "future," "intend," "may," "will," "should," "estimate," "predict," "potential," "continue," and similar words, although some forward-looking statements address matters that involve risk and uncertainties, and there are many important risks, uncertainties and other factors that could cause the Company's actual results, as well as those of the markets the Company serves, levels of activity, performance, achievements and prospects to differ materially from the forward-looking statements contained in this email. The Company undertakes no obligation to publicly update or review any forward-looking statements, whether as a result of a new information, future developments or otherwise.
 

 
##
 

 
From: adsense-api@googlegroups.com [mailto:adsense-api@googlegroups.com]
Sent: Wednesday, October 03, 2012 8:30 AM
To: nic@paradisepublishers.com
Subject: RE: [0-59714289] AdSense Host API Access
 

 
Hey Nicolas,
 

 
We have a new sandbox in v4.1, which runs on the same environment as production; the only difference is that sandbox host accounts are marked as "sandbox" in our database, do not show ads, and can only create (and be associated) with sandbox publisher accounts.
 

 
This means you can use the AdSense website to inspect and modify the accounts for your API testing, and you won't have to change your endpoint when switching accounts between sandbox and production, at the end of your migration.
 

 
Given this, could you provide me with a working email address that you'd like tied to your new sandbox host account? Remember that it can't be tied to any other AdSense account, as the goal is to point it to the new one.
 

 
If you use GMail, you can try the "+" trick; if you send an email to foo+bar@google.com, it'll show up in foo@google.com, but if you create a new Google account with this email, it'll actually be a separate Google account. You can also use this trick once you get access and start creating publisher accounts, to reduce the number of email accounts you need to create.
 

 
Let me know if you have any questions!
 

 
Cheers,
 
Sérgio
 

 
---
 
Sérgio Gomes
 
Developer Relations
 

 
Google UK Limited
 
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ
 
Registered in England Number: 3977902
 

 
Google Inc.| Developer Relations | AdSense API Team | <https://developers.google.com/adsense/> developers.google.com/adsense
 
Follow us on our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer page on Google+ and our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer Blog to learn more about the different Ads APIs at Google.
 

 
 
On 10/03/12 15:19:33 adsense-api@googlegroups.com wrote:
 
Hi Nicolas,
 

 
Apologies for the delay, we're just finalising the sandbox account creation process at the moment. I'll send you a private email with more details.
 

 
Cheers,
 
Sérgio
 

 
---
 
Sérgio Gomes
 
Developer Relations
 

 
Google UK Limited
 
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ
 
Registered in England Number: 3977902
 

 
Google Inc.| Developer Relations | AdSense API Team | <https://developers.google.com/adsense/> developers.google.com/adsense
 
Follow us on our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer page on Google+ and our <https://plus.google.com/115658573333388777174/posts> Google Ads Developer Blog to learn more about the different Ads APIs at Google.
 

 
 
On 10/03/12 14:26:49 "Nicolas Gremion" <nic@paradisepublishers.com> wrote:
 
It has been more than a week I have requested for access to AdSense Host API (default quota) through console. I got a "Your response has been recorded" when I submitted. Any idea how much time does it take?
 
--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/adsense-api/-/_DfCTLeaCSYJ.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.
 
--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.


 

 Do I Need The Adsense API?

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Dec 05 03:53AM -0800  

Hi Sebastian,
 
That is a question for the AdSense folks, this is the AdSense API forum.
However, your project seems like a good candidate for the AdSense Host API.
If you meet certain requirements<https://developers.google.com/adsense/host/gettingstarted> (100,000+
page views/day being the most important) you can become a partner.
 
Cheers,
Jose
 
---
Jose Alcérreca
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* |
developers.google.com/adsense
 
On Tuesday, 4 December 2012 13:21:38 UTC, Sebastian Facundo wrote:


 

 Migrating v3.0 generateAdCode to 4.1

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 05 01:59AM -0800  

Hi Darian,
 
Old-style ad code will continue working, yes; ads will still be displayed
and revenue will still be shared correctly. As you point out, though,
certain new features (like publisher-side reporting) will not work, though,
as well as any new features we may add in later versions that depend on ad
units.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
On Wednesday, 5 December 2012 01:48:59 UTC, Darian Shimy wrote:


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

[Inside AdSense] Working better together: Protecting against invalid activity

Publishers are the lifeblood of the Internet, and we're committed to helping you grow your businesses. Last year alone, we shared $6.5 billion with our AdSense publishers. We also invest immense amounts of time and millions of dollars in systems (including sophisticated algorithms and human reviews) that keep bad ads from appearing on your sites and prevent advertisers from being fraudulently charged for bad clicks. When everything is working well, advertisers trust our network and continue to invest in it, which generates revenue for you the publisher, ultimately funding the free content users love.

But we've also heard the stories: publishers finding their accounts suspended or even disabled for "invalid activity" without a clear understanding of why or how to fix it. We know this can be an intensely frustrating, even scary experience. So why does this happen?

While the vast majority of publishers who sign up for AdSense do so in good faith, unfortunately there are some bad actors out there.  As you can imagine, we can't reveal all the tools we use to keep bad sites and bad traffic out of our network.  But sometimes these tools result in good publishers who become a source of invalid activity having their accounts disabled without much recourse.  We're making some changes we think will help fix this:

• We are considering tenure more actively when responding to detected invalid activity. For example, some trusted publishers will now have their accounts suspended instead of terminated, and over time we hope to work directly with more publishers to resolve invalid traffic issues without needing to disable the account at all. (As always, we'll continue to credit advertisers for any invalid activity.)
• We've given publishers tools to submit more informative appeals via a new form, which may help resolve issues more quickly.
• We're providing more details on invalid activity's causes. If we've detected a violation of our policies you'll receive an email and a notification to your account with further information and instructions. And you can read all about the causes of invalid activity at our Ad Traffic Quality Resource Center, which is now available in most languages supported by AdSense, such as German, French, Polish and Arabic.
• Whether you're looking for a refresher or just creating your first ad unit, you can review the do's and don'ts of ad traffic in our expanded AdSense Academy. 
• In order to help publishers avoid common pitfalls, we're kicking off a video series that explains why some of our policies exist and how you can make sure you're working with them. Our first looks specifically at invalid traffic.

http://www.youtube.com/watch?v=W6YI1E1-M-4


We want to work with our publisher partners to keep the AdSense network strong -- keeping good publishers' accounts in good standing, while also protecting advertisers and users from fraudulent activity. This is why we're making changes, like the ones discussed today, to provide more help when things go wrong. We'll be making even more changes as the year goes on so look for continued updates on this blog.

Posted by Jonathan Bellack - Product Management Director

We want to hear from you. Let's continue the conversation -- submit your questions to us about the topics discussed in this post via Google Moderator. We'll be holding a Google Hangout in January with members of our Product Quality Operations team for the first time to address your questions. Please note that for privacy reasons, we won't be able to respond to account-specific questions.

--
Posted By Inside AdSense Team to Inside AdSense at 12/05/2012 07:00:00 AM

--
Unable to view the links or images in the message above? Want to comment on this post? Visit http://adsense.blogspot.com/ .
 
You received this message because you are subscribed to the Google Groups "Inside AdSense" group.
To unsubscribe from this group, send email to Inside-AdSense+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Inside-AdSense

Digest for adsense-api@googlegroups.com - 10 Messages in 5 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• SiteFilterService - v4.1 equivalent [1 Update]
• SiteFilterService - v4.1 equivalent [1 Update]
• Force ads to display [4 Updates]
• Migrating v3.0 generateAdCode to 4.1 [3 Updates]
• Do I Need The Adsense API? [1 Update]

 SiteFilterService - v4.1 equivalent

Group Participant <genieejeenee@gmail.com> Dec 04 07:56PM -0800  

I couldn't find it in the documentation or in a quick browsing of the php
client source. How is site filtering done in v4?


 

 SiteFilterService - v4.1 equivalent

Group Participant <genieejeenee@gmail.com> Dec 04 07:55PM -0800  

I couldn't find it in the documentation or in a quick browsing of the php
client source. How is site filtering done in v4?


 

 Force ads to display

Darian Shimy <dshimy@weebly.com> Dec 04 05:45PM -0800  

In our sandbox accounts (for the Host API), is there a way to force ads to
display on the publisher's sites? This would be very useful for testing.
Thanks.


 

Group Participant <genieejeenee@gmail.com> Dec 04 06:06PM -0800  

This is what I was told via email:
 
If you just need to run some quick tests, you can use the same developer
> credentials you already have, but authenticate with your real, live
> account. That should give you access to all the functionality, on your live
> account.
 
How to use the live account for authentication only and then use the
sandbox account for API calls I've yet to figure out.
 
2012年12月5日水曜日 10時45分52秒 UTC+9 Darian Shimy:


 

Darian Shimy <dshimy@weebly.com> Dec 04 06:10PM -0800  

Thanks for the response. That is what I was told as well, (and I am doing
that), but I'm trying to get the ads to display. I see the Javascript on
the page, but no ads yet. Is there a way to force placeholder ads to
display?
 
On Tuesday, December 4, 2012 6:06:55 PM UTC-8, Group Participant wrote:


 

Group Participant <genieejeenee@gmail.com> Dec 04 06:21PM -0800  

I'd assume no. The sandbox doesn't display ads at all, of any type, dummy
placeholders or otherwise. You'd have to somehow mock out the JS in the
generated ad tag to add your own logic for showing a placeholder.
 
While I'm at it here, could you share in a nutshell how you're doing the
live account authentication/sandbox account API calls?
 
2012年12月5日水曜日 11時10分54秒 UTC+9 Darian Shimy:


 

 Migrating v3.0 generateAdCode to 4.1

Filippo Silvestro <filippo.silvestro@altervista.it> Dec 04 02:11AM -0800  

Is there a guide or some examples that show how to create ad units? I'm
trying with the Api Explorer, but I always get the error "Supplied ad unit
is missing one or more required values" or "Invalid value".
I can't find in the documentation the allowed values for each field and
which ones are compulsory.
 
Il giorno lunedì 3 dicembre 2012 15:09:09 UTC+1, Sérgio Gomes (AdSense API
Team) ha scritto:


 

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 04 06:09AM -0800  

Hi Filippo,
 
Here are the samples for Java, we hope to have them for other languages
soon:
http://code.google.com/p/google-api-java-client/wiki/APIs#AdSense_Host_API
 
And the direct sample you're interested in, from the repository:
http://code.google.com/p/google-api-java-client/source/browse/adsensehost-cmdline-sample/src/main/java/com/google/api/services/samples/adsensehost/cmdline/AddAdUnitToPublisher.java?repo=samples
 
We'll be adding these values to the docs as well, once we iron out a few
issues with our automatic generation.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
On Tuesday, 4 December 2012 10:11:53 UTC, Filippo Silvestro wrote:


 

Darian Shimy <dshimy@weebly.com> Dec 04 05:48PM -0800  

My preference would be to use the old style code. This is what we use
today:
 
<script type="text/javascript"><!--
google_ad_client="pub-YYYY";
google_ad_host="pub-XXXX";
google_alternate_color="003366";
google_ad_width=250;
google_ad_height=250;
google_ad_format="250x250_as";
google_ad_type="text";
google_color_border="6699CC";
google_color_bg="003366";
google_color_link="FFFFFF";
google_color_url="AECCEB";
google_color_text="AECCEB";
//--></script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
 
 
As you can see, there is nothing other than the google_ad_client that needs
to change. We are not interested in the added reporting features that come
with the Ad Units. Will this continue to work in the new system?
 
 
On Monday, December 3, 2012 6:09:09 AM UTC-8, Sérgio Gomes (AdSense API
Team) wrote:


 

 Do I Need The Adsense API?

Sebastian Facundo <thespainxperience@gmail.com> Dec 04 05:21AM -0800  

HI!
 
I'm developing a digital magazine, where the contribuitors will post and
their Adsense Banners will appear in their own post, to win de 100% of the
profits of their Ads.
 
Now my problem is that they can't register with the same URL,
www.example.com, because they're hundreds and the Adsense registration
platform doesn't allow it.
 
Will I solve that problem With the Adsense API?
 
Thanks in advance


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

[WD&D] Digest for sitedesign@googlegroups.com - 11 Messages in 2 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/sitedesign/topics

• [No Subject] [1 Update]
• HTML Design flawed in IE [10 Updates]

 [No Subject]

Chad Bartels <chad.bartels@gmail.com> Nov 21 05:02AM -0800  

http://utahmarketingexpert.com/wp-content/plugins/likeit.php?friends953.img


 

 HTML Design flawed in IE

Binaek Sarkar <binaek89@gmail.com> Nov 12 05:05PM +0530  

Hello people. How's everybody?
 
I have been developing a website for the company I am currently working in.
 
The designer's father expired and now its upon my shoulders to finish this
within the next two days. And now I am presented with a strange (though not
unexpected problem. I am sure pretty all web designer have gone mad over
this at least once in life).
 
The website renders normally in *Chrome*. However, when i open it in IE 7
and below, it fails miserably.
 
I have tested it in IE8 and it displays properly. Therefore I am assuming
that it will also function properly in IE9 & IE10 (though I am not exactly
sure how correct this assumption is - as I do not have access to these
browsers)
 
Anyways, coming back to the point - *HELP!!!*
*
*
The URL is: http://mindcrew.net/codiad/workspace/Alumnus/index.html
 
PS: This is my private server and not the company server. And the *URL is
case-sensitive*.
*
*
Thank you
Binaek Sarkar


 

chris walker <customsitepro@gmail.com> Nov 12 08:48PM +0800  

Before you really go crazy, try installing the modernizr.js script and
seeing if that helps.


 

Binaek Sarkar <binaek89@gmail.com> Nov 12 06:33PM +0530  

@Chris...
 
Nope... Modernizr doesn't work..
 
I tried it only in the homepage. And the page didn't even show any sign of
remorse that its making me work on it so much...
 
:-(
 
Regards
Binaek Sarkar
 


 

Liam Kenneth <liam.kenneth89@gmail.com> Nov 12 02:13PM  

modernizr dont do shit just gives you classes to style if a browser is
missing a feature, but this may help: http://code.google.com/p/ie7-js/
 


 

C Parthapratim <c.parthapratim@gmail.com> Nov 12 10:10AM -0800  

First, .eot never worked smoothly with any version of IE.
 
Have you tried removing the Chrome specific CSS elements like this?
 
<link rel="stylesheet" type="text/css" media="screen"
href="chrome-extension://fcdjadjbdihbaodagojiomdljhjhjfho/css/atd.css">
 
And BTW, I have removed IE from my computer, for it is the crappiest
browser I have ever seen. IE's market share is NOT that big any more to be
worried about such display issue.
 
On Monday, November 12, 2012 5:05:49 PM UTC+5:30, Binaek Sarkar wrote:


 

Binaek Sarkar <binaek89@gmail.com> Nov 14 03:15PM +0530  

@Liam ::
 
I tried to get IE to behave properly by using the JS extensions, but its a
real arrogant SOB... Couldn't get it to work...
 
I could try by reslicing the PSDs and redoing the HTML, but that would
entail a lot of work and the release is due tomorrow (ie, 0000 hours IST,
14th Nov)... Even if I worked day in day out, I won't be able to get it
through...
 
Any ideas?
 
@Parthapratim ::
 
*First, .eot never worked smoothly with any version of IE.*
 
As far as I know, IE works with .eot files only. It cannot parse .TTF or
any other font format. I think its one of those Microsoft monopoly gimmicks
that they pull every now and then. We tried TTF, OTF and even WOFF, but
none of them seem to work.
 
 
*Have you tried removing the Chrome specific CSS elements like this? *
*<link rel="stylesheet" type="text/css" media="screen"
href="chrome-extension://fcdjadjbdihbaodagojiomdljhjhjfho/css/atd.css">*
 
The CSS style sheet you mentioned is specific to some particular Chrome
extension and will be there if and only if the visitor is using chrome,
with that extension installed. This line (emphasized) won't show up if you
open the same page in IE or Firefox or any other browser you care to open
in. Moreover, these extension specific CSS use a very specific naming
convention so that nomenclature conflict does not occur.
 
 
*And BTW, I have removed IE from my computer, for it is the crappiest
browser I have ever seen. IE's market share is NOT that big any more to be
worried about such display issue.*
 
I agree with you that IE does not exactly offer one of the pleasing
experiences when it comes to web browsing (may be not to such a high
degree, but mostly there)... However, it is not a question of the market
share of the browser - its about the interoperability. If it is not opening
in IE, that means something is wrong and I don't think its a good idea to
release a buggy website. After all, IT IS our bread and butter.
 
 
Regards
Binaek Sarkar
 


 

chris walker <customsitepro@gmail.com> Nov 14 06:08PM +0800  

More important than the market share of Internet explorer is who that
market share is. Government agencies do not allow anything other than
secure browsers on their networks. That eliminates Firefox, chrome, and
other browsers. It is the same thing with smartphone apps. The only
approved devices are blackberries, which compared to ios and android, is
suitable only as a paperweight.
 
If you are building a site that is of any relevance, it will need to be
compliant for those 3%ers. Those websites that have a target market of the
3% are also the best pay days for us fetching many times the budget of
vanity sites.


 

Binaek Sarkar <binaek89@gmail.com> Nov 14 04:07PM +0530  

@Chris:::
 
Agreed. I faced the same problem. I have a tendency of testing my HTML in
Chrome because of the neat Developer Tools that it offers. And the thing is
working perfectly in Chrome. However, the designer uses IE [:-)]...
 
He was the one who pointed out the flaw after about 3 rounds of HTMLising.
 
Anyways, I tried every possible plugin (JS and CSS) to get this thing to
work, but none of it seems to help. Any ideas???
 
Regards
Binaek Sarkar
 


 

Binaek Sarkar <binaek89@gmail.com> Nov 15 07:54PM +0530  

I solved the problem.
 
I never imagined it would be this easy and also that IE would be such a
lousy browser.
 
Since the layout is table based, its got a plethora of Table cells. Each
cell containing an image.
 
Now, what was happening was that after the *img *tag, ideally the
*td*should end, ie
*</td>*.
 
However, for readability, the HTMLizer left a newline after each *img *tag.
How angel of him !!!
 
Now IE was parsing this newline as a *text-node *in the DOM and leaving
space for it.
 
Hehe...
 
I had to manually remove all those newlines for it to work eventually...
 
Regards
Binaek Sarkar
Foundation
http://www.foundation.net.in/
 


 

C Parthapratim <c.parthapratim@gmail.com> Nov 15 09:22AM -0800  

Well, congrats, and at least you are convinced that IE is lousy! :)
 
 
On Thursday, November 15, 2012 7:55:12 PM UTC+5:30, Binaek Sarkar wrote:


 

You received this message because you are subscribed to the Google Group sitedesign.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this because you are subscribed to the "Web Design and Development" group at Google Groups. Messages are prefixed with [WD&D] in the subject. No spam is allowed. Be civil, be professional; try to be helpful & mind your netiquette. All posts are Copyright the original author and the Web Design and Development group. No reproduction of this content is allowed in any electronic or printed form outside the group at Google Groups and the http://www.WDaDg.org website. Any unauthorized use of our copy constitutes illegal Copyright infringement and may well be prosecuted to the full extent of the law. Digital Signature: $©"[W|D|&|D]g"|^|!SiteDesign@GG||#%$
To post to this group, email SiteDesign@googlegroups.com
To unsubscribe, email SiteDesign-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/SiteDesign?hl=en

Digest for seo-professionals@googlegroups.com - 1 Message in 1 Topic

  Today's Topic Summary

Group: http://groups.google.com/group/seo-professionals/topics

• Content Writers Required [1 Update]

 Content Writers Required

kavita pharande <kavitapharande25@gmail.com> Dec 04 01:01PM +0530  

Hello all,
 
I need bulk article content for my websites.Interested please contact with
your sample work and pricing.
 
Thanks,
Kavita
 
--
Keep Dreaming Always...
Regards,
Kavita M.Pharande
SEO SEM PPC Consultant
http://www.seoppcservicesonline.com
Mumbai 400706
+91 9819 737023


 

You received this message because you are subscribed to the Google Group seo-professionals.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

Digest for adsense-api@googlegroups.com - 8 Messages in 5 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• v4 add url channel, client id not acknowledged as valid [2 Updates]
• Users own Adense account [2 Updates]
• Migrating v3.0 generateAdCode to 4.1 [2 Updates]
• AdSense Host Api access [1 Update]
• sandbox reports [1 Update]

 v4 add url channel, client id not acknowledged as valid

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Dec 03 06:13AM -0800  

Hi again,
 
You don't need to manage publisher's channels anymore with v4.1. Now we use
host channels, so you can use channels across multiple publishers.
 
In order to use Custom Channels, set the optional argument (
hostCustomChannelId) when creating code for ad units. For URL channels,
create them using the URL pattern that matches your publisher's address.
These channels only belong to the host so you have access to them.
 
If you need to generate reports for a channel, use the dimensions
CUSTOM_CHANNEL_ID or URL_CHANNEL_ID to distinguish between them or, if you
want data for a particular channel, use filters as following:
 
filter=CUSTOM_CHANNEL_ID%3D%3D<your_custom_channel_id>
 
I hope this helps.
 
Cheers,
Jose
 
 
---
Jose Alcérreca
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* |
developers.google.com/adsense
 
On Monday, 3 December 2012 01:08:49 UTC, Group Participant wrote:


 

Group Participant <genieejeenee@gmail.com> Dec 03 03:15PM -0800  

Thank you for the reply, but I need a little more clarification, please.
 
Even if there is no longer a need to manage publishers' channels, there are
data associated with those channels. In the v3 application, reports are
generated for that data.
 
If the publishers' channels and the associated data cannot be accessed via
4.1, how can the report be generated for that data?
 
Is there an alternative way to access the same data and calculate report
results?
 
2012年12月3日月曜日 23時13分12秒 UTC+9 Jose Alcérreca (AdSense API Team):


 

 Users own Adense account

Morten Hjort <mortenhjort@gmail.com> Dec 03 02:46AM -0800  

I have an idea for custom artist-pages where the artists themself can earn
some money from advertising (with a split for us). However that means that
each user should be able to connect his/her own account where maybe 80% of
the revenue will go to, while the rest will go to us.
Is that doable with the Adsense API?


 

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 03 06:14AM -0800  

Hi Morten,
 
Sounds like the perfect use case for the AdSense Host API! Take a look at
our documentation on https://developers.google.com/adsense/host/ for more
information on the program.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Monday, 3 December 2012 10:46:51 UTC, Morten Hjort wrote:


 

 Migrating v3.0 generateAdCode to 4.1

poll bigger <pollandayker@gmail.com> Dec 01 04:05PM +0400  

yes
 


 

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 03 06:09AM -0800  

That's correct. The new Host API uses ad units (aka ad slots), so you'll
need to make sure both of these properties are correct, and that the ad
unit in question matches the sizes described in the template as well.
 
Also, don't forget google_ad_host for your revenue share!
 
Here is some sample generated code:
 
<script type=\"text/javascript\"><!--
google_ad_client = \"ca-pub-xxxxxxxxxxxxxxxx\";
google_ad_host = \"ca-host-pub-yyyyyyyyyyyyyyyy\";
/* Ad Unit x */
google_ad_slot = \"zzzzzzzzzz\";
google_ad_width = 200;
google_ad_height = 200;
//-->
</script>
<script type=\"text/javascript\"
src=\"http://pagead2.googlesyndication.com/pagead/show_ads.js\">
</script>
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
On Monday, 3 December 2012 07:56:15 UTC, Group Participant wrote:


 

 AdSense Host Api access

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 03 05:36AM -0800  

Hi Filippo,
 
You can do as you mention, although I would advise sticking to read-only
methods until you run your implementation through us. Once you do, we'll
give you a new set of developer credentials on your existing account, with
your production callback URL (should it be different from the sandbox one).
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
On Friday, 30 November 2012 10:20:07 UTC, Filippo Silvestro wrote:


 

 sandbox reports

"Sérgio Gomes (AdSense API Team)" <adsenseapiadvisor+sergio@google.com> Dec 03 05:34AM -0800  

Hi there,
 
Unfortunately, there's no way of adding any reporting data to sandbox
accounts. The only thing I can suggest is building a mock of the service
and working from there.
 
Cheers,
Sérgio
 
---
Sérgio Gomes
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
On Thursday, 29 November 2012 03:35:08 UTC, Group Participant wrote:


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

[Inside AdSense] Enhancing text ads on the Google Display Network

Text ads have proven to be a great way to help advertisers extend their Google search campaigns to sites in the Google Display Network, enabling publishers like you to earn revenue from your content. This is why we're continuing to work on improving text ads, even as we introduce new ad formats.

One change, rolling out this week, will make the look and feel of text ads more consistent as consumers and advertisers use screens interchangeably, and distinctions between devices fade. You'll notice a new clickable arrow icon, as well as slight optimizations to font size, spacing and text layout. These enhancements are among the largest that we have made to text ads, and our experiments indicate an uplift in clicks across publishers on the Google Display Network.

These changes will happen automatically for most text ads on your pages, and the color of the arrow icon will be based on the color palette you've selected for your ad units. For instance, if the background of your ad units is white, the icon will be grey; for other background colors, the icons will be a different shade of the background color. Consistent with our program policies, we ask that publishers refrain from mimicking these arrows or placing similar images around their ad units. Below are some example of this new text ad format in the 200x200 and 300x250 ad unit sizes.

200x200 Ad Unit

300x250 Ad Unit

We understand text ads are important to our publishers' business and we'll continue to innovate on new formats. Please feel free to share your feedback and suggestions with us on our AdSense +page; we look forward to helping you find new ways to grow your online businesses.

Posted by Johan Land and Stephen Yuan

--
Posted By Inside AdSense Team to Inside AdSense at 12/03/2012 12:01:00 PM

--
Unable to view the links or images in the message above? Want to comment on this post? Visit http://adsense.blogspot.com/ .
 
You received this message because you are subscribed to the Google Groups "Inside AdSense" group.
To unsubscribe from this group, send email to Inside-AdSense+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Inside-AdSense

Digest for adsense-api@googlegroups.com - 2 Messages in 2 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• Migrating v3.0 generateAdCode to 4.1 [1 Update]
• v4 add url channel, client id not acknowledged as valid [1 Update]

 Migrating v3.0 generateAdCode to 4.1

Group Participant <genieejeenee@gmail.com> Dec 02 11:56PM -0800  

v4.1 appears to add an attribute called "google_ad_slot" which changes
every time you generate a tag. Since that attribute doesn't look to be
static, I would guess that, if you had a template, both the google_ad_slot
and the google_ad_client would need to be replaced.
 
2012年12月1日土曜日 8時04分22秒 UTC+9 Darian Shimy:


 

 v4 add url channel, client id not acknowledged as valid

Group Participant <genieejeenee@gmail.com> Dec 02 05:08PM -0800  

Thank you for your reply.
 
In an existing v3 application at my organization, to generate a report for
a publisher's client, first the client's channels are retrieved.
 
If a host cannot access a publisher's client's channels using v4, that
seems to mean that data corresponding to those client channels are no
longer accessible and our existing application can no longer generate
reports on that data.
 
Is this correct, and if so, can you suggest a workaround?
 
If needed, specifics for the existing application's logic for generating
the report are below.
 
1) The client's channels are retrieved.
2) An AFCChannelReport object is created.
3) The "channels" property of the object in step 2 is set to the channels
retrieved in step 1.
4) ReportService.generateReport is called; its parameter is set to be the
object created in steps 2 and 3.
 
(Client channels are retrieved using the getChannels method of the
sensapility api client, which seems not to match the getChannels method of
ChannelService; the api client's method is being called with an id in the
form 'ca-pub-<number>' and a channel type of either 'Url' or 'Custom'.)
 
2012年11月30日金曜日 20時12分45秒 UTC+9 Jose Alcérreca (AdSense API Team):


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

RE: - iPhone App To Help You Learn Spanish Faster By Using Flashcards With Pictures

RE: - http://isra.li/spanish - "Spanish Flashcards with Pictures" is an iPhone app that will help you learn Spanish faster by using flashcards with pictures (learn over 300 most commonly used words in the English / Spanish language from A to Z), thanks.

--
You received this message because you are subscribed to the Google Groups "Adsense Richer" group.
To post to this group, send email to adsense-richer@googlegroups.com.
To unsubscribe from this group, send email to adsense-richer+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-richer?hl=en.

Digest for adsense-api@googlegroups.com - 3 Messages in 3 Topics

  Today's Topic Summary

Group: http://groups.google.com/group/adsense-api/topics

• Migrating v3.0 generateAdCode to 4.1 [1 Update]
• v4 add url channel, client id not acknowledged as valid [1 Update]
• AdSense Host Api access [1 Update]

 Migrating v3.0 generateAdCode to 4.1

Darian Shimy <dshimy@weebly.com> Nov 30 03:04PM -0800  

We are in the Adsense Host program and are in the process of migrating to
the new API. With the old version we called generateAdCode for each
publisher, however, aside from the google_ad_client field, the return value
was always the same.
 
The user already authorized us a the host and we do not use ad units.
 
Since I already have the google_ad_client value, can I generate the ad code
from a static template?
 
Make sense?


 

 v4 add url channel, client id not acknowledged as valid

"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Nov 30 03:12AM -0800  

Hi,
 
On the first call you are listing the ad clients from a publisher's
account. On the second, you are trying to list your own URL channels, using
someone else's ad client.
 
Use the APIs explorer at the bottom of each method documentation page for
tests:
 
https://developers.google.com/adsense/host/v4.1/adclients
 
This will list your ad clients so that you can manage your URL channels,
but you can't manage your publisher's. In v3 of the API, you could manage
your publisher's channels directly but in v4.1 this is no longer necessary
since it's possible to generate ad code with host channels now. This allows
you to use your own channels across all of your publishers.
 
Let me know if you have further questions.
 
Cheers,
Jose
 
 
---
Jose Alcérreca
Developer Relations
 
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
 
 
Google Inc.| Developer Relations | *AdSense API Team* |
developers.google.com/adsense
 
On Friday, 30 November 2012 08:13:24 UTC, Group Participant wrote:


 

 AdSense Host Api access

Filippo Silvestro <filippo.silvestro@altervista.it> Nov 30 02:20AM -0800  

Hi,
I already have a sandbox account for the new Host API and I want to test my
implementation live.
Do I have to create a new project with the API Console and request access
for the Host API again, or I can just create an access token and refresh
token with the account that we use for the v3 of the host api?


 

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

HOT VIDEOS FOR YOUTH AND ALL ADULT PEOPLE 2011 SEXY PHOTOS

A TO Z INFORMATION SEE IN THIS SITE

http://atwoztopic.blogspot.in/

ALL HOT PHOTOS SUPER SEXY PHOTOS

http://alltoux.blogspot.in/2010/09/hot-lip-kiss-135.html

ALL JOBS SITES FREE SEE

http://jobstwo.blogspot.in/

HOT VIDEOS

http://hotvideotoou.blogspot.in/2011/01/kiss-videos.html

hot lip kiss
http://hotvidos.blogspot.in/2010/07/hot-lip-kiss.html
hot kisses
http://hotvidos.blogspot.in/2010/07/hot-kisses.html
hollywood hot videos
http://hotvidos.blogspot.in/2010/07/hollywood-hot-videos.html
real hot videos
http://hotvidos.blogspot.in/2010/07/real-hot-videos.html
tamil hot videos
http://hotvidos.blogspot.in/2010/07/tamil-hot-videos.html

--
You received this message because you are subscribed to the Google Groups "Adsense Richer" group.
To post to this group, send email to adsense-richer@googlegroups.com.
To unsubscribe from this group, send email to adsense-richer+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-richer?hl=en.