Analytics by 5H3LL · Learn · Pricing

5H3LL product guides · Updated 27 October 2026

Plan a launch review before publishing

Set up campaign names, a completed outcome and a review window so launch-day traffic becomes useful evidence.

The question to answer

Launches combine different audiences, offers and times of day. Watching the globe can help confirm that visitors are arriving, but the later review needs consistent links, a defined outcome and enough time for people to return. Decide what you will measure before the first post goes out.

Before you start

A tested landing page, consent controls and tracking setup.

A completed-action goal and payment attribution where relevant.

A campaign register and a period for follow-up observation.

1. Choose a primary outcome

Pick one result, such as completed signups or successful payments. Record a baseline from a comparable period where possible. Keep secondary measures such as visits and checkout clicks as context rather than interchangeable definitions of success.

2. Prepare tagged links

Create separate campaign links for X, your newsletter, a community post and any partner placement. Use a shared naming convention with distinct identifiers. Keep a record of the destination, placement and publication time.

3. Run a pre-launch check

Open the actual links on desktop and mobile, verify redirects preserve tags, then complete the intended test action. Check that your payment connection or completion event is working before interpreting the campaign as a revenue experiment.

4. Watch arrival without overreacting

Use Live or press M in the dashboard to inspect current activity. Look for broken destinations or a missing event stream. A quiet moment or a large spike is not yet evidence of the launch’s overall business result.

5. Review equal observation windows

Compare campaign visitors, goals and credited payments after an agreed interval, then again after your usual purchase delay. Record campaign costs and hours separately. Use the next launch to repeat one useful finding instead of copying every detail.

Worked example

A newsletter sent on day two should not be compared with a day-one post using only the launch’s first 24 hours. Align time since publication, and note that recorded source credit is not proof of incremental lift.

Check your setup

Every controlled placement has its own campaign name.

The primary completed-action goal is tested.

The review includes buying delay and campaign cost.

How to interpret the result

Real-time activity is a snapshot, not a forecast.

Consent, blockers and missing referrers leave incomplete journeys.

The app does not fetch social impressions or automatically publish campaign posts.

Your next action

Create the campaign register now, schedule the first review after a fair observation window, and write down the single decision you want that review to inform.

Illustrative phaseQuestionRecord
Before publicationDoes the journey work?Test result and campaign URLs
During launchAre visitors reaching the site?Live checks and operational problems
After the buying windowWhich observed outcomes followed?Visitors, goals, revenue, costs and timing

Free plan available. Paid plans from £3. Refund policy.