From connected site to first brief

1. Connect the site

How traffic reaches your site determines which collection you can use, so this is the first question.

• Already proxied through the edge — core request analytics start immediately, with no snippet
• Not on the edge — deploy Smart Beacon from a first-party path on your own domain
• Either way, set the domains, timezone and reporting currency for the site

2. Say what success means

Onboarding asks one question — what does this website need to achieve? — and the whole product reorganises around the answer.

• Generate leads, start trials, sell products, start subscriptions, book appointments, take registrations, drive calls, or something custom
• Pick more than one if the site genuinely has more than one
• This determines the default brief, the funnels offered and what the revenue view means

3. Add Smart Beacon where it earns its place

Optional, and deliberately small. Add it when you need something the edge cannot see.

• Single-page and soft navigation, which never produces a document request
• Core Web Vitals and real-user performance
• Engagement, clicks, form starts and form failures
• Content-asset exposure, if a content platform is connected

4. Send server events

This is the step that separates a traffic report from a business one, and it is usually an afternoon of work.

• POST /v1/events with the event name, site, pseudonymous customer key, timestamp, value and currency
• Always send an idempotency key — retries are normal and double-counted revenue is not recoverable after the fact
• Send refunds and cancellations too, not only the happy path
• Use the recommended names where they fit, and namespace anything custom

5. Connect the commercial systems

• Your finance system for customers, invoices, payments and collected revenue
• Your accounting system for recognised revenue, cost and margin measures
• Stripe, Shopify or WooCommerce where they hold the orders and subscriptions
• Advertising and Search Console to judge paid and organic against realised revenue rather than platform-reported conversions

6. Read the brief

The first useful morning is usually spent on questions nobody could previously answer.

• Which of last week's traffic was actually people?
• Which channel produced revenue rather than sessions?
• Which page gets read and never converts?
• Did the release on Tuesday coincide with anything?

What the first week will not tell you

Stated plainly, because a comparison needs something to compare against.

• Anomaly detection needs a baseline — context-aware comparison improves over the first few weeks as weekday and seasonal patterns establish
• Customer value and trial-to-paid need enough elapsed time for the second event to have happened
• Historic data before the connection is not reconstructed; Reveliqo reports from when collection started
• Attribution across a long sales cycle is only as complete as the identity mode you configured