Testimonial from Kip.com.au (Pet Care Services)
Testimonial from Remento (B2C consumer tech)
Testimonial from Startverge (Telehealth)
Measuring the incremental revenue impact of lifecycle messaging
Bonoxs was running lifecycle campaigns through Customer.io , but traditional metrics like opens, clicks and attributed conversions couldn’t answer the most important question:
The team needed a way to connect Customer.io message exposure for Push notifications and emails with downstream behaviour and transactions in Mixpanel, while comparing messaged users against holdout groups. I designed the measurement framework connecting , allowing Bonoxs to follow the journey from lifecycle message → user behaviour → purchase → revenue. The implementation included:
- Instrumenting Customer.io webhooks to send journey and campaign data for push notification and email exposure into Mixpanel
- Passing campaign context into Mixpanel for downstream attribution
- Measuring performance by market, channel, campaign, product, segment and message variant
- Connecting anonymous users across both platforms using their Mixpanel device ID
- Enriching anonymous profiles with Customer.io customer data.
- Building identifier fallback logic for both known and anonymous users
- Creating send vs holdout measurement to separate campaign impact from purchases that would have happened anyway
- Building Mixpanel reporting around conversion rate, revenue per recipient and incremental revenue
The result was an end-to-end measurement layer:
The framework gave Bonoxs a much clearer view of the commercial impact of lifecycle messaging.
In one 7-day reporting window:
vs — approximately
vs — approximately
More importantly, Bonoxs could now evaluate performance based on the additional revenue messaging created, rather than simply attributing every post-message purchase back to Customer.io . The question changed from:
to:
That gave the Bonoxs team a much stronger basis for deciding which campaigns, segments and variants to scale, optimise or stop.
Turning automated WhatsApp messages into two-way Intercom conversations
RunaHR used Customer.io to send automated WhatsApp messages to users. But when a user replied, the response needed to move into Intercom so the team could continue the conversation without losing the context of the original message. Customer.io and Intercom does have a native integration to handle this. I designed and built a , turning automated lifecycle messages into seamless human conversations.
The system handles the full flow:
When a user replies to a WhatsApp message, n8n finds or creates the corresponding Intercom contact, opens the reply as a conversation and adds the relevant Customer.io message as context. When an Intercom agent replies, a separate workflow routes that response through Twilio back to the user's WhatsApp.
- Built bidirectional ↔ message routing
- Automatically created and updated Intercom contacts from WhatsApp users
- Stored the user's WhatsApp number for reliable reply routing
- Preserved the Customer.io message that triggered the user's response inside Intercom
- Built message-level tracking so context is added once without being duplicated on subsequent replies
- Tracked Twilio message IDs to distinguish Customer.io-generated messages from Intercom agent replies
- Prevented non-WhatsApp Intercom conversations from being routed through Twilio
- Added safeguards and error handling across the workflows
RunaHR could keep using Customer.io for scalable lifecycle messaging while handling replies entirely from Intercom. Instead of Customer.io , WhatsApp and Intercom operating as disconnected systems, the integration created one continuous journey:
The result was a workflow where automation could start the conversation, while the customer support team could naturally take over when a user responded.
- Heros backend platform runs on Rimo Health which does not have a direct integration with Customer.io . Heros also needed to ensure that sensitive patient information are not stored in Customer.io . - I created a to receive webhooks from RimoHealth, transformed the data with a Javascript event map to ensure HIPAA compliance, then identify users and sent only relevant events and event properties needed to power the lifecycle campaigns into Customer.io
n8n workflow from RimoHealth to Customer.io
Intake Assessment Quiz for Heros
in the last 30 days
This sketch cannot currently be displayed in exports
The campaign was set up to re-engage every lead that started off on the bookings landing page but did not complete a booking. It works because;
It promptly drives reconsideration after booking abandonment.
The campaign is behavioral and hence, very timely and provides tailored content showing the value of booking a stay for your pet at Kip
It capitalizes on the immediacy of the abandonment, creating a sense of urgency.
It provides additional resources to help the customer make an informed buying decision.
It motivates action with discounts and exclusive offers for prompt action.
It's a strategic, multi-email approach for increased re-engagement.
booked at least one day stay at a Kip pet resort location
This sketch cannot currently be displayed in exports
I got this during my time working at McGaw.io
All email templates are , , and
Patient Reorder Reminder Flow
I built this into a master template and modular resuable components
Using dynamic liquid to pull in customer order data and images
I built this into a master template and modular components
I designed this transactional template for Shopra that relies on data from their database delivered via API to trigger the email.Email template was designed from scratch and full optimized for all inboxes (Gmail, Outlook, Apple mail), fully responsive and darkmode optimized.
UXCam's mobile app analytics solution is mostly used by Product Managers but requires installing a mobile SDK by developers before product teams can start collecting user behavior data to derive value from the solution.
Product managers were signing up for UXCam, and delays in SDK installation meant not only longer time to value but also decreased perceived value by product managers, leading to churn.
UXCam aimed to increase its mobile SDK installation rate, a critical step in the user journey that allows product managers to access user behavior data for analytics purposes.
: The percentage of new sign-ups that successfully install the mobile SDK. This is the primary metric for success.
: The average time between a user signing up for UXCam and the SDK being installed. The goal is to reduce this time.
: The rate at which new users open, read, and take action based on the onboarding emails. This indicates the effectiveness of the email campaigns.
: The percentage of those who installed the SDK and became paying customers.
To solve this issue, I implemented a targeted three-step email onboarding sequence.
- Sent 1 hour after signup: This email outlined the value of the SDK installation, why it was necessary, and provided simple, step-by-step instructions on how to perform the installation for different mobile app development frameworks.
- Sent 2 days after signup if SDK was not installed: This email provided additional support and recommendations to pass on to their developers, addressing common installation issues and offering direct contact with the support team to help with any roadblocks.
- Sent 7 days after signup if SDK is still not installed: This final email presented a more in-depth look at the benefits product managers, and the company could derive from the installed SDK and support to find their SDK keys. It also provided an option to schedule a personalized walkthrough with the UXCam support team.
After implementing the behavioral onboarding email sequence, UXCam saw a , leading to and over
The engagement with the email campaign led to an impressive , indicating that users found the emails valuable and helpful.
Consequently, the, with more product managers deriving value from the solution sooner, reducing the overall churn rate.
These results highlighted the impact of thoughtful, targeted onboarding emails on user engagement and product value recognition. In addition, it showed the value of maintaining regular communication with users.
I started working with Atmos in May 2025 and here are the results I have been able to deliver for this client
through emails in 6 months representing
in revenue generated through email campaigns
in revenue generated through email flows
in revenue generated in 6 months from emails
New signup welcome
Checkout abandonement
Post-purchase nurture
Customer winback (30D, 60D, 90D)
Feedback flow
Customer win back flow
Unfortunately, I'm not able to share most of the emails here.
Every business is different and a strong understanding of your audience is the bedrock for helping you deliver solid revenue growth through email campaignsThe email style and template used in this campaigns are simple, minimalist, text focused with creative copywriting and offer driven.Delivering the right offer at the right time at the right place in the customer journey is the key to resounding success with email campaign like I delivered for this client.Here's an . It's not fancy with bells and whistles. That's because I tested thoroughly and discovered this is the type of email template style that works for this audience.