Optimize mobile acquisition for the outcomes your app needs

## Overview

1. 01Business models need different signals

   A subscription trial, marketplace order, retained reader, and in-app purchase have different timing and value. Event design should follow the product's economics rather than a generic template.

2. 02Creative insight needs cohort maturity

   Use the shortest window that supports a reliable business decision, then compare it with later outcomes to detect drift.

3. 03Keep implementation proportional

   Start with one network, one market, and one outcome. Expand only after event quality and the operating workflow are proven.

## Process

1. Map the acquisition funnel and business outcome
2. Select approved source events
3. Connect campaign and creative context
4. Validate delivery and reporting definitions
5. Scale the workflow after a measured pilot

## Requirements

What needs to be true for this approach to apply.

• A documented funnel and economic outcome
• Approved app, server, analytics, MMP, or warehouse access
• Network account and event configuration
• A privacy, security, and measurement review

## Limitations

What this page does not prove or guarantee.

• Long conversion windows can delay campaign learning.
• Subscription and marketplace value may require refunds, renewals, or margin adjustments.
• Network optimization and internal reporting may use different definitions.

## Questions

Which app business models are supported?

Audiencelab is designed for mobile apps and games. Fit depends on event volume, data access, network support, and the outcome a team wants to improve.

Can server-side events be used?

Yes, server-to-server integration is one supported path; exact implementation details are documented and scoped per setup.

Do I need a new SDK?

Audiencelab offers SDK and server-to-server paths. The minimum required integration depends on the available data and campaign workflow.