BrandMochiArticlesBrand LogBrandMochi home

Market

Prepare your November campaign links with a UTM checklist

Label organic Facebook, newsletter and partner links, test the destination, and review enquiries in GA4. Includes a fictional bicycle-workshop example.

Before sharing a November offer, give each promotional link a consistent label and test where it sends a customer. A small link register lets you connect the post, its destination and the enquiries you review later. You can start with a spreadsheet and the analytics already installed on your website.

This guide uses a fictional bicycle workshop offering winter service appointments. The campaign names, dates and links below are examples. No traffic or sales results are claimed. Product documentation was checked on November 1, 2026.

Choose one customer action for the campaign

Write down what a successful visit should accomplish. For the workshop, the action is a completed service enquiry. The destination is the service page with the booking form. A social post about winter maintenance should lead to that page, where customers can see the service area, what the appointment covers and how to request a slot.

Assign someone to check that destination before publication. Confirm that the offer described in the post matches the page. Open the form on a phone and follow the confirmation path. Record which team member will read incoming enquiries and when. These checks give the campaign a usable route from interest to a response.

Create a small naming rule

UTM parameters are labels added to a destination URL. Google documents source, medium and campaign fields, plus a content field for distinguishing placements. Values are case-sensitive. The labels appear in Analytics when collection is working. See Google’s campaign URL guidance.

For this example, use lowercase values and one campaign name, november_service_2026. Keep the spelling fixed for the whole offer. Give each placement a content label you will recognise during review. Use your existing organisation’s naming convention when one is already in place.

Placementutm_sourceutm_mediumutm_content
Organic Facebook Page photofacebooksocialworkshop_photo
Your own newsletternewsletteremailservice_button
Local cycling club newslettercycling_clubemailmember_note
Suggested labels for the fictional workshop; all three use utm_campaign=november_service_2026.

Source identifies the publisher; medium describes the route. Using email for both newsletters preserves that shared route while the source names distinguish them. Google’s default channel definitions describe how Analytics groups traffic. A custom label such as community_update does not guarantee placement in your preferred default channel. Check the resulting source and medium during testing.

The workshop’s illustrative Facebook destination is https://example.com/service?utm_source=facebook&utm_medium=social&utm_campaign=november_service_2026&utm_content=workshop_photo. The example.com domain is a documentation placeholder; replace it with your own working destination before sharing.

Use Google’s Campaign URL Builder or your established link tool. If the destination already contains a question mark and a parameter, append additional parameters with an ampersand. Keep an existing page anchor at the end of the URL. Open the finished link to confirm that it still selects the intended service, location or booking option.

Maintain one register row per placement with the publication date, campaign name, final tagged URL, public post or newsletter reference, owner and review date. For the workshop, a November 3 Facebook photo and a November 5 newsletter get separate rows. If the photo caption changes later, leave a dated note so the review has context.

Share the final link with any partner responsible for publication. Ask them to retain it through their newsletter or redirect system. A screenshot or copy of the published placement makes it easier to investigate a later discrepancy. Use campaign tags on external promotional links; keep your own navigation links focused on the visitor’s next page.

Keep personal information out of the labels

Use placement descriptions such as member_note. Customer names, email addresses, phone numbers and private account references belong in the appropriate customer system. Google’s guidance on personally identifiable information specifically covers information that reaches Analytics through URLs and other fields.

A partner’s public business name is enough to describe a placement. You do not need a separate tracking URL for every recipient. Review the whole destination too: a booking system might append customer details after a form submission. Ask your website maintainer to check what your analytics receives, and follow your site’s applicable consent requirements.

Test the visit and the enquiry separately

  1. Open the exact finished link on a phone. Check the page title, offer details and form. Follow redirects and confirm that the campaign parameters reach the destination that collects analytics.
  2. With the site’s consent settings respected, make an identifiable internal test visit. Use your analytics testing tools to check collection. Note the date and time in the register so the team can recognise test activity.
  3. Submit one clearly labelled test enquiry with permission from the person handling the inbox. Confirm that it reaches the expected destination and produces the intended confirmation. Remove or label the test record in your operational reporting.
  4. Check the event used to count enquiries. Confirm that it fires after a successful submission, and that a reload or another button click does not create an extra successful enquiry. Ask the website maintainer to correct duplicates before relying on the count.

For a collection check, use Realtime or ask your website maintainer to enable DebugView for the test device. Google’s setup troubleshooting guide describes both tools. Verify event delivery there, then review campaign attribution in the acquisition report after processing.

Google lists generate_lead for a submitted form or request for information in its recommended events documentation. These recommended events require implementation. Adding campaign labels to a URL does not install enquiry tracking. A booking provider on another domain also needs its measurement setup checked separately.

Review the campaign with the enquiry record beside it

In GA4, open Reports, then Acquisition and Traffic acquisition when that report is available in your navigation. Choose the campaign dates and inspect Session source / medium and Session campaign. Google’s Traffic acquisition report guide explains these session-level dimensions and notes that an editor can restore a missing report.

Use the same date range in the workshop’s enquiry record. Record visits attributed to the campaign, successfully measured enquiries and the enquiries the team has reviewed for service fit. Keep each definition visible. A form submission can be a test, a duplicate or a request outside the service area, so the operational review adds context to the analytics count.

Write one decision from that review. If visitors repeatedly ask whether cargo bikes are included, clarify the service page before the next post. If the club newsletter used an outdated destination, send the corrected link and record the repair. Choose the change supported by the evidence available, then set the next review date.

Leave room for incomplete attribution

Treat campaign labels as evidence about a recorded visit. A person can forward a tagged newsletter link to a friend, so its source still describes the original placement. Someone can read the Facebook post and later telephone the workshop. Consent choices, blocked analytics and visits across devices also limit the recorded picture. A low count is a reason to inspect the full enquiry path before drawing a conclusion about demand.

An optional “How did you hear about us?” question gives the team another source of context. Keep that answer alongside the enquiry rather than inserting it into a tracking URL. Compare the customer’s account with the campaign record when useful, and retain uncertainty where they differ.

For your next promotion, finish one register row, test its link and confirm who handles the resulting enquiry. Those three checks leave you with a destination customers can use and a record your team can review after publication.