INVALID_MOBILE_APP when creating negative placement for 10001-ca-gmail appid

[david]

Hi,

We've encountered some appIDs within automatic placements which are not of the format we would usually expect.
This thread mentions some alternatives to the 1- (iOS) or 2- (Android) format:

https://groups.google.com/d/msg/adwords-api/7n3tKhv36uc/8tdQl0x_DgAJ

 

In this case the appId is:

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>

[Luis Xander Talag (AdWords API Team)]

Hi David,

As you may already know, this appId is not in the right format which is why you're getting the INVALID_MOBILE_APP error. For IOS, the 9 digit string, while for android, the application's package name. For your "ca-gmail" value, it appears that this is not the right format. Could you provide more details as to where you were able to get the appId: 10001-ca-gmail? Could you also try to set the appId value as mobileapp::10001-ca-gmail?

Thanks,

Luis

AdWords API Team

[david]

The mobileapp::10001-ca-gmail is passed to us from the AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT in the Domain field.

The report XML request would be something like:

<reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201802">

<selector>

<fields>Domain</fields>

<fields>CampaignName</fields>

<fields>CampaignId</fields>

<fields>AdGroupName</fields>

<fields>AdGroupId</fields>

<fields>Impressions</fields>

<fields>Clicks</fields>

<fields>Cost</fields>

<fields>Conversions</fields>

<fields>ConversionValue</fields>

<predicates><field>CampaignStatus</field>

<operator>EQUALS</operator>

<values>ENABLED</values></predicates>

<predicates><field>AdGroupStatus</field>

<operator>EQUALS</operator>

<values>ENABLED</values></predicates>

<dateRange>

<min>20181024</min>

<max>20181024</max>

</dateRange>

</selector>

<reportName>AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT</reportName>

<reportType>AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT</reportType>

<dateRangeType>CUSTOM_DATE</dateRangeType>

<downloadFormat>XML</downloadFormat>

</reportDefinition>

Using the full domain "mobileapp::10001-ca-gmail" gives the same error from CampaignCriterionService when trying to create a negative placement.

<?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>000578f5a0ba07200a375dc33509a906</requestId>

      <serviceName>CampaignCriterionService</serviceName>

      <methodName>mutate</methodName>

      <operations>1</operations>

      <responseTime>177</responseTime>

    </ResponseHeader>

  </soap:Header>

  <soap:Body>

    <soap:Fault>

      <faultcode>soap:Client</faultcode>

      <faultstring>[CriterionError.INVALID_MOBILE_APP @ operations[0].operand.criterion.appId; trigger:'mobileapp::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:'mobileapp::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>mobileapp::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>

We get a few mobileapp:: domains which follow this pattern:

 mobileapp::10002-ca-app-pub-xxxxxxxxx

 mobileapp::10002-ca-mb-app-pub-xxxxxxxx

 mobileapp::10001-ca-mb-app-pub-xxxxxxxx

 mobileapp::10001-ca-gmail

Regards.

[Luis Xander Talag (AdWords API Team)]

Hi David,

Can you provide your clientCustomerId as well so I can further investigate the issue on my end? You can send it to me via Reply privately to author.

Thanks,

Luis
AdWords API Team

[axel.v...@gmail.com]

Hi -- we're getting exactly the same issue here. We're also unable to add negative mobile app placements for oddly formatted placements, including:

- "10002-ca-mb-app-pub-8856559311549217"

- "10002-ca-app-pub-2674296320769492"

- "10001-ca-gmail"

We're finding these across many different CIDs (especially the gmail one).

This is an old thread, but what was the solution in the end?

Thanks for your help!

Axel

[Google Ads API Forum Advisor]

Hi Axel,

Thank you for reaching out to our API support team.

The previous thread discussed an issue with the old AdWords API. So our team can investigate on the Google Ads API perspective, could you share your complete request and response logs and request-id, that returned the INVALID_MOBILE_APP error?

If you haven't yet, logging can be enabled by referring to this guide and by using the DEBUG log setting.

You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2iNeWE:ref