AI helpers
SetRoasFlow has a handful of AI features scattered through the dashboard. They share one design rule: they run only when you click. Nothing is generated in the background, nothing runs on a schedule, nothing fires on every page load — so the cost of having them around is effectively nothing until you actually ask for one.
They also share a job: turn dashboard data into plain language. Each one takes something you'd otherwise have to interpret — a score, a rule set, a platform error — and tells you what it means and what to do, in words, without jargon. They're helpers, not decisions: read the suggestion, then do what makes sense for your store.
Every one of them is optional. Ignore them entirely and nothing about your tracking changes.
Match-quality advisor
Where: the Delivery page, next to your match-quality score.
Your match-quality score tells you how well your events can be matched to real people, but not what to do about it. The advisor closes that gap: click it and it reads your current signal mix and hands back one to three concrete actions — "start sending hashed phone numbers", "pass the customer email on your purchase event" — the ones that would move the score most.
See Testing & troubleshooting for what the score itself measures.
Describe your audience
Where: the Segments builder.
Type what you want in plain words — "customers who added to cart in the last 14 days but never bought" — and it fills in the segment's rule fields for you to review. It's the fastest way to get from an idea to a working segment without learning the rule names first.
This one is covered in full, with examples, in Segments & audience activation.
Explain this error
Where: the Delivery page, on any failed delivery row.
Platform errors are written for developers — a status code, a field name, sometimes just a number. Click Explain on a failed row and it translates that raw error into what went wrong and how to fix it, in plain language. Usually that's the difference between "error 190" and "your Meta access token expired — regenerate it on the destination tab and re-save".
Weekly summary
Where: the Overview page.
A short, plain-language recap of your week — what happened to your events, deliveries and customers, written the way you'd explain it to a colleague rather than as a wall of numbers. Click to generate it when you want the gist without reading every chart.
What they are not
These helpers read your own dashboard data and describe it. They don't change your settings, build segments on their own, send anything to your platforms, or make spending decisions for you. When one suggests an action, you are the one who takes it. Treat the output as a well-informed second read, not an instruction.