Your implementation seems beautiful. I don't think this is a problem (and since you are getting major events, this is probably not an initialization problem). I have the same way of recording synchronization events (you can find my code below if you want to compare).
I can tell you:
1 / This is beta strong> (yes, everything @google is in beta xD) is rather unstable, and events require time to be displayed in the administration (I do not see, for example, any events for February 18). At least more than for a site with similar statistics.
2 / I can not display time events for more than 2 days or show me some errors ^^ (maybe too much data is set for a large time zone)
3 / If there is no tag, do not put a category, just set nil. The same goes for the name. I think both of them are optional parameters. And this will slow down the display of your analytics when you have more statistics.
4 / For a large dataset, temporary events are calculated based on your visits. But that should not be your problem right now ^^ http://support.google.com/analytics/bin/answer.py?hl=en&answer=1042498
Wait 2 days. If you still donβt see anything, try contacting your Google Analytics representative. Or take the "risk" to send it as it is.
My implementation
(in case this may help)
+ (void)trackGoogleTimingInCategory:(NSString *)category withTimeInterval:(NSTimeInterval)time withName:(NSString *)name withLabel:(NSString *)label { // if (![ category isKindOfClass:[ NSString class ] ]) return; NSLog(@"[%@] %@ time=%f (%@)", category, name, time, label); // if (![ name isKindOfClass:[ NSString class ] ]) name = nil; if (![ label isKindOfClass:[ NSString class ] ]) label = nil; // [ [ [ GAI sharedInstance ] defaultTracker ] sendTimingWithCategory:category withValue:time withName:name withLabel:label ]; }
To calculate the time, I do the same:
NSTimeInterval timeInterval = [ [ NSDate date ] timeIntervalSinceDate:timeStart ];
Vinzius
source share