Maximum concurrent Data Insertion connections from a server

Hi all, When using Data Insertion is there a limit on the amount of concurrent connections from a host to the Omniture data collection servers? Also, when using a timestamp enabled report suite the documentation states that when a report suite is collecting timestamped data it cannot collect data from the standard beacon collection method. Does this mean that the standard beacon method is just not available at the time of data insertion or is it not possible at all to send web beacon data to this report suite? Regards, Riaan
To answer the first question, there shouldn't scaling issues when sending data to Omniture. If you want to spawn multiple child threads to handle the data submission, this wouldn't be any different than our JavaScript implementation and having multiple visitors hitting the site at the same time. The only issue would come to bandwidth. With the JavaScript model, all beacons are distributed across the web because they are sent from where the visitor is physically located. With the Data Insertion API, all hits are sent from a smaller set of servers which could put a strain on your bandwidth depending on the volume you are expecting. Regarding your second question, you can make hits sent via the Data Insertion API co-exist with a JavaScript implementation as long as you send the hit near-real time, utilize the Omniture Cookie for visitor persistence and don't include a time stamp on the hit. If you start sending hits with a time stamp, a special configuration for the report suite will be needed to process these hits sent from the Data Insertion API correctly but will disrupt data coming in via a Java Script Implementation. Hope that helps, Nick
Reply
Out of curiosity, how many connections do you hope to utilize? Thanks! -Brent
Reply
Hi Riaan, I don't know the answer to the first question. However, for your second question -- a report suite is either timestamp-enabled, or it's not (it's just a switch than can be turned on or off). If it is timestamp-enabled, all non-timestamped (ie, standard beacon) hits sent to the report suite will be thrown away. If it is not timestamp-enabled, all timestamped hits will be thrown away. So, either use two separate report suites, or use a timestamped report suite and set s.timestamp on your beacon code with the current time (then the hit will not be thrown away). Hopefully that helps.
Reply
Hi Brent, At this stage I can't say, its actually a client that was asking me that as they wish to use the API for some parts of their site. Regards, Riaan
Reply
Much appreciated.
Reply
Hi, if you use a timestamped report suite, do we need to set s.timestamp in the s_code in the following format?: 2009-03-05T01:00:01-05 Would anyone be able to provide me with a sample code please? Thanks, Corina
Reply
Format the timestamp data, including time zone, using the Unix timestamp format, or ISO-8601 format. For example, suing the ISO-8601 format, a timestamp for a visitor event that occurred on November 17, 2008 at 5:33 PM Mountain Time (GMT-7:00:00) is as follows: 2008-11-17T17:33:22-07 So yes, this is the correct format. For more information on a Java Script Implementation, refer to Omniture's Knowledge Base. Nick
Reply

Must be logged in to comment. now to comment!