Why the basics come before the first campaign
Every basic in this tutorial is cheap to get right on the first day and expensive to fix later. An analytics property opened under a freelancer's personal login has to be rebuilt, and its history is lost when the freelancer leaves. A website that ran for months before analytics was installed has no baseline to compare the first campaign with. A list collected without a record of what people agreed to cannot be mailed with confidence. A listing whose phone number differs from the website's sends some callers nowhere. None of these is a strategy problem, and none can be solved by a better campaign.
| Basic | What goes wrong without it | Where the detail lives |
|---|---|---|
| Business-owned logins and a register | Accounts leave with the person who opened them, taking history and data | Steps one and nine of this tutorial |
| A domain and a domain email address | Sign-ups and enquiries land in someone's private inbox | The email sending domain checklist for sending |
| Analytics with defined key events | The first spend cannot be judged and there is no baseline | The GA4 setup checklist |
| A decided consent approach | Tags added before anyone decided what they may record | The privacy and consent guide |
| Listing and social profiles with matching details | Different names, addresses and numbers across the web | The Business Profile checklist and the citations guide |
| A contact list started with consent | A list nobody can defend or segment | The list-building and consent guide |
| Naming conventions for links and campaigns | Reports full of unassigned or duplicated traffic | The UTM and naming templates |
| A one-page measurement plan | Every number argued about after the fact | The measurement plan guide |
This tutorial is the sequence, not a replacement for those pages, and it is the practical companion to the ideas in the fundamentals section. Ad accounts are created when the first paid campaign is planned, and the new Google Ads account tutorial covers that layer on the assumption that the work here is done. The strategic questions, which segment to serve first, what a customer can cost and how to read the first results, belong to marketing decisions before you have data.
Before you start
- Name the owner of the records. One person, usually the founder in a new business, keeps the account register and decides who gets access. Others can do the work; one person answers for the list.
- Write the canonical business details once. The name as it appears on the sign, the address in one format, one phone number and the website address. The citations and NAP guide calls this the single source of truth, and every listing and profile is copied from it.
- Choose a secure store the business controls for passwords and recovery codes, with two-step login on it, so that access does not depend on one person's memory or phone.
- Decide what counts as a customer action. An enquiry, a booking, a call or an order: whichever shows that someone is becoming a customer. Steps three and eight build on it.
- Allow for waiting. Several steps depend on a verification code, a designer's changes or a supplier's reply, so the set rarely finishes in one sitting. Work through the steps in order and note in the register anything left pending.
The steps
Choose business-owned logins and record every account
Every marketing service will ask for a login: the website host, the analytics property, the business listing, each social profile, the email platform and, later, the ad accounts. Create each one under an address the business controls, ideally on its own domain from step two, never under the founder's personal account, a freelancer's or an agency's. People can then be given access and have it removed, while the account, its history and its data stay with the business. The new Google Ads account tutorial makes the same point for ad accounts, and the GA4 setup checklist opens with it for analytics.
Then start the register, a simple shared table with one row per account: the service, what it is for, the owning login, who else has access and at what level, where the recovery details are kept and the date it was opened. Recovery details, the backup address, phone number and codes that let someone regain an account, should point to the business rather than to a person who may leave.
Secure the domain and a domain email address
Register the domain the business will trade under, on a login from step one, and add its renewal date and payment method to the register: a domain that lapses takes the website and every address on it with it. Then create at least one address on the domain for marketing accounts and enquiries. A shared role address works better than one person's name, because sign-ups, password resets and customer replies then land somewhere the business keeps when people change.
Sending marketing email from the domain needs authentication set up first. The email sending domain checklist covers the records involved and the order to set them up, and this tutorial leaves that work to it.
Install analytics and define the few key events
Install website analytics before the site receives any paid or promoted traffic, so the first visits are recorded in the same way as every later one. The GA4 setup checklist works through the property, the data streamA source of data flowing into a GA4 property: one web stream for a site or an app stream for each iOS or Android app, each with its own settings., the settings, consent behaviour and verification in order; follow it rather than improvising, and add the property to the register.
What this step adds is restraint about events. A new business needs only the few actions that show someone becoming a customer: an enquiry sent, a call started from the website, a booking or an order. In GA4Google's event-based analytics platform. these are marked as key events (Key EventA GA4 event marked as important to the business, the property's measure of success.). Write down what each one means before creating it, for example that a booking counts when it is confirmed rather than when the form is opened, because the measurement plan in step eight refers to these definitions. Then trigger each one yourself and check that it arrives, as the checklist's verification group describes. Calls, messages and conversations in person happen off the site, where analytics cannot see them, so the business also keeps a record of every enquiry and what became of it, which the tutorial on keeping an enquiry record sets out.
Decide how consent will be asked and recorded
Consent is easiest to design before tags multiply. Every tag added later, an advertising pixel, a chat widget, a recording tool, either follows the decision made here or opens a gap in it. The privacy and consent guide explains why it matters to marketing: where consent is required, a tag that sets or reads identifiers must wait for permission, and visitors who decline are partly or wholly absent from the reports. Decide which tags the site will run, how a visitor's choice will be asked (usually through a consent banner or a CMPSoftware that collects, stores and passes on visitors' consent choices for cookies and tracking.), how that choice reaches each tag and where the record is kept. The consent mode guide covers the implementation.
Consent to marketing messages is a separate question, which step six takes up. On the rules themselves, the list-building and consent guide records that the EU's General Data Protection Regulation describes consent as freely given, specific, informed and unambiguous and requires an organisation to be able to show that it was given, and that the UK's Information Commissioner's Office publishes direct marketing guidance explaining the UK's rules on electronic marketing. Rules differ by country, this is general guidance rather than legal advice, and a business unsure which rules apply should take advice before it collects data at scale.
Claim the business listing and social profiles with matching details
Copy every field from the canonical details written before you started. The citations and NAP guide explains why the name, address and phone number (NAPA business's name, address and phone number as they appear across the web.) must agree wherever the business appears, and how the website acts as the master record.
Claim the business listing (GBPLocal listing on Google Search and Maps.) next. The Google Business Profile setup checklist begins with eligibility, claiming the profile in an account the business owns and searching for duplicates before creating a new one, then moves to the real business name without added keywords and details that match the website. Then claim the social profiles the business will actually use, and only those: the social page optimisation checklist covers admins, two-step login, matching names and handles across platforms, and contact details. An abandoned profile still appears when people search for the name, so claim only what someone will keep current. Add each listing and profile to the register.
Start a contact list with consent
An email list is the one audience a business owns outright, and it is easiest to build correctly from the first address. Put a sign-up where interested people already are: the enquiry form, the booking or order confirmation, the counter. Say plainly what people are signing up for and how often they will hear from the business.
For every address, record the source, the date and time, the wording the person saw and the choices they made. That is the record the list-building and consent guide describes, and it makes the list defensible, easy to segment and genuinely First-Party DataData a business collects directly from its own customers, visitors and users.. Keep enquiries and marketing permission apart, because answering a question someone asked is not the same as permission to send them news and offers. Do not load contacts from a personal phone or a previous employer's list without a consent record; the guide explains the risk in imported lists. When the first marketing email goes out, the domain should already pass the checks in the email domain checklist.
Write the UTM and naming conventions
Every link the business shares in an email, a social profile, a partner's website or a printed code should say where the visit came from, and every campaign should have a name that sorts and splits cleanly. The UTM and naming convention templates give the rules for UTMURL tags identifying traffic source. parameters: lower case everywhere, a short list of allowed mediums, sources that never repeat the medium, and a campaign name built from fixed fields such as market, objective, theme and period.
Copy the template, cut its lists down to the channels the business will use first and keep a register of every campaign name issued, so that links are built from the register rather than typed. Where Google Ads auto-tagging is on, the template advises leaving paid search links untagged. A Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably. written before the first tagged link leaves the building avoids months of reports in which one channel appears under several spellings.
Write a one-page measurement plan
A measurement plan records what counts, where each number comes from and who reads it. The measurement plan guide includes a minimal version for a small business that fits on one page: the objective, the KPI and its source of truth, the events that feed it, the rule for when an action counts, the diagnostics, the naming rule, the attribution stance, the reporting rhythm and a test conversion from each channel before any spend. The measurement plan framework explains the structure behind it.
Fill it in with the key events from step three and the conventions from step seven. A new business has no history, so the plan records each target as an estimate, with the date it will be replaced by a measured figure; the guide to marketing decisions before you have data shows where those first estimates come from.
Keep the access and ownership register current
The register is only useful while it is true. Update it on the day someone joins, leaves or changes role. Remove former staff, freelancers and agencies from every account, which the social page checklist lists among its access checks, and confirm that recovery details still point to the business. Add each ad account when it is created, with the same columns.
Review the whole register at a fixed point, such as the start of each planning cycle, and whenever a supplier relationship ends. A register that someone checks on a schedule catches the forgotten admin before it becomes a problem; one that is updated only when something goes wrong records the problem after the fact.
Review the set before the first spend
Before any money goes on advertising, walk through the set as if you were a new person joining the business. Can you find every account in the register and log in through a business-owned route? Does a test enquiry from the website show as a key event in analytics and in the business's own records? Do the listing, the profiles and the website show the same name, address and phone number? Is there a record behind every address on the list? Does a test link built from the naming convention arrive in analytics with the expected source, medium and campaign? Does the measurement plan say what the first campaign will be judged on?
Fix anything that fails before spending, because a campaign launched on a broken base spends its first weeks producing numbers nobody can trust. Then hand over to the platform pages, starting with the new Google Ads account tutorial if paid search comes first.
An upholstery workshop's first month (illustrative)
Mossgable Upholstery's account register before its first ad
Mossgable Upholstery, an invented workshop that re-covers chairs and sofas and makes cushions to order, opens its first premises. The owner plans to start search ads in week five and uses the first month to set up the layer beneath them. A web designer builds the site; everything else the owner does in short sessions.
| Item | Owning login | Who else has access | Recovery details | Set up |
|---|---|---|---|---|
| Domain and website host | Business role address | Web designer, editor, removed on day 28 | Business phone and role address | Day 1 |
| Domain email (role address and owner's address) | Business admin login | None | Business phone | Day 1 |
| Analytics property | Business role address | Web designer, editor, removed on day 28 | Business role address | Day 4 |
| Consent banner tool | Business role address | Web designer, editor, removed on day 28 | Business role address | Day 4 |
| Business listing | Business role address | Workshop assistant, manager | Business phone | Day 6 |
| Image-led social profile | Business role address | Workshop assistant, editor | Business phone | Day 7 |
| Community social profile | Business role address | Workshop assistant, editor | Business phone | Day 7 |
| Email platform | Business role address | None | Business role address | Day 9 |
| Campaign and link register | Business shared drive | Workshop assistant, editor | Shared drive owner | Day 10 |
Analytics records three key events: enquiry form sent, call link tapped and fabric sample request sent. Each is defined in the one-page measurement plan, with the rule that an enquiry counts as a lead only when the owner replies with a quote. The consent banner holds the analytics tag until a visitor chooses, and the plan notes that reports cover consenting visitors only.
The listing and both profiles copy the name, address and phone number from one line in the register. The enquiry form and a sign-up card at the counter offer a separate tick box for news about fabric samples and workshop open days, and the email platform stores the source, date, wording and choice for each address. By day 30 the list holds 41 addresses, every one with a record.
The review in week four finds two faults. The phone number on the community profile has two digits transposed, and the web designer still holds editor access to analytics after handover. Both are fixed the same day, and the first search campaign launches in week five with a test enquiry visible in analytics and in the owner's enquiry log.
Common mistakes
- Opening accounts under a personal or supplier login. The account, its history and its data leave with the person.
- No register. Nobody knows which accounts exist, who can reach them or how to recover them.
- Installing analytics after the first spend. The first campaign has no baseline and its results cannot be judged.
- Tracking everything and defining nothing. A few key events with written definitions beat dozens that nobody can explain.
- Adding tags before deciding on consent. Each tag added afterwards has to be retrofitted to a decision that should have come first.
- Details that differ across listings and profiles. One canonical record, copied everywhere, prevents it.
- A contact list with no consent records. Addresses that cannot show what the person agreed to are a liability, not an asset.
- Typing links by hand. Without a naming convention and a register, one channel appears under several names in every report.
- Leaving former suppliers with access. Remove it on the day the work ends, and check the register on a schedule.
