Skip to main content

​
What are Mobile Apps?

Mobile Apps in Bit2Connect are registered configurations for your iOS and Android applications that enable:
  • Deep Linking: Direct users to specific content within your mobile app
  • Attribution Tracking: Track app installs and user engagement from your dynamic links
  • Fallback Handling: Redirect users to app stores when your app isn’t installed
  • Reusability: Save app configurations to reuse across multiple dynamic links

​
Key Benefits

Simplified Link Creation

Save mobile app configurations once and reuse them across multiple dynamic links without re-entering details.

Consistent Attribution

Ensure consistent tracking and attribution across all links using the same mobile app configuration.

Centralized Management

Update app store URLs, bundle IDs, and other settings in one place to affect all associated links.

Platform Flexibility

Support both iOS and Android apps with platform-specific configurations and fallback handling.

​
Mobile App Types

​
iOS Apps

iOS mobile apps require:
  • Bundle ID: Your app’s unique identifier (e.g., com.yourcompany.yourapp)
  • App Store Fallback: URL to your app in the App Store
  • App Store ID: Numeric ID from the App Store (optional)
  • Minimum Version: Minimum iOS version required (optional)

​
Android Apps

Android mobile apps require:
  • Package Name: Your app’s package identifier (e.g., com.yourcompany.yourapp)
  • Play Store Fallback: URL to your app in the Google Play Store
  • Minimum Version: Minimum Android API level required (optional)

​
Usage Patterns

​
1. Using Saved Mobile Apps

When creating dynamic links, you can reference saved mobile apps by their ID: 
{
  "payload": {
    "link": "https://yourapp.com/content",
    "iosAppId": "550e8400-e29b-41d4-a716-446655440000",
    "androidAppId": "550e8400-e29b-41d4-a716-446655440001"
  }
}

​
2. Manual Configuration

You can also configure mobile app settings directly in the link payload: 
{
  "payload": {
    "link": "https://yourapp.com/content",
    "ios": {
      "bundleId": "com.yourcompany.yourapp",
      "app_store_fallback": "https://apps.apple.com/app/id123456789"
    },
    "android": {
      "package": "com.yourcompany.yourapp",
      "store_fallback": "https://play.google.com/store/apps/details?id=com.yourcompany.yourapp"
    }
  }
}

​
3. Save While Creating

You can save mobile app configurations while creating links for future reuse: 
{
  "payload": {
    "link": "https://yourapp.com/content",
    "ios": {
      "bundleId": "com.yourcompany.yourapp",
      "app_store_fallback": "https://apps.apple.com/app/id123456789",
      "saveApp": true,
      "appName": "My iOS App"
    }
  }
}

​
Best Practices

Reuse Mobile Apps: Create mobile app configurations once and reuse them across multiple links to maintain consistency and simplify management.
Bundle ID Accuracy: Ensure your bundle IDs and package names exactly match your published apps to enable proper deep linking.
Fallback URLs: Always provide fallback URLs to app stores so users without your app installed can still access your content.

​
Next Steps