See which channel brings your Astro buyers

MIRA FIVE is analytics built around the person, and the Astro integration is the quickest way in: one line in astro.config, and every page of the site is counted, including client-side navigation. An endpoint adds the paid orders, so you see which channel brings the people who buy.

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 organic search and paid social to email and AI assistants. In the sample shop, Direct sent 525 visits, Organic search 438 and Paid social 277 over 30 days.
2. Which pages do they land on? Journeys › Pages lists every page 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.

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. The endpoint 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 to setting up a purchase goal walks through it.

How do I collect with consent?

Switch the website source to Full under Data → Sources. Then set mode: 'full', and the integration adds the identity code to the bundle:

export default defineConfig({
  integrations: [mirafive({ mode: 'full' })],
})

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

import { mirafive } from '@mirafive/sdk-astro/client'

// From your consent banner
mirafive('consent', true) // statistics only
mirafive('consent', { statistics: true, experiments: true, targeting: false }) // by scope
mirafive('consent', false) // forgets what is stored on the device

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

// After sign-out
mirafive('reset')

Before an answer, full mode stores and sends nothing. Ids live in localStorage, never in cookies. The Astro SDK docs show how to answer before the bundle loads.

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}` },
)

The server-side guide covers retries and idempotency.

Can I read feature flags?

Yes. Add features: ['flags'] to the integration and read feature flags inside the flags listener, which runs when they load or change:

mirafive('flags', () => {
  const newCheckout = mirafive('flag', 'new-checkout', false)
  document.body.classList.toggle('new-checkout', newCheckout === true)
})

On pages rendered on demand, miraFlagsFor() from @mirafive/sdk-astro/server answers them before the first paint. A code A/B test is a flag read the same way.