know the clientCustomerId and can
proceed with the IS right away.
-Danial, AdWords API Team.
Original Message Follows:
From: "Amlan(BlueKai)"
Subject: Re: InfoService v201109 error
Date: Fri, 25 May 2012 00:13:51 -0700 (PDT)
> Eric,
>I have the ex
Eric,
I have the exact same problem as Denis.
We have used the InfoService call in a generic way to get the customer ids
for both unlinked and MCC accounts and the right thing happened (one
customerId or a set of 'sub' customerIds returned). But now I have noticed
that for a new MCC account
Hi Denis,
I believe the results should be the same regardless of whether or not the
account is a Google Apps for your domain account. If you just want to get
information about your sub-accounts then you should use the
ServicedAccountService instead.
Best,
- Eric
On Friday, March 30, 2012 3:5
Hi, Eric
thanks a lot for your reply.
This works for me. but for some of accounts i got zero values (ga accout
used is Google for domains account, non-MCC) the response is
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201109"
Hi Chris,
The content of the 500 response will give you more information about what
went wrong.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~
Hi Eric,
Scanning back through the forum, I found this posting you had made:
"That was my mistake, I described the solution incorrectly. The SoapHeader
element should be in the service's namespace, but it's contents should be
in the cm namespace."
So following that guidance, I tried:
Hi Chris,
It looks like you have some namespace issues. The RequestHeader element
should be in the cm namespace, not mcm.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/gro
It's working great now. Thank you!
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you a
Hi Eric,
I'm getting an HTTP 500 error when I do this. Here's the SOAP message I
tried using:
XX
XXX
true
UNIT_COUNT_FOR_CLIENTS
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
Hi All,
We pushed out a change today that should allow you to retrieve the customer
ID of unlinked accounts from the InfoService. If you call the
InfoService using the ApiUsageType of UNIT_COUNT_FOR_CLIENTS while
authenticated as the unlinked non-MCC account, you should receive back a
single
Hi All,
We are working on creating a solution before the sunset and hope to have
more information soon.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~
Is it fair to assume that there will be no solution before the sunset? If
so, will parts of the previous api still be available until there is a
suitable replacement in the current or future versions like previous
releases?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on ou
O.k. I will,
Thanks again for the help
On Jan 31, 11:56 pm, Eric Koleda wrote:
> Hi,
>
> We are currently working on a solution that will allow the fetching of data
> for unlinked accounts. Please watch the blog for an announcement.
>
> Best,
> - Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
Hi,
We are currently working on a solution that will allow the fetching of data
for unlinked accounts. Please watch the blog for an announcement.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http
Hey Eric,
Thanks for the reply,
But what about unlinked accounts?
how can I get their currency code and account name when the
accountService from V13 will sunset?
Thanks.
On Jan 30, 8:50 pm, Eric Koleda wrote:
> Hi Roee,
>
> The ServicedAccountService only works on accounts that are linked to
Hi Roee,
The ServicedAccountService only works on accounts that are linked to an MCC
account. Unlinked accounts will not be returned by that service.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
Hey,
It may be related bug, but I obtain the CustomerId from my client then
use it to create AuthToken.
but when using it in the ServicedAccountService I'm getting an empty
account in return.
Is there a limitation on ServicedAccountService compering to the old
AccountService in terms of which acco
Hi,
There are no updates regarding this gap in our offering. At this time our
recommendation remains to obtain the customer ID from the customer.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http
Hello,
I'm also affected by this bug - are there any updates regarding a
possible fix? Is Google's advice still to ask the customer for their
customerId?
Thanks in advance for any info,
S
On Dec 20 2011, 4:13 pm, Eric Koleda wrote:
> Hi Yagmur,
>
> Unfortunately I don't have any updates at this
It seems report downloading using the client email header has now been
disabled. As a result, apps are broken and people who've paid for them
can't use them anymore. You weren't willing to postpone the email
header deprecation, even though you currently offer us no way of getting
the apps to wo
Hi Yagmur,
Unfortunately I don't have any updates at this time. Do keep in mind that
the clientCustomerId header is usually not required, if you authenticate
directly against the target account. The only exception is report
downloading, which currently does enforce that the clientCustomerId i
Hi Eric,
I was wondering if there is an update on this bug? Not being able to
get the customer id for an unlinked account, which I guess is major
portion of all accounts, is a major problem.
Thanks for your attention,
Yagmur
On Dec 2, 2:04 pm, Eric Koleda wrote:
> Hi Yagmur,
>
> That's a good s
Hi Yagmur,
That's a good suggestion, and something we will keep in mind.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Hi Eric,
Can you guys do a blog post on this when you have the fix for it? I am sure
a lot of people would be interested in hearing about it when the fix is in
as well.
Thanks,
Yagmur
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adw
Hi,
We are aware that there is a gap in our offering when it comes to obtaining
the customer IDs of unlinked accounts, and we are working on ways to
address that. Asking the user for the CID is the only workaround at the
moment, but we recognize it's not ideal. That said, API version sunsets
Can't you reconsider the sunset? It's really a pain to develop for
this API with issues like this not thought out in advance. It's only a
few months since you recommended me to use the client email header, I
put time into changing my app to do this, people bought the tool based
on this, and now you
Hi,
At this time there are no plans to postpone the sunsets. I would recommend
you to change your application so that it gets the customer ID from the
user.
Best,
- Eric
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogs
Ok, thanks for confirming this. Would it thus be possible to postpone
the deprecation of the client email header until there is a solution
to this? Otherwise many of my clients won't be able to anymore use my
tool, for which they've paid. I'm sure other developers will face
similar problems as well
Hi MT,
You are correct that it's currently not possible to obtain the Customer ID
for an unlinked account, since as you mentioned neither the
ServicedAccountService nor InfoService provide that information. Currently
the only workaround is to ask the customer to also provide their customer
ID
Ok, but what about the situation when the authenticated account is not
an MCC, and in the selector, the client email of the authenticated non-
MCC account is passed? Seems the service does not work in these cases.
This is a problem because we need some way of obtaining the account ID
of a non-MCC l
I am following the threads in this forum to figure out how to add a
campaign in a sandbox environment v201109, but haven't had a luck of
succeeding. And that seems impossible to me now if I start in scratch. Here
is what I found so far in sandbox v201109:
1. In order to add a campaign (running
Hi MT,
That information is not outdated, and you can use an arbitrary MCC account.
However, the clientEmail you provide in the selector must exist somewhere
under the authenticated MCC or you will receive that error.
Best,
- Eric Koleda, AdWords API Team
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Thanks. The request now goes through, but when using it on my non-MCC
account to get the ID for the email, I get this error:
http://schemas.xmlsoap.org/soap/envelope/";>
https://adwords.google.com/api/
adwords/cm/v201109" xmlns="https://adwords.google.com/api/adwords/info/
v201109">
Hello MT,
I just checked the 'get_client_customer_id.rb' example and it works
perfectly for me. The XML code you are provided does not look like
library-generated code though. Are you using our client libraries or
generate the XML yourself?
The problem with your code is that the XML items nee
Thanks, but that doesn't solve the issue. Could you please post an XML
example of a successful request? I think there may be some issue with
the namespaces.
On Nov 22, 6:51 pm, Eric Koleda wrote:
> Hi,
>
> In v201109 we enabled XML validation for all of our SOAP requests in
> production (it was a
Hi,
In v201109 we enabled XML validation for all of our SOAP requests in
production (it was already enabled in the sandbox). The XML schema
included in the WSDL uses a sequence element to wrap these fields, which
requires that the order of the fields in the request must match the order
define
I'm trying to fetch a customer ID for an email (based on this example:
http://code.google.com/p/google-api-ads-ruby/source/browse/adwords_api/examples/v201109/get_client_customer_id.rb),
my request is:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instanc
37 matches
Mail list logo
