About

Alexey Drabovich

10+ years working at the intersection of paid growth, marketing analytics, and decision systems for apps and games.


Background

What I've worked on

Across subscription apps, gaming, and performance marketing — consistently at the boundary between data and decisions.

📈
Predictive LTV & cohort modeling Building LTV models that inform budget decisions — not just report on them
🎯
Paid UA & budget decision logic Scale, hold, cut, protect — making these decisions consistently and on the right signals
⚙️
UA automation & recommendation systems Designing the decision logic layer before automation is built on top of it
🔍
Attribution & measurement MMP, SKAN, incrementality, and how to know which source of truth to trust
🛡️
Fraud & low-quality traffic Detecting signals that distort UA economics and pollute decision data
📊
Game & app growth analytics Subscription flows, trial quality, renewal signals, and marginal cohort value
Focus

Why UA Decision Systems

AI agents can now access ad accounts, move budgets, and execute campaign changes. That's not a future scenario — it's already happening. The risk isn't that AI is bad at optimization. The risk is that it optimizes faster than humans can catch problems.

The gap I keep seeing isn't in the tooling. It's that the decision logic behind UA — when to scale, hold, cut, investigate, or wait — is usually informal. It lives in a UA manager's head, not in a validated ruleset. That makes automation fragile: recommendation systems inherit undocumented assumptions, and agents act on immature signals.

My focus is on the layer between data and action: signal rights, trust checks, decision trees, guardrails, and human approval workflows. The infrastructure that makes automation safe and useful — not just fast.

Most of my work sits in the uncomfortable middle: the data is available, the team has experience, but the actual budget logic is still partly implicit. My job is to make that logic explicit enough to validate, automate, and improve.

Positioning

What this is — and isn't

Not this
"Connect Claude to your Ads account"
"AI will manage your campaigns"
Another AI dashboard or BI layer
Hype-first automation without safety
This
Formalize how your team actually makes UA decisions
Define signal rights before agents touch the budget
Build decision trees that can be validated and automated
Create guardrails and approval workflows that protect you at scale

Let's talk

If you're building UA automation, recommendation systems, or connecting AI to your ad stack — and you want to make sure the decision logic is solid first — reach out on LinkedIn.

Message on LinkedIn Take the scorecard