Re: adding mobile image ad to a campaign; several questions
2nd and 3rd problems occured because the campaign was targeted to a
different country.
i'm now left only with the *size *problem:
the file is 8kb but reported as FILE_TOO_LARGE
On Sunday, October 19, 2014 10:08:40 PM UTC+3, Berry Tsakala wrote:
I found on the web only a single example of using *MobileImageAd *(duplicated
in several places).
The latest version of this example on the web seems to be from 2011 (e.g.
https://searchcode.com/codesearch/view/2598566/)
i'm trying to adapt it to version='v201402' (yes, i know it's deprecated
since last week, I assume the problems are the same)
Here's my current code:
image = {
'dimensions': [{
'key': 'FULL',
'value': {'width': width, 'height': height }
}],
'name': 'sample.jpg',
'data': base64.encodestring( Utils.ReadFile(image_file) )
}
operations = [{
'operator': 'ADD',
'operand': {
'xsi_type': 'AdGroupAd',
'adGroupId': adgroup_id,
'ad': {
'xsi_type': 'MobileImageAd',
'markupLanguages': ['HTML'], # why do I
need it anyway?
'mobileCarriers': ['T-Mobile@US', 'Verizon@US'],
'image': image,
'url': destination_url,
'displayUrl': display_url
}
}
}]
first problem:
ImageError.FILE_TOO_LARGE-- why? it's only 8k (attached).
2nd problem: carriers:
AdError.INVALID_MOBILE_CARRIER_TARGET @
operations[0].operand.ad.mobileCarriers
According to the docs, they should be accepted. This was also the syntax
for the 2011 api-version. Why not?
https://developers.google.com/adwords/api/docs/appendix/mobilecarriers
For now I ended up using ALLCARRIERS. But I'd like to target carriers,
too
3rd problem:
AdError.INVALID_AD_ADDRESS_CAMPAIGN_TARGET
(according to the docs it has nothing to do with url and display_url,
which i won't disclose here, but are perfectly valid URLs in my case)
I do not understand this error
https://developers.google.com/adwords/api/docs/reference/v201406/AdGroupAdService?hl=es
INVALID_AD_ADDRESS_CAMPAIGN_TARGETUser cannot create mobile ad for
countries targeted in specified campaign.
thank you
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0e475699-fc2c-4833-850a-ae25cef05836%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How link Google Analytics and Adwords with Different email address?
Hi, I have a Google Analytics Accounts with email adderess (eg:a...@gmail.com) and adwords account with email address(eg:x...@gmail.com). I want to setup link between those email addresses. I have tried to link but it showing There are no AdWords accounts associated with the Analytics login you're using. Make sure that you're using a Google Account (login or email address) that has Edit permission for the Analytics property and Administrative access for the AdWords account. Alternatively, create a new AdWords account. Is there is solution to link up? Help me out from this issue with best possible solutions.. Thanks Vijay -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/198a1f1d-146d-4a82-9232-363046c2f92b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: adding mobile image ad to a campaign; several questions
Hello Berry,
Please send us the full XML response with the error *over email* (Reply to
author button).
-Danial, AdWords API Team.
On Monday, October 20, 2014 2:00:17 PM UTC+4, Berry Tsakala wrote:
2nd and 3rd problems occured because the campaign was targeted to a
different country.
i'm now left only with the *size *problem:
the file is 8kb but reported as FILE_TOO_LARGE
On Sunday, October 19, 2014 10:08:40 PM UTC+3, Berry Tsakala wrote:
I found on the web only a single example of using *MobileImageAd
*(duplicated
in several places).
The latest version of this example on the web seems to be from 2011
(e.g. https://searchcode.com/codesearch/view/2598566/)
i'm trying to adapt it to version='v201402' (yes, i know it's
deprecated since last week, I assume the problems are the same)
Here's my current code:
image = {
'dimensions': [{
'key': 'FULL',
'value': {'width': width, 'height': height }
}],
'name': 'sample.jpg',
'data': base64.encodestring( Utils.ReadFile(image_file) )
}
operations = [{
'operator': 'ADD',
'operand': {
'xsi_type': 'AdGroupAd',
'adGroupId': adgroup_id,
'ad': {
'xsi_type': 'MobileImageAd',
'markupLanguages': ['HTML'], # why do I
need it anyway?
'mobileCarriers': ['T-Mobile@US', 'Verizon@US'],
'image': image,
'url': destination_url,
'displayUrl': display_url
}
}
}]
first problem:
ImageError.FILE_TOO_LARGE-- why? it's only 8k (attached).
2nd problem: carriers:
AdError.INVALID_MOBILE_CARRIER_TARGET @
operations[0].operand.ad.mobileCarriers
According to the docs, they should be accepted. This was also the syntax
for the 2011 api-version. Why not?
https://developers.google.com/adwords/api/docs/appendix/mobilecarriers
For now I ended up using ALLCARRIERS. But I'd like to target carriers,
too
3rd problem:
AdError.INVALID_AD_ADDRESS_CAMPAIGN_TARGET
(according to the docs it has nothing to do with url and display_url,
which i won't disclose here, but are perfectly valid URLs in my case)
I do not understand this error
https://developers.google.com/adwords/api/docs/reference/v201406/AdGroupAdService?hl=es
INVALID_AD_ADDRESS_CAMPAIGN_TARGETUser cannot create mobile ad for
countries targeted in specified campaign.
thank you
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/a17af706-8702-4386-9908-6ef3958ce431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: which api can i get the app list in Display Network?
Hi, The easiest way to get that list is by using either the Automatic Placements Performance Report https://developers.google.com/adwords/api/docs/appendix/reports#automatic-placements or the Placement Performance Report https://developers.google.com/adwords/api/docs/appendix/reports#placement. The Mapping Reports to the UI page https://developers.google.com/adwords/api/docs/guides/uireports#autoPlacementsReport explains the difference between those two reports. For both reports, the *DisplayName* field will return the description in your screenshot. Cheers, Josh, AdWords API Team On Sunday, October 19, 2014 10:39:52 PM UTC-4, sword wrote: For example.which api can i get the app list? https://lh5.googleusercontent.com/-M6q0kLJini0/VER0pq6Sh2I/AAk/G_g4_EzwwKQ/s1600/app.PNG -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/0c95ceb0-5289-4b31-9b6b-51d9ecf81c0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How link Google Analytics and Adwords with Different email address?
Hi Vijay, I'm not a Google Analytics expert, but my best guess is that you need to grant your Analytics account a...@gmail.com adminstrative access to your AdWords account x...@gmail.com. You can do this by logging into your AdWords account, clicking the settings (gear) icon, choosing *Account settings*, then *Account access*, then the big red *+USERS* button. In the dialog that appears you'll enter a...@gmail.com and choose *Administrative access* for the access level. Cheers, Josh, AdWords API Team On Monday, October 20, 2014 8:46:06 AM UTC-4, Vijay Reddy wrote: Hi, I have a Google Analytics Accounts with email adderess (eg:a...@gmail.com) and adwords account with email address(eg:x...@gmail.com). I want to setup link between those email addresses. I have tried to link but it showing There are no AdWords accounts associated with the Analytics login you're using. Make sure that you're using a Google Account (login or email address) that has Edit permission for the Analytics property and Administrative access for the AdWords account. Alternatively, create a new AdWords account. Is there is solution to link up? Help me out from this issue with best possible solutions.. Thanks Vijay -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/50c7078d-2318-482a-958c-7a1dcc49f804%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
DUPLICATE_ADGROUP_NAME when re-creating removed ad group
Hi, We are running into a problem with re-enabling removed ad groups. In the past both campaigns and ad groups could be re-enabled from REMOVED status by simply setting their status to ENABLED, this no longer works, as the removal seems to be permanent. Instead the API allows multiple campaigns with the same name to exist, as long as only one campaign is ENABLED or PAUSED and the rest are REMOVED. However, this does not seem to work for Ad Groups. After setting a Ad Group status to REMOVED the status can no longer be set to ENABLED, but no other Ad Group with the same name can be created either. In essence, we are now have a number of Ad Groups that are 'locked', they cannot be re-enabled, but they can't be renamed either (although the web interface can still do this.) We have worked around the issue by renaming ad groups prior to deleting them, but this is far from optimal. Is this a bug or is this working as intended? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/684b6791-88ad-4bcc-8cb5-5022ecc11625%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgraded Location extension visibility
Hello, Please see this help center article https://support.google.com/adwordspolicy/answer/144649?hl=en for more information on disapproval. Regards, Mike, AdWords API Team On Thursday, October 16, 2014 4:46:44 PM UTC-4, GDZ wrote: Wait a minute :) If say I have an account with just one campaign, if location extension is disapproved, why ads will not serve? Why not show ads without location extension? AdWords do not show location extensions every time anyway... Thank you, GDZ On Thursday, October 16, 2014 4:24:30 PM UTC-4, Michael Cloonan (AdWords API Team) wrote: Hello, If an extension is disapproved, all associated ads will not serve until the issue that caused the disapproval is resolved. It shouldn't just pick another extension to use in its place. Regards, Mike, AdWords API Team On Tuesday, October 14, 2014 3:45:22 PM UTC-4, GDZ wrote: Example: we created 2 upgraded feed-based account-level location extensions. My account has 2 campaigns. So via API we assigned extension 1 to campaign 1, extension 2 to campaign 2. Campaigns are active and running. But... say a bit later we discovered that extension 2 was not approved (say address was all wrong or whatever). What is going to happen to campaign 2? Will it show extension 1 (because it is account-wide)? No extension at all? Thank you! GDZ -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/be988d99-c06f-4116-b26c-2300cac01484%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Migration from clientLogin to oAuth2
Hi Josh,
Thanks for the reply. I have gone through the step by step instructions for
generating the refresh token.
I'm using the OAuthTokenGenerator.exe, entering my clientID and the client
secret after which I can see the consent screen.
Once I click the 'Accept' button, I see a screen showing RavenDB documents
which are empty. (Please see screen shot in my previous post).
Not sure if I am missing something or if the exe is not working as expected.
Thanks.
On Saturday, October 18, 2014 8:58:52 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:
Hi,
Sorry to hear this process has been frustrating for you. Have you looked
at the step-by-step instructions for OAuth2 on the .NET library's wiki
pages?
https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator
The *invalid_client* message you received in step 5 usually means that
the *client ID *or *client secret* are incorrect. If that's not the issue
and the step-by-step instructions don't help, please post a reply here.
Note that if you need to send any sensitive information along to me for
troubleshooting you can do so by clicking the *Reply to Author* option.
Thanks,
Josh, AdWords API Team
On Friday, October 17, 2014 3:55:23 PM UTC-4, Shruti wrote:
Hi,
I'm trying to migrate an application from using ClientLogin to oAuth2. I
have followed the instructions as given here -
https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc
and https://developers.google.com/adwords/api/docs/guides/authentication
As indicated, I have
1. created a new project in the developer console.
2. added credentials for installed application and generated the clientId
and client secret.
3. set up the consent form with email and the product name
4. used the client library utility to generate the authorization code
5. Copied the authorization code back to the client library utility to
exchange it for access token and the refresh token (which resulted in
invalid client)
6. So, I finally I used the oauth playground (note - I used the sandbox
scope) to get the access token and refresh token and used these in my
application config.
But still get the below error -
{Failed to refresh access token.\n{\n \error\ :
\unauthorized_client\\n}}
I find all this process just to obtain the authorization to access my
older adwords account too frustrating. Can you please help me identify if
I'm missing anything here?
Any urgent help will be appreciated.
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/9b5e536f-e7d5-48eb-be3f-6facc95940b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: DUPLICATE_ADGROUP_NAME when re-creating removed ad group
Hi, Starting with v201406 of the API, you can no longer edit *any* attributes of a removed Campaign or a removed AdGroup. You are correct that Campaigns allow duplicate names among REMOVED objects, but AdGroup names must be unique across all AdGroups in a Campaign, regardless of status. For the time being, the approach you are taking of renaming AdGroups on delete is the best option. Note that you *can* rename and remove an AdGroup in the same SET operation (it sounds like you are doing separate operations, but that's not actually necessary). I realize that this inconsistency is a bit of a pain, especially now that you cannot change the name of a removed AdGroup. I'll talk to the team about making the uniqueness rules for AdGroups the same as the rules for Campaigns. Cheers, Josh, AdWords API Team On Monday, October 20, 2014 10:15:25 AM UTC-4, t.k...@social-mining.com wrote: Hi, We are running into a problem with re-enabling removed ad groups. In the past both campaigns and ad groups could be re-enabled from REMOVED status by simply setting their status to ENABLED, this no longer works, as the removal seems to be permanent. Instead the API allows multiple campaigns with the same name to exist, as long as only one campaign is ENABLED or PAUSED and the rest are REMOVED. However, this does not seem to work for Ad Groups. After setting a Ad Group status to REMOVED the status can no longer be set to ENABLED, but no other Ad Group with the same name can be created either. In essence, we are now have a number of Ad Groups that are 'locked', they cannot be re-enabled, but they can't be renamed either (although the web interface can still do this.) We have worked around the issue by renaming ad groups prior to deleting them, but this is far from optimal. Is this a bug or is this working as intended? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/57c1962f-7a5a-413f-b543-0eb3026c2037%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Migration from clientLogin to oAuth2
Hi,
I see - I think the problem is that the project you created in the
Developers Console is a *Web application*, but OAuthTokenGenerator.exe
assumes you have a *Native application*. If you create a *Native
application* as described here
https://github.com/googleads/googleads-dotnet-lib/wiki/How-to-create-OAuth2-client-id-and-secret#1-native-application
and
use that application's client ID and client secret, then the generator
should work as expected.
As an aside, what's happening right now with your *Web application* is that
after you authorize, the OAuth server is redirecting you to your *Web
application*'s redirect URL. See the OAuth Web application flow
https://developers.google.com/accounts/docs/OAuth2#webserver for details.
Cheers,
Josh, AdWords API Team
On Monday, October 20, 2014 11:16:19 AM UTC-4, Shruti wrote:
Hi Josh,
Thanks for the reply. I have gone through the step by step instructions
for generating the refresh token.
I'm using the OAuthTokenGenerator.exe, entering my clientID and the client
secret after which I can see the consent screen.
Once I click the 'Accept' button, I see a screen showing RavenDB
documents which are empty. (Please see screen shot in my previous post).
Not sure if I am missing something or if the exe is not working as
expected.
Thanks.
On Saturday, October 18, 2014 8:58:52 AM UTC-4, Josh Radcliff (AdWords API
Team) wrote:
Hi,
Sorry to hear this process has been frustrating for you. Have you looked
at the step-by-step instructions for OAuth2 on the .NET library's wiki
pages?
https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator
The *invalid_client* message you received in step 5 usually means that
the *client ID *or *client secret* are incorrect. If that's not the
issue and the step-by-step instructions don't help, please post a reply
here. Note that if you need to send any sensitive information along to me
for troubleshooting you can do so by clicking the *Reply to Author*
option.
Thanks,
Josh, AdWords API Team
On Friday, October 17, 2014 3:55:23 PM UTC-4, Shruti wrote:
Hi,
I'm trying to migrate an application from using ClientLogin to oAuth2. I
have followed the instructions as given here -
https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc
and https://developers.google.com/adwords/api/docs/guides/authentication
As indicated, I have
1. created a new project in the developer console.
2. added credentials for installed application and generated the
clientId and client secret.
3. set up the consent form with email and the product name
4. used the client library utility to generate the authorization code
5. Copied the authorization code back to the client library utility to
exchange it for access token and the refresh token (which resulted in
invalid client)
6. So, I finally I used the oauth playground (note - I used the sandbox
scope) to get the access token and refresh token and used these in my
application config.
But still get the below error -
{Failed to refresh access token.\n{\n \error\ :
\unauthorized_client\\n}}
I find all this process just to obtain the authorization to access my
older adwords account too frustrating. Can you please help me identify if
I'm missing anything here?
Any urgent help will be appreciated.
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/be44db1d-f6e5-401b-94a8-b47c3fe4f165%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Migration from clientLogin to oAuth2
Hi,
I have created the client ID for the native application (same as installed
application, I believe).
I have been following the steps shown on -
https://www.youtube.com/watch?v=WifY2fFyaMw for the native application.
Thanks
On Monday, October 20, 2014 12:50:08 PM UTC-4, Josh Radcliff (AdWords API
Team) wrote:
Hi,
I see - I think the problem is that the project you created in the
Developers Console is a *Web application*, but OAuthTokenGenerator.exe
assumes you have a *Native application*. If you create a *Native
application* as described here
https://github.com/googleads/googleads-dotnet-lib/wiki/How-to-create-OAuth2-client-id-and-secret#1-native-application
and
use that application's client ID and client secret, then the generator
should work as expected.
As an aside, what's happening right now with your *Web application* is
that after you authorize, the OAuth server is redirecting you to your *Web
application*'s redirect URL. See the OAuth Web application flow
https://developers.google.com/accounts/docs/OAuth2#webserver for
details.
Cheers,
Josh, AdWords API Team
On Monday, October 20, 2014 11:16:19 AM UTC-4, Shruti wrote:
Hi Josh,
Thanks for the reply. I have gone through the step by step instructions
for generating the refresh token.
I'm using the OAuthTokenGenerator.exe, entering my clientID and the
client secret after which I can see the consent screen.
Once I click the 'Accept' button, I see a screen showing RavenDB
documents which are empty. (Please see screen shot in my previous post).
Not sure if I am missing something or if the exe is not working as
expected.
Thanks.
On Saturday, October 18, 2014 8:58:52 AM UTC-4, Josh Radcliff (AdWords
API Team) wrote:
Hi,
Sorry to hear this process has been frustrating for you. Have you looked
at the step-by-step instructions for OAuth2 on the .NET library's wiki
pages?
https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator
The *invalid_client* message you received in step 5 usually means that
the *client ID *or *client secret* are incorrect. If that's not the
issue and the step-by-step instructions don't help, please post a reply
here. Note that if you need to send any sensitive information along to me
for troubleshooting you can do so by clicking the *Reply to Author*
option.
Thanks,
Josh, AdWords API Team
On Friday, October 17, 2014 3:55:23 PM UTC-4, Shruti wrote:
Hi,
I'm trying to migrate an application from using ClientLogin to oAuth2.
I have followed the instructions as given here -
https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc
and
https://developers.google.com/adwords/api/docs/guides/authentication
As indicated, I have
1. created a new project in the developer console.
2. added credentials for installed application and generated the
clientId and client secret.
3. set up the consent form with email and the product name
4. used the client library utility to generate the authorization code
5. Copied the authorization code back to the client library utility to
exchange it for access token and the refresh token (which resulted in
invalid client)
6. So, I finally I used the oauth playground (note - I used the sandbox
scope) to get the access token and refresh token and used these in my
application config.
But still get the below error -
{Failed to refresh access token.\n{\n \error\ :
\unauthorized_client\\n}}
I find all this process just to obtain the authorization to access my
older adwords account too frustrating. Can you please help me identify if
I'm missing anything here?
Any urgent help will be appreciated.
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/fe5bb8a2-6e63-4b0e-9e75-b9b8ce9bcb6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Migration from clientLogin to oAuth2
Hi,
Could you send a screenshot of your application setup from the Developers
Console *only to me* by clicking *Reply to Author*?
Thanks,
Josh, AdWords API Team
On Monday, October 20, 2014 1:09:09 PM UTC-4, Shruti wrote:
Hi,
I have created the client ID for the native application (same as installed
application, I believe).
I have been following the steps shown on -
https://www.youtube.com/watch?v=WifY2fFyaMw for the native application.
Thanks
On Monday, October 20, 2014 12:50:08 PM UTC-4, Josh Radcliff (AdWords API
Team) wrote:
Hi,
I see - I think the problem is that the project you created in the
Developers Console is a *Web application*, but OAuthTokenGenerator.exe
assumes you have a *Native application*. If you create a *Native
application* as described here
https://github.com/googleads/googleads-dotnet-lib/wiki/How-to-create-OAuth2-client-id-and-secret#1-native-application
and
use that application's client ID and client secret, then the generator
should work as expected.
As an aside, what's happening right now with your *Web application* is
that after you authorize, the OAuth server is redirecting you to your *Web
application*'s redirect URL. See the OAuth Web application flow
https://developers.google.com/accounts/docs/OAuth2#webserver for
details.
Cheers,
Josh, AdWords API Team
On Monday, October 20, 2014 11:16:19 AM UTC-4, Shruti wrote:
Hi Josh,
Thanks for the reply. I have gone through the step by step instructions
for generating the refresh token.
I'm using the OAuthTokenGenerator.exe, entering my clientID and the
client secret after which I can see the consent screen.
Once I click the 'Accept' button, I see a screen showing RavenDB
documents which are empty. (Please see screen shot in my previous post).
Not sure if I am missing something or if the exe is not working as
expected.
Thanks.
On Saturday, October 18, 2014 8:58:52 AM UTC-4, Josh Radcliff (AdWords
API Team) wrote:
Hi,
Sorry to hear this process has been frustrating for you. Have you
looked at the step-by-step instructions for OAuth2 on the .NET library's
wiki pages?
https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator
The *invalid_client* message you received in step 5 usually means that
the *client ID *or *client secret* are incorrect. If that's not the
issue and the step-by-step instructions don't help, please post a reply
here. Note that if you need to send any sensitive information along to me
for troubleshooting you can do so by clicking the *Reply to Author*
option.
Thanks,
Josh, AdWords API Team
On Friday, October 17, 2014 3:55:23 PM UTC-4, Shruti wrote:
Hi,
I'm trying to migrate an application from using ClientLogin to oAuth2.
I have followed the instructions as given here -
https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc
and
https://developers.google.com/adwords/api/docs/guides/authentication
As indicated, I have
1. created a new project in the developer console.
2. added credentials for installed application and generated the
clientId and client secret.
3. set up the consent form with email and the product name
4. used the client library utility to generate the authorization code
5. Copied the authorization code back to the client library utility to
exchange it for access token and the refresh token (which resulted in
invalid client)
6. So, I finally I used the oauth playground (note - I used the
sandbox scope) to get the access token and refresh token and used these
in
my application config.
But still get the below error -
{Failed to refresh access token.\n{\n \error\ :
\unauthorized_client\\n}}
I find all this process just to obtain the authorization to access my
older adwords account too frustrating. Can you please help me identify if
I'm missing anything here?
Any urgent help will be appreciated.
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
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi, Anash. I switched over to the new v201409 API that was just recently released, using the latest Java API library. It still doesn't work. It now gives a reasonable exception, rather than just the generic fault occurred while processing error. However, you had said on Sep 24 that the fix that should be going live was that we'd be able to set these bid modifiers on ad groups in shopping campaigns now (as can be done in the UI for shopping campaigns and could be done in the API for the old PLA campaigns)? An example request from today: ?xml version=1.0 encoding=UTF-8?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header ns1:RequestHeader xmlns:ns1=https://adwords.google.com/api/adwords/cm/v201409; soapenv:mustUnderstand=0 ns1:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201409; operations operatorADD/operator operand adGroupId19190905510/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905390/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905270/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905150/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905030/adGroupId criterion id30001/id /criterion bidModifier1.25/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 10-20-14 15:48:08,472 [main] WARN soapXmlLogger - SOAP Response: ?xml version=1.0 encoding=UTF-8?soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Header ResponseHeader xmlns=https://adwords.google.com/api/adwords/cm/v201409; requestId000505e0d4e0e1500ab68045b8004eee/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime61/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[4].operand.criterion; trigger:'SHOPPING']/faultstring detail ApiExceptionFault xmlns=https://adwords.google.com/api/adwords/cm/v201409; message[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @
Re: OPERATION_NOT_PERMITTED_FOR_REMOVED_ENTITY Bug?
Hi Anash, Can you find out if the unique constraint is still going to be enforced going forward for removed items? If AdWords is no longer going to allow you to unremove an item, it seems strange that removed items would still be part of the uniqueness check. As we've described in this thread, it presents problems for API users, but I would also see it creating problems for UI users as well. The user would try to create a new Ad Group, the UI would tell them they can't because the name is already used - but when the user goes to look for it they can't find it, or they think to look at the removed Ad Groups and find it there, only to find they can't change it. Thanks, Eric On Tue, Oct 14, 2014 at 3:54 PM, Anash P. Oommen (AdWords API Team) adwordsapiadvisor+an...@google.com wrote: Hi David, The team got back to me telling that this change is not feasible, so you need to rename and then delete if you need to maintain unique name. Cheers, Anash On Friday, October 10, 2014 6:23:34 AM UTC-4, David Midgley wrote: Hi Anash/API Team Now that v201409 is released the countdown has started on the sunsetting of v201402 which basically means we need a workaround to this problem soon as v201402 is the only live version that allows the renaming of deleted adgroups! Anash, you mentioned: I've asked the team to investigate whether it is feasible to allow deleted adgroups and campaigns to be renamed. I'll update the thread as I hear from them Have you heard from the team? Cheers David On Thursday, 18 September 2014 14:51:46 UTC+1, Anash P. Oommen (AdWords API Team) wrote: Hi Mariusz, I've asked the team to investigate whether it is feasible to allow deleted adgroups and campaigns to be renamed. I'll update the thread as I hear from them, Cheers, Anash On Thursday, September 18, 2014 5:43:41 AM UTC-4, Mariusz wrote: One more thing to bear in mind is that you probably should version deleted adgroups. Imagine: - user creates adgroup “test” - then deletes it, so the system first renames it to “test_del” and then marks as deleted - user creates again adgroup named “test” - user tries to delete it The system will fail in step 4, because it will try to rename adgroup to “test_del”, but that name already exists. So what you may do in that case is to detect the error, and try to rename it to “test_del1”. Cheers, Mariusz On Thursday, 18 September 2014 08:24:33 UTC+1, Oliver wrote: Just thinking loud here, if the adgroups are deleted via your software, what if you rename the adgroup *before *you delete it? We used to use a similar approach where we appended the text _del to all adgroup names that are about to be deleted. Obviously, if the adgroup is deleted via the adwords interface rather than your software, then the above won't help. Oliver On Wednesday, September 17, 2014 2:33:22 PM UTC+1, David Midgley wrote: Hi Anash/API Team I responded to your question. Is there anything else you need to know? It would be great to get an answer on this please! Cheers David On Monday, 15 September 2014 16:04:31 UTC+1, Anash P. Oommen (AdWords API Team) wrote: Hi David, If I remember correctly, the name needs to be unique in only active + paused items, not globally (with the new change). So if the user deletes an adgroup with the same name, you could create one with the same name again. Let me know if you are seeing a different behaviour, and I'll ask the team to investigate this further. Cheers, Anash P. Oommen, AdWords API Advisor. On Monday, September 8, 2014 2:29:07 PM UTC-4, David Midgley wrote: Thanks for the quick response Anash! Let me explain my use case and maybe you can find a workaround? We are working on an optimisation application that uses a strict naming convention for campaign and adgroup names. If a user accidentally deletes an adgroup, my software can't correct the error by recreating the adgroup because if we create a new adgroup with the same name in the same campaign we'll get a duplicate adgroup name error. Our solution to this problem was to rename the deleted adgroup which enabled us to create the new adgroup. Now that we can't rename the deleted adgroup and we can't create a new adgroup with the same name, how can we enforce our strict naming convention? This naming convention links adgroups between campaigns and is critical to our operations. We could version adgroup names, but this seems pretty untidy. We could use labels, but this could create thousands of labels and more (potentially error-prone) manual work. Can you think of a workaround? Cheers David On Monday, 8 September 2014 19:15:49 UTC+1, Anash P. Oommen (AdWords API Team) wrote: Hi David, AdWords API v201406 no longer allows you to undelete campaigns, adgroups, etc. The UI and older API versions allows this behaviour for now, but they will eventually start working like the way
