Fallback

What is Fallback?

Fallback is a contingency mechanism in mobile marketing that activates an alternative path, destination, or tracking method when the primary strategy fails or is unavailable. Fallback configurations ensure that tracking links, deep links, ad delivery, and attribution flows continue functioning even when expected conditions, such as app installation, specific device support, or data availability, are not met. By defining fallback behavior in advance, marketers prevent broken user experiences and gaps in campaign measurement.

How it works

Fallback mechanisms operate by detecting when a primary action cannot be completed and automatically redirecting users or switching data collection methods to a predefined alternative.

Fallback in Deep Linking

When a deep link attempts to open a specific in-app screen, it first checks whether the app is installed. If the app is not present, the fallback path redirects the user to the App Store, Google Play Store, or a designated web page. Deferred deep linking extends this by storing the intended destination and routing the user there after install. Without a properly configured fallback, users who do not have the app installed encounter a broken experience with no recovery path.

Fallback in Ad Delivery

When a primary ad format fails to load due to network issues, format incompatibility, or inventory shortfalls, a fallback ad of a different format or lower priority is served instead. This prevents wasted impression opportunities and maintains fill rates across publisher placements.

Fallback in Attribution and Tracking

As privacy regulations and platform restrictions limit traditional identifier-based tracking, fallback attribution methods come into play. When device identifiers such as IDFA or GAID are unavailable, attribution platforms apply probabilistic modeling or aggregated measurement approaches as fallback signals. Server-to-server tracking can also serve as a fallback when client-side SDK tracking is blocked or restricted.

Configuring Fallback URLs in Tracking Links

When creating tracking links, marketers define fallback URLs for scenarios where the primary destination is unreachable. Airbridge's dashboard allows users to configure custom fallback paths directly within tracking link settings, specifying different destinations based on device type, OS version, or app installation status. This ensures campaigns route users appropriately regardless of their device state.

Why it matters

Fallback configurations are fundamental to maintaining campaign continuity and attribution integrity. Without them, users who encounter a failed deep link or unsupported ad format are left with a broken experience, increasing the likelihood of abandonment and reducing the effectiveness of ad spend. In attribution, missing fallback logic creates data gaps that distort conversion tracking, making it harder to evaluate which campaigns and channels are truly performing. As mobile ecosystems become more fragmented across operating systems, privacy frameworks, and device types, fallback strategies become increasingly important for ensuring consistent measurement and user engagement across all conditions. Properly configured fallbacks also reduce reliance on any single tracking method, making attribution pipelines more resilient to regulatory changes and platform updates.

How to set up fallback in mobile tracking links

Setting up fallback behavior in mobile tracking links requires defining what happens at each failure point before a campaign goes live.

Step 1: Identify failure scenarios. Map out the conditions where the primary path may fail. Common scenarios include users who do not have the app installed, users on unsupported OS versions, and users on desktop browsers where the mobile app is unavailable.

Step 2: Define fallback destinations. For each failure scenario, assign a specific fallback URL. Typical destinations include the App Store or Google Play listing, a mobile web landing page that mirrors the in-app experience, or a generic campaign page with a download prompt.

Step 3: Configure fallback paths in your MMP. Within Airbridge's tracking link dashboard, input fallback URLs for each relevant scenario. You can set separate fallbacks for iOS, Android, and desktop traffic, as well as for cases where the app is detected as not installed.

Step 4: Test each fallback path. Before launching, simulate the failure conditions by testing links on devices without the app installed and on unsupported platforms. Verify that each fallback destination loads correctly and that attribution data is still captured.

Step 5: Monitor fallback activation rates. After launch, track how frequently each fallback path is triggered. High fallback rates on specific device segments indicate a targeting or creative compatibility issue worth addressing upstream.

Related concepts