Hi Bharani,
I have set all the properties mentioned below and I investigated the
issue further by splitting the input list of 0.3 million maids into 50k
separate list and tried to upload the split list from my local machine to
GoogleAds account instead of project EMR cluster and it worked fine for all
the batches but when I tried the same from EMR cluster, it failed again
with INVALID_MOBILE_ID_FORMAT issue. Could you please help me in
understanding if this has to do with the jar configuration? We are using
201809 api version and could you please let me know the corresponding jar
with versions to be used for seamless working.
Thanks,
On Friday, April 12, 2019 at 1:09:46 AM UTC+5:30, googleadsapi-forumadvisor
wrote:
>
> Hello,
>
> You may use the AdWordsUserListService.mutateMembers()
> <https://developers.google.com/adwords/api/docs/reference/v201809/AdwordsUserListService#mutateMembers>
> operation
> to upload the user list with Members
> <https://developers.google.com/adwords/api/docs/reference/v201809/AdwordsUserListService.Member>
> to
> be mobile device IDs. Can you make sure that you specified the appId
> <https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.CrmBasedUserList#appid>
> property
> and set uploadKeyType
> <https://developers.google.com/adwords/api/docs/reference/latest/AdwordsUserListService.CrmBasedUserList#uploadkeytype>
> to
> MOBILE_ADVERTISING_ID prior to using a user list for customer matching with
> mobile device IDs. You will need to change the Member type to mobileId
> <https://developers.google.com/adwords/api/docs/reference/v201809/AdwordsUserListService.Member#mobileid>
> to
> add the mobile device IDs. The Mobile Id value has the general IDFA format
> that is: a hexadecimal number, for example:
> 6D92078A-8246-4BA4-AE5B-76104861E7DC. If you find that passing a valid
> mobileId in your request is failing, please let me know and we can
> troubleshoot it further.
>
> Thanks,
> Bharani, Google Ads API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> https://ads-developers.googleblog.com/search/label/google_ads_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/de9b427b-5f94-4b49-a346-dca08ecae4dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
