Audiencelab + your MMP
Keep the reporting layer. Add the learning loop.
Your MMP (mobile measurement partner) keeps measurement and governance consistent. Audiencelab connects campaign and creative context to approved outcomes, then turns that learning into stronger signals and better next decisions.
Signal engineering means choosing the post-install events and value signals that best reflect the outcome an ad platform should optimize for.
Bring your MMP or warehouse setup. We'll map a data path and pilot scope.
Your MMP
Measure & govern
Audiencelab
Learn & activate
Together
Stable reporting. Faster optimization.
MMP measures and governs. Audiencelab learns and activates. Both feed the next campaign decision.
Published, case-specific performance evidence.
In its Nanobit case study involving Audiencelab by Geeklab, TikTok for Business reported $1.13 CPI, 2.08 total ROAS, and 1.68 day-7 ROAS. TikTok names advanced signal engineering as one of two key performance drivers and says combining purchase and ad-revenue data produced a more comprehensive optimization signal. Creator strategy was the other named driver. Case-specific; not a guarantee. Read the case study (opens in a new tab)
How the stack works
From governed data to a better next campaign.
Audiencelab connects approved outcomes to creative learning and supported network activation while your MMP keeps reporting and governance consistent.
- 01
Govern
Your MMP
Attribution rules, reporting continuity, and partner governance.
- 02
Authorize
App or warehouse
Retention, revenue, and events your team can authorize.
- 03
Learn
Capture campaign and creative context
Source, campaign, audience, and creative.
- 04
Learn
Join approved post-install outcomes
Retention, revenue, and other outcomes you authorize from app, MMP, warehouse, or S2S.
- 05
Learn
Learn what drives valuable users
Compare creatives and campaigns on outcomes that matter, not only metrics that arrive first.
- 06
Activate
Improve signals & ad platforms
Send clearer value signals and apply learning to the next campaign.
Decision detail
Distinct jobs. One operating loop.
Keep the MMP for trusted reporting continuity. Add Audiencelab to learn faster and improve what happens next.
Your MMP
Attribute installs and events, standardize reporting, and govern partner data across the media mix.
Audiencelab
Run web-to-app campaigns, connect creative outcomes, engineer signals, and activate supported networks.
Together
The MMP stays the official report. Audiencelab improves what the team and ad networks can do next.
Connect through the path you can approve.
The right route depends on data access, consent, networks, and your reporting setup.
01
App SDK
Direct path in iOS or Android for campaign context and selected post-install events.
02
MMP or warehouse data
Approved exports or warehouse tables. No new SDK is required in some setups.
03
Server-to-server or API
When that fits your architecture and controls better.
Coverage and maturity vary by source, MMP, network, consent state, and implementation path. When numbers differ, reconcile definitions, windows, identifiers, cohort maturity, and raw events. Keep the MMP as the formal reporting source for governance.
Web-first mobile path
SKAN-independent inside Audiencelab. Compatible with the rest of your stack.
- Audiencelab path
- The current web-first measurement and activation path does not use or depend on SKAdNetwork, so SKAN conversion-value and postback operations are not part of the Audiencelab workflow.
- When an MMP is used
- Your MMP can continue using SKAdNetwork, AdAttributionKit, or other Apple-supported measurement where it belongs in your reporting stack.
- Policy boundary
- The Audiencelab SDK does not invoke Apple required-reason APIs and therefore adds no required-reason API declaration of its own. In Unity, the Unity runtime owns and declares its `PlayerPrefs` use. Other customer code and embedded SDKs remain responsible for their own applicable declarations.
Review Apple's official guidance on ATT and tracking and required-reason API declarations.
Common questions
What teams ask before adding another layer.
Does Audiencelab replace our MMP?
No. This page is designed for teams keeping their MMP. The MMP remains the reporting and governance source while Audiencelab adds creative learning, web-to-app workflows, signal engineering, and campaign activation.
Can we deploy without another SDK?
Sometimes. You can use approved MMP exports, warehouse data, server-to-server events, or APIs, depending on setup, consent, networks, and reporting needs.
How does data reach Audiencelab?
App SDK, approved MMP or warehouse data, or server-to-server/API. The right path depends on your data access, consent, networks, and reporting setup. Maturity varies by source and network.
What happens when sources disagree?
Definitions, identifiers, windows, and rules can differ. Keep the MMP as the formal reporting source, then investigate gaps using definitions, windows, identifiers, cohort maturity, and raw events.
Which MMPs or data stacks can it coexist with?
Established MMP and warehouse stacks. Integration maturity varies. Review your MMP, networks, events, consent, and reporting needs with our team before assuming a path is fully mature.
Does aggregate coverage make reporting more accurate?
It improves the learning view. Eligible aggregate outcomes extend analysis beyond an IDFA-only or ATT-opted-in cohort. Your MMP remains the formal report, while Audiencelab uses broader eligible coverage to build more useful network signals. Accuracy still depends on source quality, definitions, deduplication, windows, and implementation.
Does Audiencelab depend on SKAdNetwork?
No. Audiencelab's current web-first measurement and activation path does not use or depend on SKAdNetwork. Your MMP can still use SKAdNetwork, AdAttributionKit, or other Apple-supported measurement in the reporting stack.
Does the Audiencelab SDK need a required-reason API declaration?
No additional declaration is required for the Audiencelab SDK itself because it does not invoke Apple's required-reason APIs. In a Unity integration, Unity owns and declares the PlayerPrefs/UserDefaults access. The customer must still review its own code and every other embedded SDK for their separate manifest, ATT, disclosure, and legal obligations.
Map the combined stack
Keep reporting continuity. Add a faster learning loop.
In 30 minutes, we'll review your MMP or warehouse setup, recommend a data path, and define a pilot scope. Your official reporting stays in place.