Cosa ti piace di più di Customer.io?
The thing that keeps me on Customer.io is how much you can do inside a campaign without touching a developer. I build reactivation sequences where the copy changes based on whether a user ever visited the deposit page, what their balance looks like, and how many trades they've closed. All of that branching lives in one flow and stays readable.
Liquid templating is genuinely useful in production. The | default: filter alone has saved campaigns from breaking when an attribute is missing. I also track things like deposit count by incrementing it through event triggers and storing it back as a profile attribute, which lets me personalize messages across the full lifecycle without a data team involved.
The segment logic is precise enough to matter. Filtering on event attributes, not just event names, means I can target depositors who never traded separately from users who deposited and went quiet. Those are different people and they need different messages. Customer.io makes that distinction easy to build and easy to maintain.
On the integration side, we pipe behavioral events in real time and use them as triggers directly. The built-in request tester was useful during setup and saved a lot of back-and-forth. Sends are consistent, which matters when the content is time-sensitive.
Documentation covers most real-world edge cases. Liquid conditionals, webhook retries, attribute filtering nuances. I have rarely needed to open a ticket because the answer was usually already there.
The pricing model makes sense for how we actually operate. We are not paying for a static contact list where 60% of users have been inactive for months. Costs scale with real activity, which makes it straightforward to justify internally.
One thing worth mentioning: the built-in AI assistant has replaced a decent chunk of what I used to send to support. Not for complex setup questions, but for things like Liquid syntax, segment logic, figuring out why a trigger is not firing the way I expect. It usually gets me to an answer faster than waiting on a ticket, and the answers are specific enough to actually be useful rather than just pointing me to a doc I already read. Recensione raccolta e ospitata su G2.com.
Cosa non ti piace di Customer.io?
The biggest friction point is around historical event data. Customer.io does not expose event counts through Liquid or JavaScript, so if you want to personalize based on how many times something has happened, like number of deposits or trades, you have to either engineer a workaround through event-triggered attribute increments or do a CSV backfill. For a platform that is otherwise quite flexible, that gap feels inconsistent.
Another recurring annoyance: we treat email as a sensitive attribute for compliance reasons, which is the right call, but a side effect is that individual user search by email gets disabled. Finding a specific test user for QA checks then becomes a longer process than it should be. When you are trying to quickly verify how a particular profile will render in a campaign, that extra friction adds up.
Segment preview and campaign analytics are functional but not deep. If you want to understand why a specific user did not enter a campaign or where exactly in a flow drop-off is happening, you end up doing more manual digging than you should need to. Better per-user journey visibility inside the campaign view would save a lot of time.
None of these are reasons to leave, but they are the kind of things that slow you down on a regular basis rather than being one-time setup issues. Recensione raccolta e ospitata su G2.com.
