Skip to content

Initial SDK setup

This reference article covers how to install the Braze SDK for tvOS. Installing the Braze SDK will provide you with basic analytics functionality.

The tvOS Braze SDK should be installed or updated using CocoaPods, a dependency manager for Objective-C and Swift projects. CocoaPods provides added simplicity for integration and updating.

tvOS SDK CocoaPods integration

Step 1: Install CocoaPods

Installing the SDK via the tvOS CocoaPods automates the majority of the installation process for you. Before beginning this process, ensure that you are using Ruby version 2.0.0 or greater.

Run the following command to get started:

$ sudo gem install cocoapods

Step 2: Constructing the Podfile

Now that you’ve installed the CocoaPods Ruby Gem, you’re going to need to create a file in your Xcode project directory named Podfile.

Add the following line to your Podfile:

target 'YourAppTarget' do
  pod 'Appboy-tvOS-SDK'

We suggest you version Braze so pod updates automatically grab anything smaller than a minor version update. This looks like pod 'Appboy-tvOS-SDK' ~> Major.Minor.Build. If you want to ,automatically integrate the latest Braze SDK version, even with major changes, you can use pod 'Appboy-tvOS-SDK' in your Podfile.

Step 3: Installing the Braze SDK

To install the Braze SDK CocoaPods, navigate to the directory of your Xcode app project within your terminal and run the following command:

pod install

At this point, you should be able to open the new Xcode project workspace created by CocoaPods. Make sure to use this Xcode workspace instead of your Xcode project.

Step 4: Updating your app delegate

Add the following line of code to your AppDelegate.m file:

#import <AppboyTVOSKit/AppboyKit.h>

Within your AppDelegate.m file, add the following snippet within your application:didFinishLaunchingWithOptions method:

[Appboy startWithApiKey:@"YOUR-API-KEY"

Lastly, update YOUR-API-KEY with the correct value from your Manage Settings page.

If you are integrating the Braze SDK with CocoaPods or Carthage, add the following line of code to your AppDelegate.swift file:

import AppboyTVOSKit

For more information about using Objective-C code in Swift projects, see the Apple Developer Docs.

In AppDelegate.swift, add following snippet to your application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool:

Appboy.start(withApiKey: "YOUR-API-KEY", in:application, withLaunchOptions:launchOptions)

Next, update YOUR-API-KEY with the correct value from your Manage Settings page.

Our sharedInstance singleton will be nil before startWithApiKey: is called, as that is a prerequisite to using any Braze functionality.

Step 5: Specify your custom endpoint or data cluster

Your Braze representative should have already advised you of the correct endpoint.

If given a pre-existing custom endpoint:

  • Starting with Braze iOS SDK v3.0.2, you can set a custom endpoint using the Info.plist file. Add the Appboy dictionary to your Info.plist file. Inside the Appboy dictionary, add the Endpoint string subentry and set the value to your custom endpoint URLs authority (for example,, not

Runtime endpoint configuration

If given a pre-exisiting custom endpoint:

  • Starting with Braze iOS SDK v3.17.0+, you can override set your endpoint via the ABKEndpointKey inside the appboyOptions parameter passed to startWithApiKey:inApplication:withLaunchOptions:withAppboyOptions:. Set the value to your custom endpoint URL authority (for example,, not

SDK integration complete

Braze should now be collecting data from your application, and your basic integration should be complete. Note that when compiling your tvOS app and any other third-party libraries, Bitcode must be enabled.

Updating the Braze SDK via CocoaPods

To update a CocoaPod, simply run the following commands within your project directory:

pod update

Customizing Braze on startup

If you wish to customize Braze on startup, you can instead use the Braze initialization method startWithApiKey:inApplication:withLaunchOptions:withAppboyOptions and pass in an optional NSDictionary of Braze startup keys.

In your AppDelegate.m file, within your application:didFinishLaunchingWithOptions method, add the following Braze method:

[Appboy startWithApiKey:@"YOUR-API-KEY"

In AppDelegate.swift, within your application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool method, add the following Braze method:

Appboy.start(withApiKey: "YOUR-API-KEY",

where appboyOptions is a Dictionary of startup configuration values.

This method would replace the startWithApiKey:inApplication:withLaunchOptions: initialization method and is called with the following parameters:

  • YOUR-API-KEY: Your application’s API key is found under Manage Settings in the Braze dashboard.
  • application: The current app.
  • launchOptions: The options NSDictionary that you get from application:didFinishLaunchingWithOptions:.
  • appboyOptions: An optional NSDictionary with startup configuration values for Braze.

See Appboy.h for a list of Braze startup keys.

Appboy.sharedInstance() and Swift nullability

Differing somewhat from common practice, the Appboy.sharedInstance() singleton is optional. This is because sharedInstance is nil before startWithApiKey: is called, and there are some non-standard but not-invalid implementations in which a delayed initialization can be used.

If you call startWithApiKey: in your didFinishLaunchingWithOptions: delegate before any access to Appboy’s sharedInstance (the standard implementation), you can use optional chaining, like Appboy.sharedInstance()?.changeUser("testUser"), to avoid cumbersome checks. This will have parity with an Objective-C implementation that assumed a non-null sharedInstance.

Manual integration options

You can also integrate our tvOS SDK manually - simply grab the Framework from our Public Repository and initialize Braze as outlined in the preceding sections.

Identifying users and reporting analytics

See our iOS documentation for information about setting user ids, logging custom events, setting user attributes. We also recommend familiarizing yourself with our event naming conventions.

New Stuff!