Product-Led Growth via Real-Time Tool Adoption and Achievement Triggers
A global creator platform couldn't see user achievements across its eight seed products. We turned a passive ETL pipeline into a Product-Led Growth (PLG) engine, so specific user milestones now route directly to Customer.io and trigger context-aware expansion sequences that drove high-value paid-tier subscription upgrades.
Executive Summary
Context
A global streaming software provider needed to move users into a wider suite of eight products, aiming for paid-tier subscription conversions and lower churn.
What We Built
We built a technical event-routing pipeline that translates real-world product achievements into context-aware growth sequences across a global creator base.
Tech Stack
- Custom ETL (API-driven)
- Customer.io
- 8 seed product databases (editing, streaming, merchandise and other tools)
Not a fit if you lack internal development resources to maintain custom middleware. Single-product offerings without distinct sub-tools won't benefit either.
The Challenge
A creator could be doing well with the donation or merchandise tools while the marketing automation layer knew nothing about those milestones, because user success in the secondary seed products never reached it. Without that data parity, no one could distinguish a dormant user from a high-performing creator who was ready for an upsell into the wider product suite.
The ETL middleware is passive, so every expansion of the data schema had to be hard-coded by hand into both the source product and the ETL itself. Any update to a tool such as the streaming product therefore risked breaking the expansion triggers for the entire global audience if the API payload no longer matched the format the marketing engine expected.
Our Approach
We approached the work as intent mapping rather than data migration. Across the eight seed products we identified the success plateaus, the points at which a user's behavior showed they had outgrown their current toolset. When a podcaster reached a specific distribution milestone, for instance, the system triggered educational content for the video repurposing tools.
Those achievement events also had to be normalized across the passive ETL before they reached the lifecycle engine, so that a milestone from any of the eight products arrived in the same shape.
A mandatory onboarding questionnaire sets each user's starting persona (livestreamer, podcaster or video editor), and tool adoption data then refines it: a podcaster who starts using streaming alerts moves onto the streaming track. At year end, Liquid logic pulls each user's own figures, such as minutes streamed and viewer growth, into a Year in Review email timed to the renewal window.
This engagement is part of our growth programs work for telecommunications & media organisations.
Impact
Suite-Wide Stickiness
Sequences triggered by actual product achievements increased usage across all eight seed products, and creators moved from being single-tool users to using the suite broadly.
Milestone-Based Conversion
Achievement data (e.g., First Merch Sale) identifies the "conversion-ready" creators. Context-aware paid-tier subscription prompts then deploy during their periods of peak engagement.
Unified Achievement Data
Real-time event payloads from disparate tools now consolidate into a single user profile, giving a complete view of creator success.
Automated Growth Velocity
Product launches no longer need any manual campaign assembly. The event-driven framework automatically routes each user to the relevant educational track based on their behavior.
The database captures specific tool-usage thresholds and pushes them to the ETL as event-specific JSON payloads (e.g., MERCH_SALE_COMPLETED).
The ETL middleware acts as a validation layer. Achievement events from different products normalize into a standardized schema before publishing to the Customer.io API.
Achievement events serve as entry triggers for specialized "Exploration" flows. Each flow checks whether the user is already active in the target tool. If adoption is verified, the message gets suppressed.
The system watches for "Success Plateaus": a user highly active in free tools who hasn't converted. It then fires high-value subscription prompts highlighting the specific paid-tier features relevant to those achievements.
A creator could succeed with the donation or merchandise tools while the marketing automation layer knew nothing about it. The passive custom ETL also meant every schema change was hard-coded by hand. Now achievement events are normalized in the ETL, so a milestone from any of the eight seed products reaches Customer.io in the same shape. A podcaster reaching a distribution target, for instance, triggers the matching educational track.
FAQ
The trigger is nearly instantaneous. The custom ETL is passive and relies on "pushes" from the product database, so a "congratulations" or "next-step" email can reach the user while they're still actively engaged in the software.
Schema changes are the primary constraint of the "two-point-of-failure" architecture. If a schema changes, the ETL code must be manually updated to recognize the new payload. Product engineering and RevOps have to stay strictly synchronized to prevent trigger failures.
