New on Apptrove: A Flexible Dynamic Link Plan for Firebase Migrators
The deprecation of Firebase Dynamic Links has left a pretty clear and immediate gap for many different teams.
Some teams have a straightforward need, like a reliable deep-linking solution to create and manage deep links without adding complexity, while others also require deep linking to enhance their performance visibility and thus see the replacement of Firebase as an opportunity to gain more insight into user behavior and installs.
In both situations, there is a need that is not for a one-size-fits-all solution, but for flexibility.
Through the Dynamic Link Plan, Apptrove introduces a more flexible approach to deep linking. Teams can use Apptrove solely to create and route Unilinks, or they can extend their use of Apptrove to include reporting and attribution, as per their team’s needs.
Let’s Understand the Shift
Firebase Dynamic Links was widely adopted because it solved a focused problem: deep linking without operational overhead.
Its deprecation has surfaced two distinct use cases:
- Teams that want to retain deep linking with performance visibility
- Teams that require only link generation and routing, often through APIs
Most platforms tend to bundle these needs together. In practice, however, they serve very different workflows.
This release is designed to separate them.With the Dynamic Link Plan, Apptrove introduces a more adaptable approach to deep linking. Teams can now use Apptrove purely for Unilink creation and routing, or extend it to include reporting and attribution, depending on their requirements.
Two Distinct Ways to Use Dynamic Links on Apptrove
1. Unilinks with Reporting (Limited Panel Access)
This mode is intended for teams that want to combine deep linking with a layer of performance insight, without adopting a full MMP setup.
Users can access a focused set of modules, including reporting, logs, Unilink management, and link analysis. Attribution remains active, which means installs and events are processed and available for analysis.
This approach provides a balance. Teams gain visibility into how their links perform, while avoiding the complexity of navigating the full platform.
It is particularly relevant for teams that previously relied on Firebase and now want a more structured view of performance without significantly expanding their stack.
2. Unilinks via API Only (No Attribution, No Dashboard)
For teams that use deep linking strictly as infrastructure, a lighter approach is often more appropriate.
In this mode, Apptrove functions as a dedicated link management layer. Users can generate and manage Unilinks through APIs or a minimal panel interface, without accessing dashboards, reports, or attribution features.
The SDK, where used, supports redirection but does not process installs or in-app events. Attribution pipelines are bypassed entirely.
This is particularly suited to backend-driven environments, where deep linking is integrated into broader systems and analytics is handled separately.
A More Intentional Product Experience
One of the core changes in this release is how the platform adapts to different user needs.
Instead of exposing the entire product by default, access is now structured based on the selected usage mode. Teams working with reporting see only the modules relevant to analysis and link management. Teams focused on infrastructure are presented with a minimal interface centered on Unilinks.
This reduces unnecessary complexity and shortens the path from setup to value.
Billing That Reflects Usage, Not Assumptions
A significant part of this update lies in how dynamic link usage is priced.
Unilink with Reporting
Billing remains aligned with the existing model, based on non-organic installs. This ensures continuity for teams already familiar with attribution-based pricing.
Unilink-Only Usage (No Attribution)
A new billing construct that has been introduced is Dynamic Link Quota. This is a contract-based model rather than a usage-based one. It represents a predefined cost for dynamic link usage, independent of traffic or install volume.
When this model is applied:
- Attribution is disabled
- Install-based billing is removed
- Pricing remains predictable and consistent
This structure is particularly valuable for teams that want clarity and control over costs, without variability tied to usage spikes.
Designed for Migration Without Friction
Deep linking is often treated as a supporting capability, but it plays a central role in how users move across platforms and experiences.
When it is reliable, it goes unnoticed. When it fails, the impact is immediate.
The Dynamic Link Plan is designed to keep this layer stable, flexible, and aligned with how teams actually work, whether they need a lightweight solution or a more insight-driven approach.For teams transitioning from Firebase Dynamic Links, the priority is continuity.
This release is designed to ensure that:
- Deep linking workflows remain uninterrupted
- Teams can choose the level of functionality they actually need
- Onboarding does not require unnecessary configuration
- Existing systems can integrate without disruption
Rather than forcing a shift in how teams operate, the platform adapts to existing workflows and gradually extends them where needed.
Getting Started
The Dynamic Link Plan can be enabled during account setup or configured for existing accounts through Apptrove.
Once enabled, the platform experience and billing structure adjust automatically based on the selected mode.
Want a closer look at how the Dynamic Link Plan works? Explore the full setup, access modes, and implementation details in the Apptrove Knowledge Base.
from Apptrove https://apptrove.com/new-on-apptrove-dynamic-link-plan-for-migrators/
via Apptrove
Comments
Post a Comment