Website Analytics Setup Checklist: Track What Matters Early

Analytics set up in a hurry produces numbers nobody trusts. Analytics set up with a plan produces answers. This website analytics setup checklist is ordered the way the work should happen: decide, install, configure, test, document.

It is tool-neutral on purpose. Menus and labels change, but the sequence of good decisions does not. Where a topic has its own deeper guide, you will find a link.

Step 1: Write down the questions first

Before touching any tool, write five to ten questions the data should answer. Good questions are specific and tied to action:

• Which pages bring visitors who later get in touch or buy?
• Which channels send visitors who actually take action?
• Where do visitors drop out of the booking or checkout path?
• Which content is read and which is ignored?

Notice that none of these ask for "traffic". Visits are only useful when connected to a purpose. If a question would not change a decision, drop it.

A hypothetical example: imagine a small yoga studio. Its questions might be: how many people view the class timetable, how many start the booking form, how many finish, and which social or search sources lead to bookings. Four questions, one clear path to measure.

Step 2: Define your key actions

Turn the questions into a short list of actions worth counting. Separate them into two groups.

1. Main outcomes: purchases, enquiries, bookings, calls, sign-ups.
2. Supporting signals: clicking a phone number, viewing pricing, downloading a guide, starting a form.

Keep the list short. Five well-defined actions beat thirty vague ones. Give each a clear, consistent name, because names are hard to change later. The GA4 events and conversions setup guide explains how to translate these into events in a common analytics tool.

Step 3: Choose and create your accounts

Pick the tool or tools that fit your needs and budget. For many small sites that means one analytics platform plus Google Search Console for search data.

• Create the accounts using a business email, not a personal one that may vanish when someone leaves.
• Give at least two trusted people administrator access, so you are never locked out.
• Record who owns each account and where the login details are stored securely.
• Create one property or data stream per site, not one per page.

If you are new to the platform, Google Analytics 4 basics for marketers introduces its model of events and reports.

Step 4: Install the tracking code properly

There are a few common ways to install tracking, and each has its place.

• A plugin or built-in integration for your website platform, which is quick but limited.
• Pasting the code into the site header, which is simple but easy to forget or duplicate.
• A tag manager, which is a container where you add and edit tags without touching site code each time. This suits sites with several tools.

Whichever route you choose, follow these rules:

1. Install it once only. Duplicate installation doubles counts.
2. Install it on every page, including the thank-you page and any separate booking or shop subdomain.
3. Do not mix installation methods without knowing what each does.
4. Note the installation method in your documentation.

Step 5: Handle consent and privacy

Measurement collects data about visitors, so respect their choices and the rules that apply.

• Check what consent your visitors' locations require, and configure your tools accordingly.
• Make sure analytics tags respect the choice recorded by your consent banner. See the cookie consent banner guide for the design and testing side.
• Do not collect personal details such as names or emails in analytics fields, including in page addresses or form values.
• Publish a privacy policy that describes what you measure and why.

This is general guidance, not legal advice. Confirm the requirements that apply to your site.

Step 6: Configure the settings that distort data

Default settings are not always right. Review these early.

1. Time zone and currency: set them to match your business.
2. Internal traffic: exclude visits from your own team, office network or devices, otherwise your own browsing inflates results.
3. Referral exclusions: stop payment gateways and booking tools from being counted as the source of a sale, since that hides the real source.
4. Cross-domain tracking: if visitors move between your site and a separate shop or booking domain, configure it so they remain one visit.
5. Data retention and sharing options: review and choose deliberately.
6. Search linking: connect Search Console so queries and landing pages appear alongside behaviour.

Each of these prevents confusion months later. The Google Search Console basics article explains what that connection adds.

Step 7: Set up events and conversions

Now implement the key actions from step 2.

• Use any events the tool collects automatically, such as page views and scrolling, and check what they mean in practice.
• Add custom events for form submissions, phone clicks, button clicks and downloads.
• Mark only your main outcomes as conversions. Marking everything as a conversion makes the reports meaningless.
• Pass useful details with events where available, such as the form name or the product category, but never personal information.

For more depth on purchases, leads and ad platforms, see the conversion tracking setup guide.

Step 8: Tag your campaigns consistently

Without clear tagging, traffic from emails, social posts and adverts lands in vague groups. Add parameters to campaign links using a consistent naming scheme: lower case, no spaces, same words every time. The UTM parameters guide lays out a scheme you can copy. Keep a shared spreadsheet of campaign names so everybody uses the same ones.

Step 9: Test before you trust

Never assume tracking works. Test it.

1. Use the tool's real-time view and visit your site from a private window.
2. Click through the key path and check that each event appears once, with the right name.
3. Submit a test form, and confirm the conversion registers exactly once.
4. Test on a phone as well as a computer.
5. Test with consent both given and refused, and confirm behaviour matches your intention.
6. Check that your own visits are excluded.
7. Complete a test purchase or booking, if relevant, and confirm any value is passed correctly.

Allow a day or so for standard reports to populate, and compare them with a second source, such as your sales records or enquiry inbox, to see whether the counts are plausible. Small differences are normal. Large gaps point to a setup issue.

Step 10: Build a simple dashboard

Raw reports are rarely the best view. Create a single page showing the answers to your original questions: key actions over time, top sources, top landing pages and the main path's drop-off points. The marketing dashboard guide and Looker Studio dashboard guide show how to lay this out in a readable way.

Keep it light. A dashboard with a dozen charts is rarely read.

Step 11: Document everything

This step is skipped most often and regretted most. Create one short document that records:

• The questions the setup answers.
• The accounts, owners and access levels.
• The installation method and where tags live.
• The list of events and conversions, with definitions.
• The naming scheme for campaigns.
• Known quirks, such as excluded traffic or the date tracking changed.
• A change log, where you note every future edit with a date.

This document helps new team members, agencies and your future self.

Step 12: Schedule maintenance

Tracking breaks quietly. Add these to a regular routine alongside your website maintenance checklist.

1. Check monthly that data is still flowing and conversions still register.
2. Re-test after any redesign, plugin change or form replacement.
3. Review the event list quarterly and remove unused ones.
4. Revisit your questions twice a year, as the business changes.
5. Audit access and remove people who have left.

Quick reference checklist

• Questions and key actions written down.
• Business-owned accounts with more than one admin.
• Tracking installed once, on every page and domain.
• Consent and privacy handled.
• Internal traffic and referral exclusions set.
• Events and conversions created and tested.
• Campaign tagging scheme agreed.
• Dashboard built.
• Documentation and review schedule in place.

Takeaway

Good analytics begins with questions, not code. Decide what you need to know, define the few actions that matter, install tracking cleanly, configure the settings that distort data, test thoroughly and write it all down. A small, trustworthy setup is worth far more than a sprawling one.

If you would like help planning or auditing your tracking, get in touch with a short note on your site and goals.