Onboarding is a single session. After that, the pipeline runs on its own, every week, until you tell it otherwise.
Onboarding is a single session, done through OAuth, no CSV exports. After that, this cycle repeats every week on its own. The only input required from you is an approve or dismiss click.
Store, ad accounts, and email tool, connected via OAuth in a single session.
Cost of goods, return lag, and fees blended into the real number, per campaign.
Each with a dollar impact and an approve or dismiss action.
Approving executes the change through the platform's API. Dismissing does nothing.
Any approved change can be undone within 24 hours from the same report.
This sandbox uses an illustrative store and dummy ad accounts. The mechanism, including the approve/dismiss buttons and safety rails, is the same one used in a live report.
Generate a simulated weekly report, then approve or dismiss each decision to see how the execution mechanism behaves. Nothing here affects a real account. The confidence percentage on each card is how sure the calculation is, given the data available; low confidence usually means a data lag, like returns still coming in.
True ROAS 0.9× after cost of goods, fees, and returns (platform shows 1.8×). Losing money on every order.
True ROAS 2.4×. Earns $1.40 per dollar spent after all deductions. Increase capped at 30% of current weekly budget.
The 2.1pt margin dip traces to a monthly payment-processing fee tier. One plan change resolves it permanently. No ad account change required.
No CSV exports, no scraping. Every integration uses the platform's OAuth flow. Don't see yours? Request it.
A 20-minute call, using your real store and ad account data. No pitch deck.