FlurryWatch Class Reference

Inherits NSObject.

Class Methods
(FlurryEventRecordStatus)	+ logWatchEvent:
	Records a custom event specified by eventName. More...
(FlurryEventRecordStatus)	+ logWatchEvent:withParameters:
	Records a custom parameterized event specified by eventName with parameters. More...

Detailed Description

Definition at line 11 of file FlurryWatch.h.

Method Documentation

+ (FlurryEventRecordStatus) logWatchEvent:

(NSString *)

eventName

Records a custom event specified by eventName.

Since

6.4.0

This method allows you to specify custom watch events within your watch extension. As a general rule you should capture events related to user navigation within your app, any actionaround monetization, and other events as they are applicable to tracking progress towards your business goals.

Note

You should not pass private or confidential information about your users in a custom event.
This method is only supported within a watch extension.

See Also

+ logWatchEvent:withParameters: for details on storing events with parameters.

   - (void)interestingAppAction
{
[FlurryWatch logWatchEvent:@"Interesting_Action"];
// Perform interesting action
}

Parameters

eventName

Name of the event. For maximum effectiveness, we recommend using a naming scheme that can be easily understood by non-technical people in your business domain.

Returns

enum FlurryEventRecordStatus for the recording status of the logged event.

+ (FlurryEventRecordStatus) logWatchEvent:		(NSString *)	eventName
withParameters:		(NSDictionary *)	parameters

Records a custom parameterized event specified by eventName with parameters.

Since

6.4.0

This method overloads #logWatchEvent to allow you to associate parameters with an event. Parameters are extremely valuable as they allow you to store characteristics of an action. For example, if a user clicked a confirmation button, it may be useful to know the reservation details. By setting this parameter you will be able to view a distribution of reservations on the Flurrly Dev Portal.

Note

You should not pass private or confidential information about your users in a custom event.
A maximum of 10 parameter names may be associated with any event. Sending over 10 parameter names with a single event will result in no parameters being logged for that event. You may specify an infinite number of Parameter values. For example, a Search Box would have 1 parameter name (e.g. - Search Box) and many values, which would allow you to see what values users look for the most in your app.
Where applicable, you should make a concerted effort to use timed events with parameters (#logEvent:withParameters:timed:). This provides valuable information around the time the user spends within an action (e.g. - time spent on a level or viewing a page). This method is only supported within a watch extension.

   - (void)userConfirmedTheReservation
{
NSDictionary *params =
[NSDictionary dictionaryWithObjectsAndKeys:@"Great Restaurant", // Parameter Value
@"Destination", // Parameter Name
nil];
[FlurryWatch logWatchEvent:@"Reservation Confirmed" withParameters:params];
// Confirm the reservation
}

Parameters

eventName	Name of the event. For maximum effectiveness, we recommend using a naming scheme that can be easily understood by non-technical people in your business domain.
parameters	An immutable copy of map containing Name-Value pairs of parameters.

Returns

enum FlurryEventRecordStatus for the recording status of the logged event.

---

The documentation for this class was generated from the following file:

• /Users/sd_builder_43497419/sd/src/git.vzbuilders.com/flurry/IOSSDK/FlurrySDK/PublicAPIs/FlurryAPI/FlurryWatch.h