 |
 |
 |
|
03.16.09 Understanding The Use Of Omniture’s Token System 
By Gary AngelIn my next post, I'm going to dive down and talk in more detail how the API actually works and show pieces of a real application. But before I go there, I wanted to touch one more time on tokens and give any programmers out there a heads-up on the "Great Token Gotcha." In my last post, I described Omniture's token system - the basic metering systems that controls how many API requests you can make and how they cost. In essence, each API request you make costs you a token. And to use the reporting API, you have to submit a request and then you have to get the report. So you typically use two tokens per request. Simple? It is, but there is a big gotcha out there. Here's how it works. To make a request to the API, you build up a report object that tells Omniture what data you want to retrieve and what time period you are looking for. When you've defined everything, you submit your report. So far so good. Now here comes the tricky part. Most Omniture Sample code works the same way. After the request is submitted, you go into a wait loop. You pause your program for a second or two, request the report object to see if it's finished. If it's done, you are good to go. If it's not done, you wait for another second or two and check again.
Here's some heavily commented code (this whole post is really for programmers so feel free to skip if your interest in the API is more on the business site): //request the report reportQueueResponse response = glob.ws.ReportQueueRanked(rd); // Wait for 1000 milliseconds or 1 second System.Threading.Thread.Sleep(1000); // Grab report reportResponse reportR = glob.ws.ReportGetReport(response.reportID); // If the report is not ready then wait and check to see if it is ready while (reportR.status != "done") { // Wait another second System.Threading.Thread.Sleep(1000); // Check the report again reportR = glob.ws.ReportGetReport(response.reportID) // Keep checking (go back to the while until the reportR.status is done } This is a simple, obvious way to manage your code. There are others, but this is the way most of the Omniture examples on their dev site are built and it makes perfect sense. It's also terribly wrong and the reason isn't programmatic. What is hidden in the system is that Omniture will dock you a token for each and every time you make the: Continue reading this article. About the Author: Gary Angel is the author of the "SEMAngel blog - Web Analytics and Search Engine Marketing practices and perspectives from a 10-year experienced guru. |
||||||||
|
| ||
| -- DevWebPro India
is an iEntry, Inc. publication -- iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509 2009 iEntry, Inc. All Rights Reserved Privacy Policy Legal archives | advertising info | news headlines | free newsletters | comments/feedback | submit article |
