
the thing that actually changed how i use it is realizing customer.io thinks in events, not campaigns. i came from mailchimp and kept trying to do the same thing, make a list, schedule a blast. it kept fighting me until that clicked.
now i can say: when a user creates their second project but hasn't invited a teammate in 48 hours, send this email. that level of precision would have taken me three tools before.
the journey builder took about two weeks to get comfortable with. the "wait until" block is the one i use most, it holds a message until a condition is true instead of just waiting a fixed number of days. replaced two zaps i had running just with that.
liquid templating felt intimidating at first but the docs are genuinely good. once you get the syntax down you can pull in things like a user's last active feature directly into the email copy. makes a big difference in how the message lands.
support is solid. asked a question about suppression lists late at night, had a real answer by morning that actually referenced my account setup. not a template. Review collected by and hosted on G2.com.
pricing caught us off guard. grew past the 5,000 profile tier in about 3 months and the next tier was a big jump. felt like there should be something in between for where we were at that point.
the email editor is my least favourite part. it works but it always feels a step behind klaviyo or beehiiv. i ended up designing in figma and hand coding templates through parcel which is their separate email editor. it works but its extra steps every time.
the bigger issue if you're a solo marketer is the setup. customer.io is api-first which means someone has to actually instrument your product events properly. when our dev was stuck in a sprint i was basically blocked for two weeks on the onboarding flow i had planned. nothing i could do until he was free.
if you don't have a developer available when you're getting started, factor that in before you commit. Review collected by and hosted on G2.com.