Yep. That was it. All I had to do was setClientCustomerId on the
AdWordsSession.
I'm back in business again!
Thanks Josh.
On Monday, March 31, 2014 1:59:06 PM UTC-7, Josh Radcliff (AdWords API
Team) wrote:
> Hi,
>
> From the behavior you are describing it sounds like you are passing an MC
On Monday, March 31, 2014 11:06:23 AM UTC-7, New Day Consulting wrote:
>
> I am a java developer transitioning to AdWords API v201402 from v201306.
>
> I have generated an oAuth2Credential via the OfflineCredentialsBuilder()
> as suggested as a replacement for getting oAuth2 authorization via a
Hi,
>From the behavior you are describing it sounds like you are passing an MCC
customer ID in the *clientCustomerId* header. For the CampaignService
you'll want to specify a regular AdWords customer ID by either updating
your ads.properties file or calling setClientCustomerId on your
AdWords
I am a java developer transitioning to AdWords API v201402 from v201306.
I have generated an oAuth2Credential via the OfflineCredentialsBuilder() as
suggested as a replacement for getting oAuth2 authorization via a private
key file (a *.p12" file)
and an email and password in an ads.properties f
