Verify and debug

Use this page to confirm that events reach MIRA FIVE, and to find out why they do not. Every check below works without the dashboard except the last step, the live view. For the codes themselves, see Errors.

Check an installCopy Anchor Link

In the browser:

1. Open the site on its real domain. From localhost, nothing is sent unless you allow it (see Localhost).
2. Open the browser's developer tools on the Network tab.
3. Send the queue now instead of waiting up to 5 seconds: run mirafive('flush') in the console for the script tag, or call mira.flush() in your code.
4. Find POST https://events.mirafive.io/v1/batch/mf_…. It answers 202 with a receipt:

{ "batch": "0192d4a8-7b1c-4e8a-9c1d-2b3e4f5a6b7c", "accepted": 1, "dropped": 0 }

5. Open the source's live view in MIRA FIVE and find the event.

A 202 is final, also when it kept nothing. The reasons:

For a server, send an install check and read the receipt, or pass onError and watch it.

LocalhostCopy Anchor Link

Browser SDKs send nothing from localhost, 127.*, [::1], *.local or a file: page, so development does not pollute your numbers. To send from there:

<script defer src="https://cdn.mirafive.io/mira.js" data-key="mf_…" data-track-localhost></script>

The Astro integration is also off in astro dev unless you pass dev: true (see Astro).

The server always accepts localhost and 127.0.0.1 as origins, so you do not add them to a source's allowed origins. Use a separate source for development if you want to keep test events apart.

Install checkCopy Anchor Link

$install_check is an event that proves a key and a host work. The server answers it with a receipt and never stores or bills it:

curl https://events.mirafive.io/v1/batch \
  -H "Authorization: Bearer $MIRAFIVE_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"v":1,"batch":"0192d4a8-7b1c-4e8a-9c1d-2b3e4f5a6b7c","mode":"full","events":[{"name":"$install_check"}]}'

The answer:

{ "batch": "0192d4a8-7b1c-4e8a-9c1d-2b3e4f5a6b7c", "accepted": 0, "dropped": 1, "reason": "install_check" }

mirafive:check prints the host, the key's namespace and the mode, sends the check and fails unless the reason is install_check. The install check runs before the bot filter, so curl works with a website key too: POST /v1/batch/mf_… with the same body and no Authorization header.

RefusalsCopy Anchor Link

A refused batch answers with an error body, { "code": "…", "detail": "…" }:

The browser SDKs show the code as a development warning ([mirafive] batch: origin_not_allowed). MIRA FIVE also records refusals that come after the key check on the source, so you can see them there.

Nothing arrivesCopy Anchor Link

Work down this list:

1. The page runs on localhost or another local host without trackLocalhost (see Localhost).
2. Do Not Track or Global Privacy Control is on in your browser. The browser SDKs then send nothing, by design. Test in a profile without them.
3. window.__mirafive_ignore is set, for example because you are signed in as an admin (see Ignore your own visits).
4. The page is in full mode and no statistics consent was given. Full mode sends nothing before the grant (see Consent).
5. The page's Content Security Policy blocks the request. Allow connect-src https://events.mirafive.io (or your host), and for the script tag script-src https://cdn.mirafive.io.
6. The receipt says dropped with a reason, or the request is refused (see above).
7. Server events: the process ended before the buffer was sent (see Batching and flushing), or onError reports a failure.

Development warningsCopy Anchor Link

Browser SDKs log warnings starting with [mirafive] only on a local host name (localhost, 127.*, [::1], *.local, file:), once per message. To see warnings about the server's answers, develop on localhost with trackLocalhost: true.

The script tag logs these on every host, since they mean a broken install: [mirafive] no data-key, [mirafive] bad key (the data-key is not a website key), [mirafive] no script tag, and [mirafive] <feature> chunk failed (a part of the script was blocked by the network, a Content Security Policy or an integrity check).

createMira() throws a TypeError for a secretKey option, a host without a scheme, and mode: 'full' without identity(). Server SDKs report failures to onError, or log [mirafive] … without one.

TestsCopy Anchor Link

Keep tests from sending events:

The fakes still check every event, so an event MIRA FIVE would refuse fails the test as it would fail in production.