Where your React app's buyers come from

MIRA FIVE is analytics built around the person. In a React app it takes one client and one provider in the browser, and your server adds the paid orders, so every buyer leads back to the channel that brought them.

What will I see after installing?

The first three questions the dashboard answers, from the default setup:

1. Which channels send visitors? Acquisition › Channels splits visits into nine channels, from paid search and email to AI assistants such as ChatGPT. In the sample shop, Direct sent 525 visits, Organic search 438 and Email 170 over 30 days.
2. Which pages do they land on? Journeys › Pages lists every route with pageviews, entries, bounce rate, exits and time on page. Sort by entries to see your landing pages.
3. Which goals do they reach? Goals counts every conversion of the events you send, such as a sign-up or a paid order.

The default setup sets no cookies, stores nothing on the device and sends no identifier.

How does a paid order reach its channel?

Through the person who paid. With their consent, the browser keeps an id for the visitor, and identify ties it to your own user id when they sign in. Your server sends the order with the same user id, so MIRA FIVE puts the purchase on that person, next to their first visit and the channel that brought them.

Create a purchase goal for order_paid, and Acquisition shows buyers and revenue per channel and campaign. The guide Which channel brings the customers who pay? reads those numbers.

How do I collect with consent?

Switch the website source to Full under Data → Sources. Then switch the client to full mode and add the identity() plugin:

import { identity } from '@mirafive/sdk-browser/identity'

const mira = createMira({
  key: import.meta.env.VITE_MIRAFIVE_KEY,
  mode: 'full',
  plugins: [pageviews(), identity(), flags()],
})

Then pass your banner’s answer and the signed-in user:

const mira = useMira()

// From your consent banner's callback
mira.consent({ statistics: true, experiments: true, targeting: false })

// After sign-in, with your own user id
mira.identify(user.id, { plan: user.plan })

// After sign-out
mira.reset()

Before an answer, full mode stores and sends nothing. consent(true) grants statistics only, and consent(false) forgets the ids. Ids live in localStorage, never in cookies. The consent guide explains the three scopes.

How do I make a webhook count once?

Payment providers sometimes deliver a webhook twice. send delivers at once and takes an idempotency key, so a repeat is stored once:

await mira.send(
  [{ name: 'order_paid', userId: order.customerId, properties: { revenue: 328, currency: 'EUR' } }],
  { idempotencyKey: `order-${order.id}` },
)

track buffers and sends within a second. In a function that ends early, await mira.flush() before it returns. The server-side guide covers each runtime.

Can the same client read feature flags?

Yes, through the flags() plugin from step 2. useFlag('new-checkout', false) returns the variant, or true and false for an on/off feature flag, and useFlagConfig returns a remote-config value. A code A/B test is a flag your app reads the same way. The React SDK docs cover server rendering.