DCM API upload offline conversions - INVALID_ARGUMENT - The timestampMicros is too old
430 views
Skip to first unread message
Anirudh Bizlawan
Jul 25, 2019, 2:14:26 PM7/25/19
to Google's DoubleClick Campaign Manager API Forum
Hello Group,
I am new to this group and am also using this API for the first time. I am in the process of setting up an offline conversions upload to Campaign Manager floodlights. I have been able to set up appropriate permissions to access the floodlights with the conversions API, however, I have run into this issue where even though the web service request executes successfully (200 OK), the batchinsert method seems to be failing a certain validation for my request. The error message sounds pretty straightforward, however, I have tried to resolve this by sending current UNIX time as the timestamp as well, and the error comes back as the same, "The timestampMicros is too old". I have pasted my request below:
{
"kind": "dfareporting#conversionsBatchInsertRequest",
"conversions": [
{
"kind": "dfareporting#conversion",
"floodlightConfigurationId": 6384424,
"floodlightActivityId": 8696163,
"encryptedUserId": "",
"encryptedUserIdCandidates": [],
"mobileDeviceId": "",
"gclid": "CKPsp4aX4uICFY2PxQIdNU8Ncw",
"limitAdTracking": false,
"childDirectedTreatment": false,
"nonPersonalizedAd": true,
"treatmentForUnderage": false,
"timestampMicros": 1564078345,
"value": 1,
"quantity": 1,
"ordinal": "1",
"customVariables": [
{
"kind": "dfareporting#customFloodlightVariable",
"type": "U11",
"value": ""
}
]
}
]
}
I am using the batchinsert endpoint for this request. I am getting 200 success code with the following response object
{
"kind": "dfareporting#conversionsBatchInsertResponse",
"hasFailures": true,
"status": [
{
"kind": "dfareporting#conversionStatus",
"conversion": {
"kind": "dfareporting#conversion",
"floodlightConfigurationId": "6384424",
"floodlightActivityId": "8696163",
"encryptedUserId": "",
"mobileDeviceId": "",
"gclid": "CKPsp4aX4uICFY2PxQIdNU8Ncw",
"limitAdTracking": false,
"childDirectedTreatment": false,
"nonPersonalizedAd": true,
"treatmentForUnderage": false,
"timestampMicros": "1564078345",
"value": 1.0,
"quantity": "1",
"ordinal": "1",
"customVariables": [
{
"kind": "dfareporting#customFloodlightVariable",
"type": "U11",
"value": ""
}
]
},
"errors": [
{
"kind": "dfareporting#conversionError",
"code": "INVALID_ARGUMENT",
"message": "The timestampMicros is too old"
}
]
}
]
}
Anirudh Bizlawan
Jul 25, 2019, 2:29:07 PM7/25/19
to Google's DoubleClick Campaign Manager API Forum
I found the issue in my request. I was passing the EPOCH time in seconds instead of microseconds.
Reply all
Reply to author
Forward
0 new messages