See which campaign brings your Next.js customers

MIRA FIVE is analytics built around the person. In a Next.js app one package covers both sides: a provider for the browser, and a server entry for route handlers, server actions and Server Components.

What will I see after installing?

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

1. Which channels and campaigns send visitors? Acquisition › Channels splits visits into nine channels, and each channel opens to its campaigns from your UTM tags. In the sample shop, Direct sent 525 visits, Organic search 438 and Paid search 240 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 route handler sends the order with the same user id, so MIRA FIVE puts the purchase on that person, next to the campaign that first 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. Plugins are functions, so set full mode in a client providers file and render it in the root layout instead of the plain provider:

'use client'

import { identity } from '@mirafive/sdk-browser/identity'
import { MiraProvider } from '@mirafive/sdk-next'
import type { ReactNode } from 'react'

export function Providers({ children }: { children: ReactNode }) {
  return (
    <MiraProvider mode="full" plugins={[identity()]}>
      {children}
    </MiraProvider>
  )
}

Then, in client components, 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. 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}` },
)

The server-side guide covers retries and idempotency.

Can I render feature flags without a flicker?

Yes. flagsFor() from @mirafive/sdk-next/server reads the visitor’s feature flags in the root layout, and the provider hands the answers to the browser, so the first paint shows the right variant. Client components read them with useFlag and useFlagConfig. A code A/B test is a flag read the same way. The Next.js SDK docs show the three pieces and the caching rules.