The remote commands module that wraps the Branch methods
Either the JSON configuration file or Remote Command tag that translates event tracking into native Branch calls
Adding the Branch remote command module to your app automatically installs and builds the required Branch libraries, without having to add vendor-specific code to your app. If you are using a dependency manager installation, there is no need to install the Branch SDK separately.
There are two remote command options: A JSON configuration file, or using iQ Tag Management to configure the mappings. A JSON configuration file is the recommended option for your vendor integration, hosted either remotely or locally within your app. If using iQ Tag Management, add the Remote Command tag for the vendor integration. Learn more about vendor integrations.
We recommend using one of the following dependency managers for installation:
If you are using the Tealium iOS (Objective-C) library, use the manual installation method. The CocoaPods and Carthage options are only available if you are using the Tealium iOS (Swift) library.
To install Branch remote commands for iOS using CocoaPods:
Remove tealium-swift and pod "Branch" if they already exist your Podfile. The dependency for tealium-swift is already included in the TealiumBranch framework.
Add the following dependency to your Podfile:
The TealiumBranch pod includes the following TealiumSwift dependencies:
If you are configuring remote commands using a JSON configuration file, refer to the following template to get started. The template includes common mappings used in a standard installation. Edit the mappings as needed.
The following Branch methods are triggered using a data mapping in the Branch Remote Command tag using the following Tealium commands:
iOS Remote Commands
iOS Remote Command
Android Remote Commands
Android Remote Command
Standard Event Names
The following standard event command names are supported with the logEvent method. When a command is sent, and all required variables are mapped and defined for the event, then the command is automatically triggered in the Branch SDK.