MMP coexistence
Keep AppsFlyer. Add a workflow for learning and activation.
Audiencelab can complement AppsFlyer. AppsFlyer can remain the attribution, reporting, and governance layer while Audiencelab supports web-to-app campaigns, creative-level outcome analysis, and signal engineering. The exact connection depends on approved exports, APIs, server events, SDKs, or warehouse data available to the customer.
Overview
01AppsFlyer's job
Preserve existing attribution, cross-network reporting, governance, and downstream dashboards. Do not change the source of record without a deliberate migration decision.
02Audiencelab's job
Connect measurement to campaign action through web-to-app workflows, creative analysis, event design, and supported network feedback.
03Reconcile, do not declare a winner
When totals differ, compare windows, time zones, attribution rules, identifiers, currency, cohort maturity, and raw source events.
Process
- Document how AppsFlyer is used today
- Choose the approved data handoff
- Map definitions and expected discrepancies
- Run both views during a pilot
- Assign ownership for ongoing reconciliation
Different layers, different responsibilities
| Job | AppsFlyer | Audiencelab |
|---|---|---|
| Cross-network attribution | Primary | Uses approved outputs where available |
| Reporting governance | Primary | Complementary |
| Web-to-app workflow | Configuration dependent | Primary focus |
| Signal and creative activation | Platform dependent | Primary focus |
Requirements
What needs to be true for this approach to apply.
- Access to the required AppsFlyer data or export
- Documented attribution settings and windows
- Approved destination and retention controls
- A clear operational use case beyond duplicate reporting
Limitations
What this page does not prove or guarantee.
- Available AppsFlyer connection methods depend on customer configuration and permissions.
- The systems may report different totals for valid methodological reasons.
- Audiencelab should not be described as a native integration until the specific path is confirmed.
Questions
- Do I need to remove AppsFlyer?
- No. The default positioning is coexistence, not rip-and-replace.
- How is data connected?
- Depending on the approved setup, options may include exports, APIs, SDK or server events, and warehouse data. Confirm the exact path before implementation.
- Which system is the source of truth?
- The customer should declare a source of record for each reporting and operational decision. No system should be treated as automatic truth for every purpose.