Aima started as a marketing assistant that could answer questions about your store. It has grown into something more useful. An evidence-first operator that works with your real, messy merchant data.
The difference is simple. Aima used to give you an answer. Now it shows you the evidence behind it, tells you how confident it is, and flags what it could not verify.
Here is what changed.
Less guesswork
Aima now separates facts, correlations, assumptions, and unavailable data. It no longer jumps to a confident conclusion when the evidence is thin.
When data is missing, it says so. You will see clear labels like Partial and Unknown instead of a clean answer that quietly hides a gap.
Aima can now tell the difference between a tracking issue, an upload issue, a platform reporting difference, a permission gap, and simply missing data. That means fewer dead ends and faster fixes.
Meta diagnostics: Meta sent-event diagnostics now use structured server-side dispatch evidence, cover PageView / ViewContent / Purchase, and deduplicate by event ID, pixel, request ID, and lifecycle stage.
Meta duplicate analysis: AIMA now separates source action, Aimerce transport, and Meta downstream behavior, avoiding unsupported conclusions about Pixel/CAPI mismatch or duplicate events.
Meta CPA analysis: CPA reporting now uses paginated Meta Insights data, row-level
Spend / purchases, and clearly states account, currency, timezone, attribution, and coverage.Google Ads diagnostics: Improved recommendation checks, clearer error details, and stricter separation between facts, platform recommendations, and model assumptions.
Klaviyo analysis: Improved flow/campaign revenue analysis, exact 30-day comparisons, Top 5 flows, account health, event health, and revenue date validation.
Shopify analysis: Improved order summaries, COD vs non-COD handling, date-window validation, order permission handling, and partial coverage messaging.
Attribution answers: AIMA now avoids turning aggregate data into fake daily trends, distinguishes tracked visits from Shopify Sessions and Page Views, and clearly marks unavailable coverage.
Scheduled tasks: Fixed Slack fallback, duplicate runs, watchdog timeouts, recovery behavior, low-balance task states, and idempotency around scheduled time.
Merchant-safe output: AIMA now hides raw tool names, internal backend details, query metadata, emails, phones, IPs, browser identifiers, and other sensitive values.
Safer answers
Merchant-facing responses now hide sensitive identifiers automatically. Emails, phone numbers, IPs, and browser identifiers like fbp and fbc stay out of the output.
Internal tool names and infrastructure details are hidden too. You get the insight without the plumbing.
More reliable automation
Scheduled recaps and Slack workflows are far more resilient. Better retry logic, watchdog handling, fallback delivery, and billing checks that run before a task starts instead of failing halfway through.
If a message lands in Slack, you will not get a duplicate failure alert afterward. If an account balance is low, the task fails predictably instead of silently.
Better next steps
Instead of stopping at "something failed," Aima points you toward the fix. Reconnect an account. Check a permission. Widen a date range. Validate a specific platform.
Try it
Why did my Meta Purchase events drop yesterday?
Check whether my Google Ads conversions are uploading correctly.
Compare Klaviyo flow revenue over the last 30 days and show the top 5 flows.
Why is my CPA different from what I expected?
Check if my Purchase events are duplicated.
Summarize COD vs non-COD orders last week.
Run a daily recap every morning and send it to Slack.
Export last week's UTM revenue performance.
Check whether attribution data is complete or partial.
Is my tracking, Meta, Google Ads, Klaviyo, and Shopify setup healthy?
Ask Aima anything about your store's data. It will tell you what it checked, what it found, and what still needs a look.
Put Aima on a schedule
You do not have to remember to ask. Aima can run your most common checks on a schedule and deliver the answer to Slack or your dashboard before you start your day.
The best use is catching problems early. Instead of asking "why did revenue drop" after the fact, let Aima watch for it and tell you first.
A few worth turning on:
Daily account recap. Yesterday's orders, revenue, AOV, and spend and ROAS by platform, with anything that moved sharply flagged.
Tracking and CAPI health check. A daily confirmation that your Meta events are firing, nothing is duplicated, and no Purchase events failed to send.
Revenue anomaly watch. A quiet all-clear most mornings, and a short root-cause pass on the days something actually moves.
Weekly product performance. Best and worst performers over the last 30 days, with the biggest movers called out.
Klaviyo campaign and flow review. Your last sends and your flows-vs-campaigns revenue, every Monday.
Set the cadence, time, and channel you want. Change or pause any task whenever you like. Ask Aima to schedule something and it will set it up for you.
Task | Default cadence | Channel |
|---|---|---|
Daily Account Recon | Daily, 8am local | Slack + dashboard |
Weekly Product Performance | Weekly, Mon 8am | Slack + dashboard |
Tracking & CAPI Health Check | Daily, 8am | Slack + dashboard |
Revenue Anomaly Watch | Daily, 8am | Slack + dashboard |
Meta ROAS Watch | Daily, 8am | Slack + dashboard |
Weekly Klaviyo Campaign Review | Weekly, Mon 8am | Slack + dashboard |
Klaviyo Revenue: Flows vs Campaigns | Weekly, Mon 8am | Slack + dashboard |
Weekly Channel CAC & Attribution | Weekly, Mon 8am | Slack + dashboard |
Product Launch Tracker | Daily, time-boxed | Slack + dashboard |
Device & AOV Breakdown | Monthly, 1st | Slack + dashboard |
Here to help you win,
Yiqi
