![Yaroslav B.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Yaroslav B.")
YB

Yaroslav B.

Full Stack Engineer

Information Technology and Services

Mid-Market (51-1000 emp.)

7/8/2026

"Drip turned our product events into something marketing could actually use"

4.5/5

What do you like best about Drip?

What makes it valuable for me is the way it turns user behavior into actions that marketing can actually use. Purchase events, browsing activity, and customer interactions can become automated workflows without needing to build everything from scratch. It becomes easy to understand what should happen when someone abandons a cart, makes their first purchase, comes back after being inactive for a few weeks, or enters a specific segment. From a developer perspective, that matters a lot because marketing doesn't have to depend on me every time they want to understand or adjust a workflow. If an automation depends on a purchase event, a tag, a segment, or a specific behavior, the logic is clear enough for everyone to follow. The API has also been flexible enough for more customized setups. In one project where we weren't working with a standard ecommerce platform, we were able to send our own events and customer attributes from the backend to power segments and automations without creating unnecessary complexity. Review collected by and hosted on G2.com.

What do you dislike about Drip?

I haven't run into any major issues with Drip, but I quickly realize that the platform works best when your data structure is organized. If events are named differently across systems, if a property changes between the frontend and backend, or if segments are created without checking the source data, workflows can start behaving in unexpected ways even when everything technically looks fine. Review collected by and hosted on G2.com.

What problems is Drip solving and how is that benefiting you?

A cart recovery automation gives us a good example of that. For several days, the campaign is generating fewer results than expected. Marketing thinks the email subject line needs improvement, while the product team suspects something is wrong with checkout. Before changing the interface or rebuilding the campaign, we review the events being sent into Drip. That's where we find the real issue. Users coming from a specific promotion are adding items to their cart, but they aren't entering the recovery workflow correctly because the event from that path is missing an important property. We fix the backend event, test the flow with several users, and the automation starts working exactly as expected. What I appreciate about that experience is that Drip doesn't just help us send better emails. It gives different teams a shared view of what is actually happening and helps us catch problems that could have stayed hidden for weeks. Review collected by and hosted on G2.com.

Show More

Current UserValidated ReviewerIncentivizedSource: G2 invite

See what 468 reviewers think of Drip

4.4 out of 5 · Verified reviews from real users

[
Read all reviews
](https://www.g2.com/products/drip/reviews)