Monetly
Docs home

Monetly Docs

Troubleshooting No Decision

Diagnose why a Monetly experiment has not produced a BUILD, ITERATE, or KILL decision yet.

View as MarkdownLast updated:

Public usage documentation: this page explains how to use Monetly. It does not define product logic. Core behavior is governed by Monetly's internal Decision OS and platform contracts.

Summary

No decision usually means Monetly does not yet have enough qualified evidence for the experiment. It can also mean the experiment is not in a state where decision evaluation is possible.

Troubleshooting should focus on setup, traffic quality, experiment state, and billing state before assuming the idea has failed.

Key Rules

  • No traffic means no behavior to evaluate.
  • Traffic quality matters as much as traffic volume.
  • Mode-specific behavior must match the validation mode.
  • Stopped, concluded, draft, or billing-blocked experiments may need action before more evidence can be collected.

Steps

  1. Confirm the experiment is running.
  2. Confirm the public URL works for the domain option you chose.
  3. Check whether the traffic source matches the intended audience.
  4. Check whether visitors can complete the intended mode action.
  5. Review dashboard messages for billing, quota, or setup blocks.
  6. If the setup changed materially, consider starting a clean new experiment.

Common Mistakes

  • Assuming no decision means KILL.
  • Sending traffic to an old or unverified URL.
  • Using a validation mode whose action does not match the offer.
  • Changing the page during a run and expecting one clean interpretation.

Traffic Problems

If visitors are not reaching the experiment, Monetly has nothing useful to evaluate. Check the active URL, campaign destination, and domain status.

If visitors are reaching the page but do not represent the intended audience, the signal may stay weak or noisy.

Setup Problems

A draft experiment, unverified custom domain, missing active page, or blocked billing state can prevent a clean validation run.

Fix setup problems first. Then send stable traffic to the active experiment and wait for new evidence.