Public trace · no login
One bid.
Twenty-one steps, all shown.
Most PPC tools give you a number. This is the whole decision behind one — the conversion estimate and where it came from, the seven safety gates it had to clear, and the arithmetic that turned €0.58 into €0.68.
Read the traceAccount settings read at decision time
- Target ACoS
- 27.5%
- Set per marketplace by the seller. DE, GENERIC · BROAD campaigns.
- Average order value
- €68.70
- Trailing 28 days for this ASIN on Amazon.de.
- Warm-start prior
- Beta(2.2, 68.8)
- Category prior, so hour one has a sensible bid instead of no bid.
- Observed window
- 402 clicks · 14 conversions
- Trailing 28 days for this keyword.
- Days of supply
- 38 days · lead time 14
- From SP-API. Feeds the Sentinel multiplier.
- Previous live bid
- €0.58
- 14-day median €0.59, which sets the anti-decay floor.
agent
Tactician
marketplace
DE
keyword
leather laptop sleeve 14"
campaign
GENERIC · BROAD
The Strategist runs a state machine per ASIN — LAUNCH, GROWTH, PROFIT, DEFEND, HARVEST. PROFIT means the listing has enough conversion history to be bid for margin rather than for rank, which is what licenses the target-ACoS arithmetic further down. In LAUNCH the same keyword would be bid above break-even on purpose.
StrategistWhere the ad can appear for this term. GENERIC is unbranded search — the buyer is describing a product, not naming a seller. Branded and competitor surfaces carry different conversion rates and different ceilings, so the surface is read before anything is computed rather than after.
SemanticConversion rate for this hour of this weekday, trained on Amazon Marketing Cloud data. Amazon.de converts materially better on a Tuesday afternoon than at 03:00, and a bid that ignores the hour overpays overnight and underbids in the window that actually sells.
Semantic(2.2 + 14) ÷ (2.2 + 68.8 + 402) = 16.2 ÷ 473 = 3.42%
The posterior mean of a BetaBinomial: the category prior plus what this keyword has actually done. Raw observation says 14 ÷ 402 = 3.48%; the prior pulls it toward the category’s 3.10%. With 402 clicks the data dominates, which is the behaviour you want — at 12 clicks the prior would still be carrying most of the estimate rather than letting one lucky conversion set the bid.
Tactician402 ÷ (402 + 164) = 0.71
How much of the estimate comes from this keyword rather than from the hourly model. 164 is the half-weight point: at 164 clicks the two contribute equally. It is a deliberate distrust of small samples — a keyword with 20 clicks is bid mostly on the model, and earns its own weight as it accumulates evidence.
Tactician(0.71 × 3.42% + 0.29 × 4.81%) × €68.70 = 3.83% × €68.70 = €2.63
Expected revenue from one click: the blended conversion rate multiplied by the average order value. Everything above this line is about how often a click converts; everything below is about what fraction of that revenue we are willing to spend to get it.
Tactician1 ÷ (1 + e^(−1.6 × (38 ÷ 14 − 1))) = 0.94
Sentinel damps the bid as stock runs down, on a sigmoid over cover ratio — days of supply against effective lead time. At 38 days against a 14-day lead the multiplier is 0.94, so barely any damping. At parity it would be 0.50, and below it the bid falls away quickly. This is the gate that stops a tool spending hardest on the ASIN about to stock out.
Sentinel0.70 × €0.59 median bid (14 days) = €0.41
An anti-decay floor. Several small legitimate decreases in a row can walk a keyword down to a bid that no longer wins impressions, at which point it stops gathering the data needed to correct itself. The envelope holds the floor at 70% of the recent median so a decline stays recoverable. Not binding here — €0.68 is well above it.
Tactician€0.58 × 0.8 = €0.46 · €0.58 × 1.2 = €0.70
No single cycle may move a bid more than ±20%. The proposal is €0.68, inside the band, so the cap does not bind. When it does bind the bid moves to the edge of the band and the rest of the change arrives next cycle — a target reached in steps is recoverable, a target reached in one jump is a live experiment on the seller’s money.
Tactician€0.68 ≤ 35% × €2.63 = €0.92
A hard ceiling on bid against expected revenue per click, independent of the ACoS target. It exists because the ACoS target is a setting a seller can mistype: this gate catches a bid that would be absurd whatever the target says.
Sentinel€0.68 ÷ €2.63 = 25.9% ≤ 27.5%
The implied ACoS of the proposed bid against the seller’s target for this marketplace. 25.9% against a 27.5% ceiling. The two are close because the proposal was derived from the target — this gate is checking the arithmetic that produced it, not applying a second opinion.
Sentinel€0.68 ≤ 5% × €68.70 = €3.44
A per-marketplace absolute ceiling at 5% of order value, applied regardless of what the model believes. The backstop for a corrupted input: if AMC returned a nonsense conversion rate, every proportional check above would agree with itself and still be wrong.
Sentinel14 conversions in 402 clicks — not zero-conversion
Guard 3.5: a keyword that has spent $100 or taken 50 clicks with no conversion stops being bid up, whatever the model estimates. This keyword converts, so the gate is inert. It is the single cheapest waste control in the system.
SentinelTwo switches, global and per-marketplace, either of which halts submissions immediately. Checked at decision time rather than at submission time so a switch thrown mid-cycle stops the decision as well as the write.
SentinelA per-keyword breaker that opens when return on ad spend collapses relative to its own recent baseline, and stays open until the keyword recovers. CLOSED is the healthy state — current flows. Per-keyword rather than per-campaign so one failing term cannot freeze a whole campaign, and cannot hide inside its average either.
SentinelA hash of (keyword, bid, campaign) checked against the last 24 hours. A retry after a timeout must not place the same bid twice — Amazon accepts it, and the audit log then shows two decisions where one was made.
Executor€0.68 ÷ €0.58 = 1.17× ≤ 3×
The last gate before the write: proposal against the keyword’s own baseline, clamped at 3×. The cycle cap already bounds a normal move, so anything reaching this gate is a bug rather than a decision. It has fired in staging and never in production, which is the correct ratio for a check of this kind.
ExecutorA Thompson draw decides whether this cycle exploits the current estimate or explores around it. In PROFIT state exploration is held to 5% of decisions, and this draw came back EXPLOIT — so no exploration multiplier is applied and the bid is exactly what the model asked for.
BidExplorerThe bid currently live at Amazon for this keyword, read at decision time.
Executor€2.63 × 27.5% × 0.94 = €0.68
Expected revenue per click, times the share of it the seller is willing to spend, times the supply multiplier. Every term is on this page and every term is checkable — which is the whole argument for writing the trace down.
Tactician(€0.68 − €0.58) ÷ €0.58 = +17.2%
Submitted to Amazon. Seven gates cleared, one cap not binding, one anti-decay floor not binding. The trace is retained 30 days and exports as CSV, so this line can be answered for later — by the seller, by their accountant, or by us.
Executor
21 steps · 30-day retention
click any row to expand · blue rows changed the outcome
What you are looking at
Mirox re-prices keywords on a cycle. Each time it considers one, the Tactician writes a structured record of the decision: the inputs it read, the intermediate values it computed, every safety gate it checked and in what order, and the action it submitted. That record is the trace. It is stored for 30 days, exports as CSV, and is what you read in the dashboard the moment after a bid posts.
The 21 lines above divide into four kinds. Inputs are read, not decided — the state machine’s verdict on the ASIN, the hour’s historical conversion rate, the bid currently live. Computations derive one number from others, and each shows its working. Gates can only stop a bid, never raise one. The single decision at the end is what went to Amazon.
The order matters as much as the content. Gates run after the proposal and before the write, so a bid that fails one is not submitted at all — never partially, never at a reduced figure — and the trace names the gate that stopped it. The seven-layer safety system is that ordering, written down.
Why this page exists
Every tool in this category says its AI is explainable. Ask one why a specific bid moved on a specific Tuesday and you will usually get a chart of outcomes rather than an account of the decision. The distinction is not academic: a chart tells you what happened, and only a trace tells you whether it should have.
So this is the version that can be checked. The numbers reconcile, the formulas are printed next to the values they produce, and the CSV is the same export a paying customer gets. If the arithmetic is wrong, it is wrong in public, which is a stronger commitment than any adjective we could put on a landing page.
Want to price the gap between where your account is and where you want it? The waste calculator does that from three numbers, and the ACoS calculator works out the break-even the target ACoS above is measured against.
Questions this raises
- Is this a real seller’s data?
- The shape is real — it is exactly what the Tactician writes for every decision, and the export button gives you the same CSV the dashboard does. The account is not a customer’s. Publishing a seller’s keywords, conversion rates and order values because they made the clearest example is not a trade we get to make on their behalf.
- Can I check the maths?
- That is the point of the page. Every derived figure shows its arithmetic with this trace’s numbers substituted, and every input it depends on is listed at the top. The chain closes: blended conversion rate times order value gives revenue per click, times the target ACoS gives the target bid, times the supply multiplier gives the €0.68 that was submitted. If a line does not add up, tell us — that is a bug in the product, not a typo on a marketing page.
- What happens if a gate fails?
- The bid does not go out, and the trace records which gate stopped it and why. Gates are checked in order and the first failure ends the decision — there is no path where a bid is submitted with a gate unresolved. The kill switches are checked at decision time as well as at submission, so one thrown mid-cycle stops the decision too.
- Do I get this for my own account?
- Yes, from the first day of Simulation Mode, before any money moves. Simulation Mode scores your real keywords and writes a full trace for every bid it would have placed — without placing it. Traces are retained 30 days and export as CSV.
- Why publish this at all?
- Because "explainable AI" is a claim every vendor in this category makes and almost none of them will show you. A screenshot proves nothing; a complete trace with checkable arithmetic and a download button is either right or it is publicly wrong. We would rather be the second than be vague.
Your account, your traces
Read one of these
for every bid on your account.
Simulation Mode runs 30 days on your real keywords, read-only and without a card. Every bid it would have placed gets a trace like this one — before a cent moves.
30 days free on Simulation Mode · no card required · connect and disconnect in one click