Error while creating conversion tracker - DOMAIN_EXCEPTION

[Ondřej P]

Hi,

I have an issue with creating of AdWordsConversionTracker through Java SDK. I found that it depends on parameter conversionPageLanguage. I get ConversionTrackingError.DOMAIN_EXCEPTION error when conversionPageLanguage value is nb (Norwegian Bokmål) or he (Hebrew). Is it because these languages are not supported, or is it a bug?

SOAP Request body:

    <soapenv:Body>
        <mutate xmlns="https://adwords.google.com/api/adwords/cm/v201609">
            <operations>
                <operator>ADD</operator>
                <operand xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201609" xsi:type="ns2:AdWordsConversionTracker">
                    <ns2:name>ROI Hunter Conversion Tracker ID hllf</ns2:name>
                    <ns2:status>ENABLED</ns2:status>
                    <ns2:category>DEFAULT</ns2:category>
                    <ns2:viewthroughLookbackWindow>30</ns2:viewthroughLookbackWindow>
                    <ns2:ctcLookbackWindow>30</ns2:ctcLookbackWindow>
                    <ns2:countingType>MANY_PER_CLICK</ns2:countingType>
                    <ns2:defaultRevenueValue>1.0</ns2:defaultRevenueValue>
                    <ns2:defaultRevenueCurrencyCode>NOK</ns2:defaultRevenueCurrencyCode>
                    <ns2:alwaysUseDefaultRevenueValue>false</ns2:alwaysUseDefaultRevenueValue>
                    <ns2:excludeFromBidding>false</ns2:excludeFromBidding>
                    <ns2:attributionModelType>LAST_CLICK</ns2:attributionModelType>
                    <ns2:textFormat>HIDDEN</ns2:textFormat>
                    <ns2:conversionPageLanguage>nb</ns2:conversionPageLanguage>
                    <ns2:backgroundColor>ffffff</ns2:backgroundColor>
                    <ns2:trackingCodeType>WEBPAGE</ns2:trackingCodeType>
                </operand>
            </operations>
        </mutate>
    </soapenv:Body>

SOAP Response:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201609">
            <requestId>00055159e8d1d8590a3749533200b016</requestId>
            <serviceName>ConversionTrackerService</serviceName>
            <methodName>mutate</methodName>
            <operations>1</operations>
            <responseTime>178</responseTime>
        </ResponseHeader>
    </soap:Header>
    <soap:Body>
        <soap:Fault>
            <faultcode>soap:Server</faultcode>
            <faultstring>[ConversionTrackingError.DOMAIN_EXCEPTION @ operations[0].operand.conversionPageLanguage]</faultstring>
            <detail>
                <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201609">
                    <message>[ConversionTrackingError.DOMAIN_EXCEPTION @ operations[0].operand.conversionPageLanguage]</message>
                    <ApplicationException.Type>ApiException</ApplicationException.Type>
                    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ConversionTrackingError">
                        <fieldPath>operations[0].operand.conversionPageLanguage</fieldPath>
                        <trigger/>
                        <errorString>ConversionTrackingError.DOMAIN_EXCEPTION</errorString>
                        <ApiError.Type>ConversionTrackingError</ApiError.Type>
                        <reason>DOMAIN_EXCEPTION</reason>
                    </errors>
                </ApiExceptionFault>
            </detail>
        </soap:Fault>
    </soap:Body>
</soap:Envelope>

Thank you!

[Peter Oliquino]

Hi,

Could you confirm if you also encounter errors while using other conversion page language options other than "nb" and "he" or is it isolated only for these values? If the issue persists while using other language codes, please send to me the generated SOAP request and response logs and you may reply to me using Reply privately to author.

I also noticed that you are currently using a deprecated version of the AdWords API, and using deprecated versions sometimes result in unexpected errors. You might try upgrading to the latest version to avoid any other unexpected errors.

Best regards,

Peter

AdWords API Team