Avo Functions in Swift

5 minute read

Platforms

Avo can code generate Avo Functions in Swift targeted at the following platforms

  • iOS
  • macOS

Quickstart

Avo functions usage consists of 4 steps.

Step 1. Include the Avo file

Pull the generated code with the Avo CLI

To get the Avo generated Swift file you must be a member of an Avo workspace with a Swift source. Ask for an invite from a colleague or create a new workspace

Terminal
Copy
$
$
$
npm install -g avo
avo login
avo pull --branch my-branch-name

Learn more about the CLI here.

You can also download the file manually from your Avo workspace.

Step 2. Initialize Avo

Initialize Avo by creating an object using constructor from the generated Avo file

Swift
Copy
1
val avo = Avo(env: .dev/*, other parameters depending on your tracking plan setup*/)

The actual parameters depend on your tracking plan setup, see the parameters explanation in the reference below.

Step 3. Call Avo functions to track your product usage

Every event in your tracking plan, marked with the "Implement with Avo" checkbox, gets a function in the generated code, named according to the event name, in camelCase.

For example, if you have a "Signup Start" event defined like this in Avo:

Event 'Signup Start' defined in Avo with referral string property and implement with Avo check

You'll be able to call it like this from the generated code

Swift
Copy
1
avo.signupStart(referral: "direct")

Notice, that you are not passing the System property with the call. System properties are defined on the init step and then automatically included with all events. You can update the system properties with setSystemProperties function.

Step 4. Verify the implementation

Use the Implementation status in your Avo workspace and the Avo Inspector to verify that your implementation is correct. If you don't want to use the Avo Inspector you can use the standalone visual debugger.

Reference

Constructor

Swift
Copy
1
2
3
4
5
public init(env: AvoEnv,
// Other parameters may not be present, depending on your tracking plan
systemProperty0: Int, systemProperty1: Bool,
customDestination: AvoCustomDestination,
strict: Bool = true, noop: Bool = false)

Creates the Avo object that will be used to track. This method will initialize the SDKs for all destinations that are managed by Avo, and call the make(env) callback in all provided custom destinations.

Arguments

env: AvoEnv: Can be set to dev, prod and staging.

systemProperties: a number of parameters equal to the number of system properties defined in your Avo workspace. The parameters are named the same as system properties, in camelCase, and require corresponding types: string, int, long, float, bool, list, object or any.

customDestination: AvoCustomDestination: object, required if target source has a custom destination set up in Avo. Otherwise not present.

Custom destination protocol format:

Swift
Copy
1
2
3
4
5
6
7
public protocol AvoCustomDestination {
func make(env: AvoEnv)
func logEvent(eventName: String, eventProperties: [String:Any])
func setUserProperties(userId: String, userProperties: [String:Any])
func identify(userId: String)
func unidentify()
}

Read more about custom destinations here.

strict: Bool = true: bool, default value is true, if true, Avo will throw an exception when it detects a tracking problem in development or staging. Note that the strict flag is ignored in production.

noop: Bool = false: bool, default value is false, if true, Avo won't make any network calls (no tracking) in development and staging environments. Note that the noop flag is ignored in production.

Note that you do not need to pass the Avo Inspector instance to the constructor. It will be automatically picked up if you include the library and enable Avo Inspector for your iOS source in the Avo workspace. Read more here.

avoLogger

Swift
Copy
1
var avoLogger: AvoLogger

where avoLogger conforms to a protocol

Swift
Copy
1
2
3
4
5
public protocol AvoLogger {
func logDebug(env: AvoEnv, message: String) -> Bool
func logWarn(env: AvoEnv, message: String) -> Bool
func logError(env: AvoEnv, message: String) -> Bool
}

Allows you to provide custom implementation of the logger used by the Avo Functions. Can for example be used to disable logs or change which logging method is used.

Find the code snippet here.

setSystemProperties

Swift
Copy
1
public func setSystemProperties(systemProperty0: Int, systemProperty1: Bool?, ...)

A method to update system properties after initialization.

Arguments

systemProperties: a number of parameters equal to the number of system properties defined in your Avo workspace. The parameters are named the same as system properties, in camelCase, and require corresponding types: string, int, long, float, bool, list, object or any.

Event tracking functions

Swift
Copy
1
public func [yourEventName](eventProperty0: Int, eventProperty1: Double?, ..., userProperty0: Bool?, userProperty1: [Int], ..., userId_: String)

Every event you define in your tracking plan in Avo gets a function named after the event in camelCase. The arguments of the function depend on how it's defined in your tracking plan

Arguments

eventProperty: type defined in the Avo tracking plan, can be string, int, long, float, bool, list, object and any: Every event property attached to the event in the Avo UI gets a corresponding argument. The argument key is camelCase version of the property name. Pass the value of the property to track here.

userProperty: type defined in the Avo tracking plan as a user property, can be string, int, long, float, bool, list, object and any: Every user property attached to the event in the Avo UI gets a corresponding argument. The argument key is camelCase version of the property name. Pass the value of the property to update here.

userId_: String: used to connect event to specific user. Added if the event has the Identify User action

Destinations

You can send your data using the Avo generated Swift code to any data destination that accepts custom events, including:

  • Amplitude
  • FacebookAnalytics
  • FullStory
  • Mixpanel
  • Mixpanel
  • Permutive
  • Segment
  • Snowplow
  • ZendeskConnect
  • Adobe Analytics
  • Apptelemetry
  • Rudderstack
  • Freshpaint
  • Posthog
  • Google Analytics 4 / Firebase Analytics
  • Heap
  • Keen
  • Kissmetrics
  • LaunchDarkly Events
  • Pendo
  • Fivetran
  • AppsFlyer
  • Braze
  • Intercom
  • A home made SDK
  • Internal API