Re: How to add a user to existing Google Ads account
Thank you for the clarification. We don't have access to the interface in
most cases and want to invite a user for an existing account. Ah well
Do you get complaints on the new API? The API is so complicated and
difficult to use.
I've been developing for AdWords API sinds 2012/13 and that API was a
nightmare compared to any other REST API I've worked with, but Google API
is the next level.
Simple operations require large coding efforts with building complicated
objects. Why not use simple JSON structure for operations/mutations. Easy
to read, easy to construct.
Are there any plans or ways to construct the operations programmatically
and without the need to large code chunk to fill out the objects. What I
mean is that pushing dicts (in Python) is so much easier, because you can
construct them very easily and clearly. I mean getting statusses like
`google_ads_client.get_type('MerchantCenterLinkStatusEnum').ENABLED` makes
coding operations messy. Having string 'enabled' would make everything so
much easier
On Wed, May 27, 2020 at 3:47 PM Google Ads API Forum Advisor Prod <
adsapiforumadvi...@gmail.com> wrote:
> Hi Dennis,
>
> That's alright! Sometimes users may come here to ask questions about the
> UI so I wanted to make sure. As for your concern, unfortunately you cannot
> list the users for an account nor add a new user to an account via the API.
> Currently, this can only be done in the UI by logging into the Google Ads
> Account, and then checking “Tools and Settings” > “Setup” > “Account
> Access” and the list of users should be available in which you can add or
> remove users. I'll add a request for this feature to be included. In the
> meantime, please follow our blog
> on
> this request and if/when it will be included. Let me know if you have
> further questions.
>
> Thank you,
> Bryan, Google Ads API Team
>
>
> ref:_00D1U1174p._5004Q1zrvLQ:ref
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/CAJZiTBV9W3bKsB5%3DcpCfqOFJKi4cT4a%3DfZbUvxM8ViBU6cN-7w%40mail.gmail.com.
Re: How to find out what changes were made in the past 90 days
I see! Thanks for clearing it up. Is there a way to see the history of objects? Of at least the number of changes an object had in the last X days? On Monday, September 22, 2014 5:02:05 PM UTC+2, Anash P. Oommen (AdWords API Team) wrote: Hi, CustomerSyncService is not meant to be used as a change history tracker; it is more meant to let you know what objects to sync when syncing between your local server and the AdWords server. If you get TOO_MANY_CHANGES error, you should either reduce the time period to see if you can get a valid response. If this doesn't work, then you should resync the whole object. Cheers, Anash P. Oommen, AdWords API Advisor. On Sunday, September 21, 2014 3:56:54 PM UTC-4, ddofborg wrote: I'm trying to use CustomerSyncService https://developers.google.com/adwords/api/docs/reference/v201406/CustomerSyncService to find out what was changes in the past 90 days. I don't get it to work, because I aways get [CustomerSyncError.TOO_MANY_CHANGES @ selector]. I mean even one hour on a small campaign. What should I do? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups AdWords API Forum group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/a23468e7-253d-4028-bb53-ea48c10cbc8a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Accessing Shared[*]Services AdWords API services given access denied error.
We have some trouble accessing Shared[*]Services to download all shared negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED errors on get-request. Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups AdWords API Forum group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/e8c70e94-579f-4f4d-af1b-c41e826fac8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Accessing Shared[*]Services AdWords API services given access denied error.
I see! Is there another way to download shared negative keywords? Using adhoc or something else? On Friday, August 29, 2014 3:19:12 PM UTC+2, Josh Radcliff (AdWords API Team) wrote: Hi, Shared set services are only available to existing whitelisted customers https://developers.google.com/adwords/api/docs/guides/shared-sets. Cheers, Josh, AdWords API Team On Friday, August 29, 2014 5:17:35 AM UTC-4, ddofborg wrote: We have some trouble accessing Shared[*]Services to download all shared negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED errors on get-request. Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups AdWords API Forum group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/8cc78caa-3d9d-4a0e-a9ec-1bebf912c352%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Accessing Shared[*]Services AdWords API services given access denied error.
I see. Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups AdWords API Forum group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/5c40f92c-a0e2-4546-8f59-a303f82d78c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Strange SelectorError.START_INDEX_IS_TOO_HIGH
Is there a way to limit the size of the AdHoc report? I'd like to download is in parts and not as a whole. On Sunday, September 8, 2013 11:44:08 AM UTC+2, Takeshi Hagikura (AdWords API Team) wrote: To follow up on this, As mentioned in the blog post, the recommended way to retrieve large set of result is - narrow the query as much as possible with predicates or - Use Adhoc reports If there is any fields missing in adhoc reports, we're going to make it available in adhoc reports. (e.g. ad params) Before it's available in adhoc reports, please use predicates to narrow down results. Best, - Takeshi, AdWords API Team On Sunday, September 8, 2013 2:06:11 PM UTC+9, Takeshi Hagikura wrote: Hi Dorian, This was an expected behavior. In the first place, AdWords API does not allow you to retrieve data whose start index is past 5 (the maximum number increased to 100 though). Please see http://googleadsdeveloper.blogspot.jp/2012/02/adwords-api-retrieving-large-result.html. So if the size of the result is large, please use adhoc reports or try to narrow the query with predicates. Best, - Takeshi, AdWords API Team On Friday, September 6, 2013 3:50:11 AM UTC+9, Dorian Kind wrote: Hi Takeshi, thanks for your answer, however I am not sure I understand your suggestion. Removing paging.startIndex works fine, but how are we then supposed to fetch results beyond the maximum value of paging.numberResults? In my test, I received a SizeLimitError.RESPONSE_SIZE_LIMIT_EXCEEDED error when raising numberResults beyond approximately 10'000. Cheers, Dorian On Thursday, September 5, 2013 8:42:19 PM UTC+2, Takeshi Hagikura (AdWords API Team) wrote: Hi everyone, Thanks for sharing requestIds. Looks like the limit for paging.startIndex was changed. Can you please try removing startIndex to see if it works as a workaround? Best, - Takeshi, On Thursday, September 5, 2013 12:20:05 PM UTC+9, mm wrote: FWIW, we are also seeing this error - can supply additional Request ID's if that is useful Thanks - mm On Tuesday, September 3, 2013 9:35:16 AM UTC-5, fr...@bgenius.comwrote: Hi Takeshi, We also seem to be experiencing this issue. We have a client account that, according to the AdParamPage objects we get from the adparamservice, contains 402856 ad params. After succesfully retrieving a number of pages we get: [SelectorError.START_INDEX_IS_TOO_HIGH @ ; trigger:'19'] Request ID: 0004e57b8f9aa3680ae5500a660d Thank you for looking into this matter. Kind regards, Jaap-Jan Frans bGenius 0004e57b6dc1b4c00ae599cb65dd For example we have an account that has 402856 ad params, and we get the start index too high message when we reach start index Example request ID: Op maandag 2 september 2013 14:39:59 UTC+2 schreef Takeshi Hagikura (AdWords API Team): Hi Dorlan, Thanks for the report. Could you please tell us the example requestId (It's included in the soap response)? I'll look into that. Best, - Takeshi, AdWords API Team On Monday, September 2, 2013 4:46:57 PM UTC+9, Dorian Kind wrote: Hello, as this issue is affecting us quite heavily, I'm bumping this thread. If any request IDs or SOAP logs would be of help, I'll gladly provide them. Many thanks and best regards, Dorian On Thursday, August 29, 2013 5:30:06 PM UTC+2, Dorian Kind wrote: Hi all, since yesterday, we started to see SelectorError.START_INDEX_IS_TOO_HIGH errors when fetching all AdParams for a given campaign, even though there are more AdParams existing. These errors usually start appearing at an offset of around 12. The campaign in question currently has 148124 AdParams set as indicated by the totalNumEntries of the returned pages that are working; entries beyond a specifc offset however just throw a START_INDEX_IS_TOO_HIGH error. I'd be grateful for any hints as we have currently no way at all to retrieve a complete list of AdParams for that specific campaign. Best regards, Dorian -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups AdWords API Forum group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
