AdWords : Feed Service API error

[gurpreet....@gmail.com]

Hi,

 

Since last 2 days we have been getting “AuthenticationError. OAUTH_TOKEN_INVALID” error while calling feed service to create customer feeds for GMB location for all the accounts. We use GMB only to create location extensions in AdWords.

 

Attached is the request and response for a sample account.

 

Error details:

<faultstring>[AuthenticationError.OAUTH_TOKEN_INVALID @ operations[0].operand.systemFeedGenerationData.oAuthInfo; trigger:'https://www.googleapis.com/auth/plus.business.manage']</faultstring>

<trigger>https://www.googleapis.com/auth/plus.business.manage</trigger>

               <errorString>AuthenticationError.OAUTH_TOKEN_INVALID</errorString>

               <ApiError.Type>AuthenticationError</ApiError.Type>

               <reason>OAUTH_TOKEN_INVALID</reason>

 

Also there were no changes (api/property) made at our end since last 2-3 days which can lead to this error.Feed service creation was working fine a few days ago for the same soap request and response.

 

Other Details:

 

We use centralized/common GMB business account for multiple AdWords accounts, so the GMB account uses different sign-in email address from the one used for our AdWords account(s).

 

Request:

<operand>

                    <name>GMBLocationExtension</name>

                    <origin>ADWORDS</origin>

                    <systemFeedGenerationData xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201708" xsi:type="ns2:PlacesLocationFeedData">

                        <ns2:oAuthInfo>

                            <ns2:httpMethod>GET</ns2:httpMethod>

                            <ns2:httpRequestUrl>https://www.googleapis.com/auth/plus.business.manage</ns2:httpRequestUrl>

                            <ns2:httpAuthorizationHeader>GMB API user access token</ns2:httpAuthorizationHeader>

                        </ns2:oAuthInfo>

                        <ns2:emailAddress>aml.gmb...@gmail.com</ns2:emailAddress>

                        <ns2:labelFilters>4177937093</ns2:labelFilters>

                    </systemFeedGenerationData>

                </operand>

 

GMB refresh/access token is generated with scope (only GMB): https://www.googleapis.com/auth/plus.business.manage

Adwords refresh/access token is generated with scope (adwords and GMB): https://adwords.google.com/api/adwords  https://www.googleapis.com/auth/plus.business.manage

 

Also other adwords api services like campaign creation, budget updates etc using same adwords access token is created successfully and GMB location are created successfully in GMB account using GMB access token.

 

Any insight to why this is happening and how to resolve this would be great.

 

Thanks

Gurpreet Singh

[Vincent Racaza (AdWords API Team)]

Hi Gurpreet,

As you can see in this blog post, you will now need to use the AdWords API scope (https://www.googleapis.com/auth/adwords) in your OAuthInfo's httpRequestUrl field when creating location extension feeds. Kindly do this suggestion and let me know how it goes. If the issue still persists after doing the suggestion, kindly provide the SOAP request and response logs via Reply privately to author option so I can further check it. 

Thanks,

Vincent

AdWords API Team

[gurpreet....@gmail.com]

Hi Vincent,

Thanks for the info. Currently we use common GMB account for multiple adwords accounts having different email ids. So we were following step 4 in "use location extensions".

According to your suggestion (blog post link) below, it looks like we should now pass the adwords scope and adwords api email id in feed service oAuthInfo object. As I mentioned earlier, we have different adwords email id for each adwords api user and different email id for GMB. If we follow your suggestion we will have to add each adwords api user to GMB as manager and also set adwords api user mail id which is extra work of keeping mail ids of all adwords api user.

Currently we had created just one GMB manager user in GMB and its mail id,GMB scope and GMB Oauth was enough to create customer feeds in adwords by passing these info in oAuthInfo and email.

As below blog post suggest that the GMB scope is sunsetting and so we cannot use the our current approach, Is there any better way of handling our use case where we have multiple adwords api users using same GMB account ??  Any info on handling this scenario would be great.

Thanks,

Gurpreet

[Vincent Racaza (AdWords API Team)]

Hi Gurpreet,

Can you confirm if these multiple AdWords accounts are under one parent MCC? If they are under one parent MCC, you can just use the access token from a user/email address of the manager account. You don't need to create multiple AdWords user/email addresses in order to use its access token in the httpAuthorizationHeader field.

However, if these AdWords accounts are from different parent MCCs, then I am afraid that you need to use different email addresses that has access to the client account (has access to the AdWords API scope, and not to the GMB API).