Claravine + Branch

Claravine partners with Branch, an industry-leading mobile measurement and deep linking platform, so that brands can apply data standards to links built for their mobile experiences, just as they already do for other channels managed in Claravine. With our Branch integration, newly created links are enriched with all of the right data and values so consumer engagement data is clean on the way in. Marketers can create structured Branch links in bulk through our web-based spreadsheet view with the familiarity of Excel or Google Sheets.

From the Claravine platform, simply use our Branch-specific templates to enter mobile link data into preset fields. Submit your completed templates, whose data is sent to Branch; completed Branch links are then available in the Claravine platform. When your campaigns are set live in their execution platforms and consumers click on your ads or visit landing pages, Branch receives the attribution data. User event data is then sent to Adobe or Google Analytics.

Integrate Your Claravine Account With Branch

Prepare Branch to Connect With Claravine

In your Branch account, navigate to Configure → Account Settings → Profile and create a Branch Key and Branch Secret (be sure the correct Branch App is selected in the upper left).

Configure the Branch Connector in Claravine

1. In The Data Standards Platform, navigate to Settings → Integrations → Accounts, choosing Branch, then adding a name and description.
   
   
   
   
2. Scroll down to add your Branch Key and Branch Secret and add Custom Field Mappings. Custom field mappings allow you to export Claravine fields to Branch as key/value pairs. Refer to Custom Field Mapping for more details on configuring Branch custom field mappings. For a full list of Branch fields supported by our integration, consult the Supported Fields section below.
   
   
   
   
3. Ciick Save Account.

Branch Outbound Configuration

To configure the Branch integration for a template, select Branch from the list of outbound connectors and complete the configuration.

Deliver Branch Link Data (Outbound)

Configuration is similar to our Email and File-Based Outbound integrations.

Generate Branch Quicklinks

Once the template configuration is complete, you can begin a new submission to start creating Branch links in The Data Standards Cloud. When the submission is completed, new rows will be added to your dataset with a new, auto-populated Deeplink field that includes the Branch Quicklink.

Branch Alias Field Value Must Be Unique

If you map the Branch Alias field, the value you submit to that field must be unique within that Branch account. This field will become the custom back half value for the link generated (for example: www.claravine.com/custom-back-half-value). If you submit an alias value that is already taken inside of that Branch account, the submission will fail. The UI will display an error on the column that is mapped to the alias field, telling you the value is already taken.

Resubmitting or Editing a Submission Updates Mapped Branch Fields

Resubmitting or doing a selective edit on a submission will update the Branch fields that are being mapped. For example, if you have all of the utm parameter mappings set up to be mapped, resubmitting with different values for those columns will update the utm parameters inside of Branch. The exception for this is the alias field: once an alias field is set it, cannot be updated.

Supported Fields

The Branch integration supports the following Branch fields. These fields are available to map to your templates fields in the Connector configuration without the need to create custom fields:

Read more:

• Our blog on "Going Deep On Deep Linking: Mobile, Deferred, Tips & Examples"
• Claravine Product Update: Branch Integration
• Marketing Fact Pact 2021, AdAge
• The Five Mobile Advertising Trends To Watch in 2020, Forrester