Distribute and grow
Distribute and grow

Multi-team bundles

Updated: Jan 5, 2026
You can cross-market your apps and IAP with that of other developer teams by creating a joint venture known as Multi-team bundles (MTB). One team creates the initial MTB, and then shares an invite code. Each invited team can then contribute their own items to the MTB.
Multi-team bundles are a great way to drive additional revenue through creative cross-team collaborations that bring in new audiences to your apps.

Eligibility and guidelines

Anyone in your organization can create or join a bundle as long as they meet the following criteria:
  • An active developer account on the Meta Horizon platform
  • At least one published app
  • In order to perform any of these tasks, you must be an administrator for your organization

Getting started

The MTB feature assumes that a partnership among organizations has already been established off-platform as the feature does not contain a way to communicate with other organizations. Start by aligning on details such as payout ratios, assets, and pricing via email or other channels before creating a bundle to streamline the configuration steps.
MTBs have separate user flows for creators and invitees. A creator is responsible for populating the bundle’s details, including payout ratios, assets, and pricing, and for submitting the bundle for Meta approval. Invitees are responsible for populating the bundle with apps and IAP items from their own organization, and for approving the final bundle configuration before it’s sent to Meta for approval.
Bundle creators
  1. Log in to the Developer Dashboard
  2. Navigate to Growth > Bundles
    1. Click the Multi-team bundle tab and then click Create multi-team bundle.
  3. Copy and share the bundle invite code with other developer organizations that you want to invite to this bundle
Bundle invitees
  1. Log in to the Developer Dashboard.
  2. Navigate to Growth > Bundles
  3. Click the Multi-team bundle tab and then click Join existing bundle.

Bundle phases

Because this feature requires coordination among different organizations, we’ve outlined the important phases:
  1. Create bundle - The bundle creator creates the bundle and shares the invite code to enable other bundle participants to join the bundle.
  2. Configure bundle details - Both the creator and bundle invitees work together to fill out the bundle details. Bundle invitees are responsible for adding the apps and items from their organization into the bundle. The bundle creator is responsible for configuring all other bundle details such as payout ratios, assets, pricing, and dates.
  3. Approve bundle details - Once bundle details have been filled out, all bundle participants must approve the bundle before it can be submitted to Meta for approval.
  4. Submit bundle for Meta review - Meta will review the bundle assets and details according to the existing Store policies and approve or reject the submission.
  5. Publish bundle - Once Meta has approved the bundle, the bundle will be published according to the start and end date specified in the bundle.

Key features

Keep the following key features in mind when creating and managing multi-team bundles:

Bundle creation and collaboration

  • Flexible invite system: Developers can invite other organizations to join a bundle by generating and sharing invite codes.
  • Comprehensive bundle configuration: Bundle participants can select specific app items (apps, IAPs) from their organization. Bundle creators can control all aspects of a bundle, including descriptions, assets, and pricing.
  • Clear collaboration model: Bundle creators and participants have different roles and permissions to facilitate faster bundle creation.

Permissions and control

  • Controls on data sharing: Bundle participants must manually add in apps and items from their organization; no information is automatically shared between organizations.
  • Joint approval: All participants must approve the bundle before it’s submitted for Meta review.
  • Ending a bundle: Any participant can end a published bundle prior to the scheduled end date.

Analytics

  • Bundle revenue: Track revenue generated from the bundle
  • Bundle impressions: Monitor how many users are viewing your bundle

Best practices

  • Forge strategic partnerships: Focus on creating bundles with complementary apps to drive additional sales and improve store discoverability for all included content. The bundle should make sense to your target audience.
  • Maintain clear communication: Bundle configuration occurs asynchronously, meaning participants might not be immediately aware of changes. Establish clear communication channels and practices with your organizations to ensure smooth coordination.
  • Cross-marketing opportunity: Do not rely solely on Meta to promote bundles on your behalf. All bundle participants should promote the bundle to their users on social media and other channels.
Did you find this page helpful?