Klaviyo Strawberry

Why that customer got that email, answered in two minutes

A profile looked up by email, the account’s metrics listed, then that profile’s events in order. What comes back is a timeline with event ids you can paste into a bug report.

A customer who bought last Tuesday got the win-back email on Thursday, replied to ask whether anyone there pays attention, and three people are now guessing at the cause in a thread.

A companion answers it. It finds the profile, lists the metrics that could have fired, and pulls that profile’s events in order, so the thread ends with a timeline instead of three theories.

Why did this person get that email?

The companion looks the profile up by email, lists the account’s metrics to find the right event types, then pulls that profile’s events in order: the order placed on Tuesday, the timestamps around it, and what did or did not fire afterwards. A timeline with event ids you can paste into a bug report.

That is usually enough to see the cause, the purchase event arriving under a different metric than the flow’s exclusion checks, and it takes a couple of minutes instead of an afternoon. Every claim in it points at an event somebody else can go and look at.

Two tools write, and both are deliberate

Creating a profile adds a person to your account and deliberately does not subscribe them to email or SMS, because subscription goes through a different Klaviyo endpoint this integration does not carry. Consent stays an explicit act.

Tracking an event records something against a profile by email and will create the metric if it does not already exist, so it is a tool you point rather than fire. Everything that reaches a customer stays where the approvals and the compliance controls already are.

Can the analysis land where the team reads it?

Most Klaviyo questions end in a document: which segments actually bought after the September campaign, how the repeat-purchase window shifted, which list is full of people who have not opened anything since spring. A companion pulls the profiles, events and campaign list, assembles the answer, and writes it into your sheet or doc with the metric and profile ids beside the figures.

Scheduled monthly, that is a standing brief instead of a request. And because the same companion browses, it pairs what your own data says with what is visible outside it, the competitor’s current offer, the review thread about your shipping times, research that starts from your own customer records.

What stays inside Klaviyo

Reading profiles and events is native, repeatable and cheap, which is why the investigation above becomes a standing monthly brief rather than a favour somebody asks for. That is the half a marketing team hands over without a conversation about blast radius.

Flows, segment builders, templates and the send scheduler are changed in Klaviyo, with a companion driving your signed-in session step by step and in view.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Listing metrics, querying events by metric, profile or time window, listing profiles, and looking one up by email are all native. That combination answers most “why did this customer receive that” questions with a timeline of real event ids.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide