See which channel brings your Nuxt customers

MIRA FIVE is analytics built around the person. In a Nuxt app one module covers both sides: auto-imported composables in your components, and server utils that send paid orders from server/.

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 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. The server route 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. With Google Ads connected, it adds cost per buyer for each campaign.

How do I collect with consent?

Switch the website source to Full under Data → Sources. Then set mode: 'full' in nuxt.config.ts, and the module adds the identity code to the bundle:

export default defineNuxtConfig({
  modules: ['@mirafive/sdk-nuxt'],
  mirafive: {
    mode: 'full',
    features: ['flags'],
  },
})

Then pass your banner’s answer and the signed-in user through useMira():

const mira = useMira()

// From your consent banner
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, and consent(false) forgets what is stored on the device. 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 useServerMira(event).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. With 'flags' in features, useFlag and useFlagConfig return read-only refs:

<script setup lang="ts">
const newCheckout = useFlag('new-checkout', false)
</script>

<template>
  <button>{{ newCheckout === true ? 'Buy now' : 'Checkout' }}</button>
</template>

Server routes read feature flags with miraFlagsFor(event, { userId }). A code A/B test is a flag read the same way. The Nuxt SDK docs cover the flag bootstrap and cached routes.