Hi,

I would like to confirm from my end if the workaround you tried is indeed
correct. For me to further check, could you provide the complete report
definition you used to generate the Automatic Placement Report as well as
your clientCustomerId so I could check those mobile app IDs with the team?
You may reply via *Reply privately to author*.

Regards,
Luis
AdWords API Team


=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
    http://googleadsdeveloper.blogspot.com/search/label/adwords_api
    https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 01/19/19 04:16:35 ppcdevelo...@mineeds.com wrote:

I found a workaround :
if you submit them with a prefix of 1- (for iOS) and 2- (for Android) then
the API call returns successfully.

AdWords returns this:
mobileapp::10002-ca-app-pub-3605354403339561

 and if you call AdWords back with the same app ID like below to either
target or exclude this particular app, you'll get invalid app ID error.
mobileapp::10002-ca-app-pub-3605354403339561

But...if you append the platform id like below it works:
mobileapp::2-10002-ca-app-pub-3605354403339561

So in my code, I have a special case handling for mobileapp IDs that start
with 10002 or 10001, then replace it with 2-10002 and for 10001, replace it
with 1-10001.

Automatic Placement reports also return app ID's with 3-<appd ID> where 3-
identifies Windows mobile apps. However, I found that these cannot be
excluded or specifically targeted. So not sure why Google is giving us the
traffic, but yet we're unable to control anything about windows apps :
can't pause them, can't add them to exclude list, can't specifically target
them, can't adjust bids programmatically, etc...That seems like a very
strange business practice to me.

But the above workaround fixed my problem for iOS and Android apps.


On Friday, January 18, 2019 at 4:25:56 PM UTC, Dorian Kind wrote:

FWIW, I also reached out to the group back in 2017 about this sort of
placements, and was told that

"[...] these IDs may continue to appear in placement reports for a time
while we continue to work on cleaning up the old data. However, the invalid
IDs do not actually affect your targeting, and they should always come back
with no stats because of this."


If I understand OP correctly, not only do they still appear in the
placement reports, they also accumulate stats now. I'd also like to
understand how we can exclude these (AdMob?) placements.

Best,
Dorian


On Friday, 18 January 2019 16:02:00 UTC+1, PPC Developer wrote:

Hi Luis,

I'm well aware of the format for both iOS and Android. However, these
mobile application IDs are returned by AdWords via a call to get Automatic
Placement Performance report.. So basically, adwords is telling me that
these are the mobile apps that are giving us a lot of clicks. It's not me
trying to construct my own app ID. These are coming back from the API call
to adwords. And when I try to add these to exclusion lists via
NegativeCampaignCriteria, the API returns an error complaining about the
app ID format. So, it's basically AdWords returning these.

I saw another post related to this, https://groups.google.
com/forum/#!searchin/adwords-api/INVALID_MOBILE_APP%7Csort:
date/adwords-api/WUvX2wjhz6U/Xn_x7wdMBgAJ

But, what's the solution?

On Friday, January 18, 2019 at 8:22:08 AM UTC, googleadsapi-forumadvisor
wrote:

Hi,

The format of the app ID that you used was invalid which triggers
the CriterionError.INVALID_MOBILE_APP error. A well formed app ID for
AdWords API would be "1-476943146" for iOS and "2-com.labpixies.colordrips"
for Android. You may check this guide
<https://developers.google.com/adwords/api/docs/reference/v201809/AdGroupCriterionService.MobileApplication#appid> for
details. I would suggest to correct those app ID then retry your request
again.

Let me know if you still encounter any error after doing my suggestion.

Thanks and regards,
Luis
AdWords API Team


=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
    http://googleadsdeveloper.blogspot.com/search/label/adwords_api
    https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Was your question answered? Please rate your experience with us by taking a
short survey.
If not -- reply to this email and tell us what else we can do to help.

Take Survey
<https://support.google.com/google-ads/contact/survey_transactional?caseid=5-5851000025222&hl=en&ctx=1>

Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
On 01/18/19 12:06:25 ppcdev...@mineeds.com wrote:

I'm getting mobile application ID(s) via the API, and trying to add as
negative or biddable criterion to another ad group. In doing so, I get
exceptions:

[CriterionError.INVALID_MOBILE_APP @ operations[103].operand.criterion.appId; trigger:'10002-CA-APP-PUB-8367418828198308', CriterionError.INVALID_MOBILE_APP
@ operations[309].operand.criterion.appId; trigger:'10002-CA-APP-PUB-
8392731756470098']

And I have a lot of these, where I cannot neither add or delete them:
mobileapp::10002-ca-app-pub-8367418828198308
mobileapp::10002-ca-app-pub-8392731756470098
mobileapp::10002-ca-app-pub-4028238683451937
mobileapp::10002-ca-app-pub-8162149483502798
mobileapp::10002-ca-app-pub-5694554969453415
mobileapp::10002-ca-app-pub-1413939963884036
mobileapp::10002-ca-app-pub-5075118958809920
mobileapp::10002-ca-app-pub-2397825577270378
mobileapp::10002-ca-app-pub-4640908852121081
mobileapp::10002-ca-app-pub-3169207933671961
mobileapp::10002-ca-app-pub-4547683005564946
mobileapp::10002-ca-app-pub-9549248647599949
mobileapp::10002-ca-app-pub-3605354403339561


How do I add or delete these mobile apps as adgroupscriterion?

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/2b1b6dad-3a08-4efb-b958-998cb94d26a7%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/2b1b6dad-3a08-4efb-b958-998cb94d26a7%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/4883f471-52c4-4be3-a6ac-365652ea325c%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/4883f471-52c4-4be3-a6ac-365652ea325c%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
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/h0ui9the700000010o0k26005bu5hmw6kmjae1l64o30c1g68qj4chi%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
  • Invalid... PPC Developer
    • RE... googleadsapi-forumadvisor via AdWords API and Google Ads API Forum
      • ... PPC Developer
        • ... Dorian Kind
          • ... PPC Developer
            • ... googleadsapi-forumadvisor via AdWords API and Google Ads API Forum

Reply via email to