Back to Glossary

App Bundle ID

i

A unique string that identifies your app across Apple's and Google's ecosystems. It's essentially your app's digital fingerprint in the stores.

Why the App Bundle ID Matters for Mobile Marketing

For mobile marketers, app developers, and attribution specialists, the App Bundle ID is not just a technical detail—it’s a critical piece of infrastructure that enables:

1. Accurate Mobile Attribution

Mobile Measurement Partners (MMPs) like Affise MMP use the Bundle ID to correctly identify which app is being installed, launched, or generating in-app events. Without a correctly configured Bundle ID, attribution data becomes unreliable or unusable.

2. SDK Integration

When integrating an MMP SDK into your app, the Bundle ID must match exactly what you’ve registered in your MMP dashboard. Any mismatch will break the data flow and prevent proper tracking.

3. App Store and Play Store Linking

Your Bundle ID connects your app to its store listing. Affise MMP uses this identifier to automatically pull app information—including name, logo, and description—directly from the app store.

4. Partner and Ad Network Integration

When setting up campaigns with advertising partners (Meta, Google Ads, Unity Ads, etc.), the Bundle ID ensures that traffic is attributed to the correct app.


Bundle ID vs. App ID: What’s the Difference?

These terms are often used interchangeably, but they refer to slightly different things:

Term Platform Description
Bundle ID iOS / Apple Reverse-DNS identifier (e.g., com.company.app) set in Xcode
Package Name Android / Google The unique identifier for an Android app (e.g., com.company.app)
App ID Affise MMP The internal system ID that Affise assigns to your app in its database

For practical purposes in mobile marketing, Bundle IDPackage Name, and Application ID all refer to the same concept: the unique identifier for your app.


How to Find Your App Bundle ID

For iOS Apps

  • In Xcode: Open your project → select the target → go to the Signing & Capabilities pane → look for the Bundle Identifier field

  • In App Store Connect: Navigate to My Apps → select your app → the Bundle ID is listed in the App Information section

  • In the App Store URL: The Bundle ID is not the numeric App Store ID—it’s a reverse-DNS string, not the number after id= in the URL

For Android Apps

  • In Android Studio: Check the applicationId in your build.gradle file

  • In the Google Play Console: Navigate to your app → the Package Name is displayed in the app details

  • In the Google Play URL: Look for the string after id= in the Play Store URL (e.g., id=com.company.app)


How Affise MMP Uses the App Bundle ID

In Affise MMP, the App Bundle ID (referred to as Package Name / ID) is a required field when adding a new application to track.

Adding an App in Affise MMP

  1. Navigate to Applications and click Add new application

  2. Select your app’s store: Play Market, Appstore, Telegram, or Alternative Market

  3. Fill in the required fields:

    • App link: The URL to your app in the store

    • Package name / ID: Your app’s Bundle ID / Package Name

    • Logo: Upload your app icon (max 5 MB)

    • Application name: The name of your app

    • Timezone and Currency: For accurate reporting

Pro Tip: When you add a valid app store link, Affise MMP automatically pulls the ID, logo, app name, and description from the store—saving you time and ensuring accuracy.

Where to Find the Bundle ID in Affise MMP

Once your app is added, you can view its details in the Applications list under Attribution > Applications. Key columns include:

  • App ID: The internal Affise system ID for your app

  • Application: Your app name and logo

  • OS: The operating system of your app

  • Store link: Direct link to your app’s store listing

Clicking on an app opens the Application Overview, where you can view detailed information including the OS, store, version, and App ID.


Common Use Cases in Affise MMP

1. SDK Integration

When integrating the Affise SDK into your app, you’ll need to initialize it with your app’s keys and IDs—including the Bundle ID. This ensures that all installs and events are correctly attributed to your app.

2. Partner Tracking Links

When setting up partner tracking links, partners need to include the correct Bundle ID to ensure their traffic is attributed to your app.

3. Postback Configuration

Postback URLs in Affise MMP rely on correct app identification. Each app has its own postback settings, and the Bundle ID ensures that conversion data goes to the right place.

4. Cross-Platform Tracking

If you have separate iOS and Android versions of your app, each will have its own Bundle ID / Package Name. Affise MMP allows you to manage both within a single dashboard.


Best Practices for Managing App Bundle IDs

✅ DO:

  • Choose a consistent naming convention using reverse-DNS format (e.g., com.company.appname)

  • Verify the Bundle ID matches across your Xcode project, App Store Connect, and Affise MMP

  • Document all Bundle IDs for your apps in a central location

  • Use the same Bundle ID for all environments (development, staging, production) when possible—or clearly differentiate them

❌ DON’T:

  • Don’t change the Bundle ID after publishing—it’s permanent

  • Don’t use special characters or spaces in your Bundle ID

  • Don’t confuse the Bundle ID with the App Store ID (numeric) or Affise App ID (system-generated)