Why Meta Ads Manager and Airbridge Show Different Install Numbers

Learn why Airbridge and ad-platform reports show different install counts, how attribution windows and duplicate events create gaps, and how to reconcile them.

Airbridge6 min read
Why Meta Ads Manager and Airbridge Show Different Install Numbers

Key Takeaway

  • Meta Ads Manager and Airbridge report different conversion numbers because each platform configures attribution windows and classifies events under its own rules.
  • Meta credits itself whenever a user interacts with a Meta ad in the attribution window, while Airbridge evaluates touchpoints across multiple channels to assign a single winning touchpoint.
  • Leaving event logging active in the Meta SDK alongside Airbridge postbacks can duplicate conversion counts in Meta Ads Manager.

You launch a new campaign for your subscription app, spend your weekend budget, and open two browser tabs on Monday morning to see what worked. In one tab, Meta Ads Manager shows a spike in installs and trials. In the other, your attribution dashboard reports a noticeably smaller number for that exact same campaign. When you are wearing five hats and managing every dollar of ad spend yourself, seeing two different sets of numbers makes it hard to know whether to scale the campaign or pause it. The two dashboards apply different attribution rules based on how they define and configure attribution windows and classify events.

Primary causes of number gaps

Conversion counts diverge between the two platforms primarily because Meta and Airbridge apply different attribution window configurations and event classification logic. Beyond attribution modeling, four technical and timing mechanisms create gaps when you compare dashboards side by side:

  • Reporting latency: Airbridge generally shows conversion events on its dashboard in real time, whereas Meta receives conversion data via postbacks and can take several hours to display those events in Meta Ads Manager.
  • Duplicate event logging: If you have the Meta SDK installed in your app and do not disable its native event logging, events can be duplicated, creating discrepancies between Airbridge and Meta Ads.
  • SKAdNetwork (SKAN) mapping and sync schedules: On iOS, Airbridge pulls the past 7 days of SKAN data from self-attributing networks (SANs) and updates its reports daily at 4:00 PM UTC, which can cause differences from SAN dashboards such as Meta Ads. In addition, SKAN data can look different depending on how events measured under Airbridge's SKAN conversion-value rules map to Meta ads events. When one Airbridge event maps to one Meta ads event, both dashboards display the data the same way, but mapping several Airbridge events to a single Meta ads event can make the numbers diverge.
  • Aggregated Event Measurement (AEM) on iOS: For iOS campaigns using AEM, Meta Ads applies its own methodology to AEM attribution data while Airbridge keeps its existing attribution model. Airbridge provides Meta Ads AEM attribution data collected on or after October 10, 2024, and combining SKAN and AEM data may cause Meta Ads to report higher performance.

Attribution windows and credit rules

Even when postbacks arrive on time and SDK logging is clean, the two platforms follow fundamentally different philosophies on who gets credit for a conversion. Meta attributes a conversion to Meta when there has been any interaction with a Meta ad within the attribution window. Airbridge collects touchpoints across multiple ad channels and credits the conversion to a single winning touchpoint based on its attribution model. Because of this multi-channel view, Airbridge may attribute conversions to another ad channel that Meta claims were driven by Meta ads.

When you run ads across Google, Meta, Apple Ads, and TikTok—the four ad channels included in the Airbridge Core Plan—a user might see a video on Meta, tap a search ad on Apple Ads two days later, and install your app. Airbridge collects touchpoints from various ad channels and attributes the conversion to a winning touchpoint under its attribution model.

Under default window settings, Airbridge selects the winning touchpoint from touchpoints gathered within a 7-day lookback window from the day of a click, and uses a default attribution window of 30 days. Airbridge also separates the target event attributed to that winning touchpoint from the subsequent events that follow the touchpoint to which the target event was attributed. Meta, by contrast, uses click-through attribution windows of 1 day and 7 days alongside view-through and engaged-view windows of 1 day each, and it counts every event within the configured attribution period without distinguishing target events from subsequent events.

How touchpoints are weighted also affects which interaction wins:

  • Engaged views vs. regular views: From Meta Ads campaigns, Airbridge prioritizes engaged views over regular views. Airbridge defines an engaged view as a view followed by a conversion within 24 hours after the user either watches 5 seconds of a skippable video ad or watches at least 97% of a video ad shorter than 10 seconds.
  • Probabilistic and AEM parity: Within Airbridge, touchpoints used for probabilistic modeling attribution and touchpoints used for AEM attribution receive the same priority.

Meta event approval for postbacks

Sometimes a discrepancy happens not because of attribution windows, but because an event sent from Airbridge is placed in Action Required in Meta Events Manager.

During the Meta Ads channel integration, completing Step 1 (Facebook App ID) causes Airbridge to automatically send Install (App), Deeplink Open (App), and Deeplink Pageview (App) event data to Meta Ads. To forward mapped events, you configure Step 2 (In-App Event Postback), where mapping Airbridge events to Meta Ads events causes Airbridge to send the corresponding event data to Meta Ads.

When you start sending new events from Airbridge to Meta Ads, custom events or events containing sensitive information may be placed automatically into the Action Required status inside Meta Events Manager. While an event sits in Action Required, it will not show up in your Meta reporting until it is approved. If your Airbridge dashboard records in-app events that are completely missing from Meta Ads Manager, checking Meta Events Manager for pending approvals should be your first step.

Checklist to reconcile your data

When your numbers look too far apart to be explained by multi-touch attribution alone, walk through these steps to find and eliminate duplicate or unmapped event sources:

  1. Disable duplicate Meta SDK logging: If Meta SDK event logging is turned on for an event that Airbridge is also sending via postback, disable Meta SDK event logging to stop the event from being counted twice.
  2. Inspect the integration source in Meta Events Manager: To see where Meta Ads is pulling its aggregated events from, select your app in Events Manager > Data Sets and look at the event's Integration value; if the value says Multiple, export the data.
  3. Compare SDK and MMP counts in the exported file: Open the downloaded event data from Meta and check two columns: facebook_sdk_received_count, which shows events collected by the Meta SDK, and mmp_received_count, which shows events Airbridge sent to Meta Ads. If facebook_sdk_received_count is anything other than zero, the Meta SDK is still collecting that event alongside your postbacks.
  4. Check for overlapping measurement partners: Keep in mind that if both Airbridge and another mobile measurement partner are sending events to Meta Ads at the same time, mmp_received_count lumps them together and does not separate Airbridge's events from the other partner's events.

FAQS

FAQ

How does the Airbridge Core Plan handle subscription events and ad channel attribution?

The Airbridge Core Plan includes channel integrations for Google, Meta, Apple Ads, and TikTok, and the SDK comes with 25 preconfigured standard events, three of which are subscription events (Start Trial, Subscribe, and Unsubscribe). In the Actuals Report, you can group campaign and channel costs with subscription outcomes to track custom metrics like cost per trial or cost divided by subscriptions alongside CPI and ROAS.

What reports and features are included in the Airbridge Core Plan?

Alongside Actuals, the Airbridge Core Plan includes Trend, Active Users, Funnel, Retention, and Revenue reports, cost and ad spend aggregation, subscription revenue aggregation, Predictive LTV, and up to 2 third-party integrations such as RevenueCat, Adapty, or Amplitude.