I am trying to post so simple test data using the data insertion api ...
I'm receiving a success response, but the data is not showing up in the site catalyst report. I'm wondering if there is a log or status I can check to see what the processing problems were?
As far as I can tell, the required fields are present and seem to contain valid data. I'm sure there is an issue, I just can't see what it is.
Below is the sample data:
Here is the URL I’m posting to:
http://ebmgllumcpro.112.2o7.net/b/ss//6
I’ve also tried 112.207.net as the domain … both return a success.
Here is the xml body I’m posting:
<?xml version="1.0" encoding="UTF-8" ?>
<request>
<scXmlVer>1.0</scXmlVer>
<reportSuiteID>ebmgllumcpro</reportSuiteID>
<timestamp>2009-07-02T13:18:34-00</timestamp>
<visitorID>4a4d1d22d6515</visitorID>
<pageURL>http://www.twitter.com</pageURL>
<pageName>Twitter</pageName>
<prop7>Cancer Treatment</prop7>
</request>
I have tried this with different combinations of visitorID and timestamp …
I’ve also used different prop values and all prop values were setup in site catalyst.
timestamp data is usually 1 day behind.
The pageURL and pageName are the above for some of the data and a URL/name for some.
All the above combinations seem to return the following:
<?xml version="1.0" encoding="UTF-8"?>
<status>SUCCESS</status>
My test posts using visitorId have sent 5 posts with 3 being 1 visitor ID and 2 posts being a different visitor ID.
Based on the report suite ID, it appears you are receiving live data from a JavaScript implementation which will give you problems based on the example you submitted.
The core problem is the timestamp field. During the JavaScript implementation all data is sent without a timestamp and is assigned a timestamp once it is accepted by the collection server.
The XML you provide contains a timestamp which is causing the problem because, as silly as it may sound, a report suite can be configured to only accept data that is either pretimestamped or not. Because you are accepting JS beacons, you are configured to accept non-timestamped hits and as a result the XML hits with timestamps are being rejected despite being told they are successfully accepted.
In short to fix the issue, simply remove the timestamp field in your XML request. This has a down side though as you can't back date data. The hit will be processed and timestamped based on when it was received, just like the JavaScript beacons.
If you need to insert historical data, use Full Processing Data Sources, which is a batch file upload process that does accept timestamped hits for any historical timeframe.
I hope this helps.
Nick