Braze Multi-App Key Support Beta

You can now configure platform-specific App Identifier Keys for iOS, Android, and Web within a single Braze destination. The RudderStack SDK automatically selects the appropriate key based on the device/platform type at runtime, falling back to the Default App Key if a platform-specific key is not provided.

This feature is currently in Beta and behind a feature flag. It is expected to be generally available by March 31, 2026.

Contact RudderStack Support to enable this feature for your account.

For setup instructions, see the Braze destination documentation.

Why we built this

Braze recommends using separate App Identifier Keys for each platform to ensure proper data attribution and analytics segmentation. Previously, RudderStack only supported one App Key per Braze destination, which meant customers with multi-platform apps (iOS and Android) needed to create separate Braze destinations for each platform.

This was especially problematic for teams using cross-platform frameworks like React Native or Flutter, where RudderStack treats these as single sources but Braze requires separate app keys for each underlying platform.

With Multi-App Key Support, you can consolidate your setup into a single Braze destination while still following Braze’s recommended configuration.

Key features

• Platform-specific keys: Configure separate App Identifier Keys for Android, iOS, and Web within one destination
• Automatic routing: The RudderStack SDK detects the platform at runtime and routes events to the correct Braze app
• Cross-platform support: Works seamlessly with React Native and Flutter sources
• Backward compatible: Existing configurations with only the Default App Key continue to work without changes

How to use it

1. Navigate to your Braze destination settings in the RudderStack dashboard
2. Enable the Enable Platform-Specific App Identifier Keys toggle
3. Enter the App Identifier Keys from your Braze dashboard for each platform (Android, iOS, Web)
4. The Default App Identifier Key serves as a fallback for any platform without a specific key configured

This feature applies only to device mode connections. Cloud mode connections do not use App Identifier Keys.

SDK upgrade required

To use platform-specific keys, upgrade your device mode SDK to the minimum supported versions:

If you keep the Default App Identifier Key configured, older SDK versions will continue to work using the default key.

Resources

See the following guides for detailed instructions on using this feature:

• Braze Destination Setup Guide
• Use platform-specific Braze App Identifier keys
  

Questions? Contact us by Email or on Slack