Offline Conversion Feed DateError.INVALID_FIELD_VALUES_IN_DATE_TIME

[cbmam...@gmail.com]

We have had an upload of offline conversions working for a little over a month using API V201309 and yesterday we started getting errors saying we have an invalid date and time.

snipped from the request:

            <operations>

                <operator>ADD</operator>

                <operand>

                    <googleClickId>CPnNu5z-lb0CFSNk7AoduicA4A</googleClickId>

                    <conversionName>RTLead</conversionName>

                    <conversionTime>20140315 222113</conversionTime>

                    <conversionValue>40.28</conversionValue>

                </operand>

            </operations>

and snipped from the response

                    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="DateError">

                        <fieldPath>operations[0].operand</fieldPath>

                        <trigger/>

                        <errorString>DateError.INVALID_FIELD_VALUES_IN_DATE_TIME</errorString>

                        <ApiError.Type>DateError</ApiError.Type>

                        <reason>INVALID_FIELD_VALUES_IN_DATE_TIME</reason>

                    </errors>

The documentation doesn't list valid formats and the field is a string rather than xsd:dateTime.  What should be valid and what happened?

thanks,

Chris

[Ray Tsang (AdWords API Team)]

Chris,

Please make sure that the time is after the click time and also not in the future.  Secondly, can you try this format instead?

  yyyy-MM-dd HH:mm:ss

Cheers,

[cbmam...@gmail.com]

Ray,

      The format you are suggesting also produces an error but not exactly the same one.

snippet from the request:

            <operations>

                <operator>ADD</operator>

                <operand>

                    <googleClickId>CPHt9bfblL0CFchZ7AodFGcAHA</googleClickId>

                    <conversionName>RTLead</conversionName>

                    <conversionTime>2014-03-15 10:13:25</conversionTime>

                    <conversionValue>110.28</conversionValue>

                </operand>

            </operations>

response

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

    <soap:Body>

        <soap:Fault>

            <faultcode>soap:Server</faultcode>

            <faultstring>DateError.INVALID_STRING_DATE_TIME @ ; trigger:'2014-03-15 10:13:25'</faultstring>

            <detail>

                <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201309">

                    <message>DateError.INVALID_STRING_DATE_TIME @ ; trigger:'2014-03-15 10:13:25'</message>

                    <ApplicationException.Type>ApiException</ApplicationException.Type>

                    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="DateError">

                        <fieldPath/>

                        <trigger>2014-03-15 10:13:25</trigger>

                        <errorString>DateError.INVALID_STRING_DATE_TIME</errorString>

                        <ApiError.Type>DateError</ApiError.Type>

                        <reason>INVALID_STRING_DATE_TIME</reason>

                    </errors>

                </ApiExceptionFault>

            </detail>

        </soap:Fault>

    </soap:Body>

</soap:Envelope>

Thanks,
Chris

[Ray Tsang (AdWords API Team)]

Chris,

My apologies.  Could I trouble you to append the timezone to your original format?  The timezone should be the same as the timezone associated w/ the AW account that you are uploading the conversion to, e.g.:

20140315 222113 EST

Thanks,

Ray

[Ray Tsang (AdWords API Team)]

Chris,

Just to clarify the timezone values - those are documented here: https://developers.google.com/adwords/api/docs/appendix/timezones

And that you should be able to specify a timezone thta's not the same as the AW account.

Cheers,

Ray

[Chris Marshall]

Ray,

    One of the other thread described trying –08:00 for the timezone.  I used –05:00 and that worked.

Thanks,

Chris

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@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 Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.