AppId with strange platform code?

205 views
Skip to first unread message

Berry

unread,
Jan 7, 2016, 8:06:38 AM1/7/16
to AdWords API Forum
Hi,

In the URL performance report i'm getting some entries with field 'URL' that start with "mobileapp::10001-...".
From the documentation, the platform codes should be either 1 (iOS) or 2 (Android).Which platform do these apps belong to?
These entries are not present in the UI.

Thanks

Nadine Sundquist (AdWords API Team)

unread,
Jan 7, 2016, 11:29:10 AM1/7/16
to AdWords API Forum
Hi Berry,

I haven't seen that one before, either. Could you please click Reply privately to author in the forum and send me your customer ID where you're seeing this along with the date range that you're using to pull your report? Even the report query with the customer ID would help. In the meantime, I'll ask around to see if anyone has seen this before.

Thanks,
Nadine, AdWords API Team

Nadine Sundquist (AdWords API Team)

unread,
Jan 11, 2016, 3:25:30 PM1/11/16
to AdWords API Forum
Hi Berry,

Thanks for sending over the additional information. I'm posting the answer publicly rather than directly to you to help other people who may see this. Here's the mapping.
  • mobileapp::10001-<site id> iOS apps with either very long or empty app IDs
  • mobileapp::10002-<site id> Google Play apps with either very long or empty app IDs
As far as I can tell, this case doesn't happen very often.

Cheers,
Nadine, AdWords API Team

On Thursday, January 7, 2016 at 8:06:38 AM UTC-5, Berry wrote:

Dorian Kind

unread,
Aug 31, 2018, 8:57:21 AM8/31/18
to AdWords API and Google Ads API Forum
Hi,

sorry for bringing this old thread back to life, but I just stumbled over mobile apps whose platform code is none of the above, but 3. As an example:

mobileapp::3-6a12c4cf-5681-4db2-a433-7aaa063aab35

Is there any information about what this platform code corresponds to?

Thanks and best regards,
Dorian

Nadine Sundquist (AdWords API Team)

unread,
Aug 31, 2018, 10:28:31 AM8/31/18
to AdWords API and Google Ads API Forum
Hello Dorian,

The 3 after mobileapp indicates that it's from the Windows store. I don't see it that often myself, but I think it's cool that your business is growing enough to start picking up even more platforms. Congrats!

Cheers,
Nadine, AdWords API Team

Dorian Kind

unread,
Aug 31, 2018, 10:47:17 AM8/31/18
to AdWords API and Google Ads API Forum
Hi Nadine,

thanks a lot for your quick reply! I noticed that it's not yet possible to use this format over the API—I got a CriterionError.INVALID_MOBILE_APP error. Can we expect Windows Store apps to be supported it one of the upcoming API revisions?

Cheers,
Dorian

Nadine Sundquist (AdWords API Team)

unread,
Aug 31, 2018, 1:49:15 PM8/31/18
to AdWords API and Google Ads API Forum
HI Dorian,

You ask your questions so clearly, so it makes it a lot easier to reply quickly. I don't know the answer to whether or not it will be supported; I wasn't aware it wasn't because I haven't tried it. I have started a thread internally asking that question. Hopefully, someone gets back to me soon.

Regards,
Nadine, Adwords API Team

Nadine Sundquist (AdWords API Team)

unread,
Aug 31, 2018, 2:32:50 PM8/31/18
to AdWords API and Google Ads API Forum
Hello Dorian,

I already got an answer back on my thread. Woohoo! It looks like we're only supporting iOS and Android on serving, and I don't see any plans to add Windows soon.

Take care,
Nadine, AdWords API Team

david

unread,
Oct 22, 2018, 9:05:44 AM10/22/18
to AdWords API and Google Ads API Forum
Hi sorry to hijack this old thread.

We've encountered some appIDs within automatic placements which are of the format you mentioned...

In this case:

10001-ca-gmail

Problem is we'd like to create a negative placement for it, but the CampaignCriterionService keeps returning INVALID_MOBILE_APP when we use "10001-ca-gmail" as the appId within a NegativeCampaignCriterion object.


The SOAP request body would be:

<SOAP-ENV:Body> <mutate xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <operations> <operator>ADD</operator> <operand xsi:type="NegativeCampaignCriterion" > <campaignId>123456789</campaignId> <criterion xsi:type="MobileApplication" > <appId>10001-ca-gmail<appId>
</criterion> </operand> </operations> </mutate> </SOAP-ENV:Body>

The response we're getting is the following. Is there a way to achieve a negative placement for such an appId?
Thanks

<?xml version="1.0"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <requestId>000578ce5282c4380a372fc45c03ba6d</requestId> <serviceName>CampaignCriterionService</serviceName> <methodName>mutate</methodName> <operations>1</operations> <responseTime>158</responseTime> </ResponseHeader> </soap:Header> <soap:Body> <soap:Fault> <faultcode>soap:Client</faultcode> <faultstring>[CriterionError.INVALID_MOBILE_APP @ operations[0].operand.criterion.appId; trigger:'10001-ca-gmail']</faultstring> <detail> <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201802"> <message>[CriterionError.INVALID_MOBILE_APP @ operations[0].operand.criterion.appId; trigger:'10001-ca-gmail']</message> <ApplicationException.Type>ApiException</ApplicationException.Type> <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CriterionError"> <fieldPath>operations[0].operand.criterion.appId</fieldPath> <fieldPathElements> <field>operations</field> <index>0</index> </fieldPathElements> <fieldPathElements> <field>operand</field> </fieldPathElements> <fieldPathElements> <field>criterion</field> </fieldPathElements> <fieldPathElements> <field>appId</field> </fieldPathElements> <trigger>10001-ca-gmail</trigger> <errorString>CriterionError.INVALID_MOBILE_APP</errorString> <ApiError.Type>CriterionError</ApiError.Type> <reason>INVALID_MOBILE_APP</reason> </errors> </ApiExceptionFault> </detail> </soap:Fault> </soap:Body> </soap:Envelope>

Nadine Sundquist (AdWords API Team)

unread,
Oct 22, 2018, 4:39:08 PM10/22/18
to AdWords API and Google Ads API Forum
Hello David,

This looks like a slightly different issue, so could you please start a new thread and just refer to this thread? That would be really helpful. That way people in the future don't get lost in this thread if they are looking for an answer to a specific question.

Thanks a bunch,
Nadine, AdWords API Team
Reply all
Reply to author
Forward
0 new messages