01
Keep data and decisions scoped to the app.
Connections, revenue sources, targets, and action history remain attached to the relevant app rather than becoming one undifferentiated workspace.
For app studios and agencies
Use one operating model across a portfolio of Apple Ads accounts.
Give each app its own data boundary, revenue context, goals, and guardrails while standardizing the repetitive work your team performs every week.
Lily Ads
Scoped connectionSummarize material changes across the portfolio without mixing client data.
Five app-scoped briefs are ready. Two accounts need budget review; no cross-app data was included in the client views.
Scope
App by app
Workflow
Repeatable
Review
Client-safe
02
Reuse the workflow, not the assumptions.
Standardize account checks, reporting formats, and campaign build steps while preserving different economics, markets, and approval rules per client.
03
Increase account capacity without hiding the work.
Lily prepares analysis and operations with receipts: inputs, rationale, proposed changes, and approval state remain available for internal or client review.
How it works
A clear path from connection to decision.
- 01
Map apps and stakeholders
Define which accounts, revenue sources, and reviewers belong to each app.
- 02
Create reusable review standards
Agree on reporting windows, minimum data, and escalation rules.
- 03
Add automation by account
Apply Autopilot only where objectives and guardrails are explicit.
Questions
Before you connect
Can client accounts have different rules?
Yes. The operating scope, targets, revenue source, and automation boundaries should be configured per app and account.
Does Lily pool client data?
Client-facing analysis should remain app-scoped. Portfolio summaries can be produced only from the accounts and fields deliberately included in that workflow.
Is portfolio pricing self-serve?
Self-serve plans cover defined app and usage limits. Larger portfolios should contact Lily to align access, support, and operating requirements.