Your campaign report shows clicks. Your inbox shows inquiries. Your payment records show orders. Can you connect them without guessing?
To track where leads come from, carry consistent campaign labels from the incoming link to the inquiry record, then link that record to a confirmed outcome. Keep visits, leads and paid orders as separate events. Keep unknown sources visible.
This guide is for a small expertise business running its first content campaigns. You will build a simple naming card and test one route before you add more dashboards.
Decide what each number means
Write these definitions before comparing channels:
- Visit: A recorded visit under the measurement tool's rules. Consent, blocking and filters can affect what is recorded.
- Inquiry: A valid request successfully saved by the form or CRM. A button click alone does not count.
- Qualified inquiry: A request that meets your written fit criteria. Decide those criteria before evaluating a campaign.
- Paid order: A payment confirmed by the payment system and matched to the right order. A thank-you page view alone does not count.
Keep failed, test, duplicate, cancelled and refunded records distinct. If your reports cannot separate them yet, state that limit before making a budget decision.
Give each shared link a naming card
Google Analytics documents UTM parameters for identifying referring campaigns. The core labels describe the source, medium and campaign; an optional content label distinguishes a particular creative or link.
Here is a fictional naming card for a LinkedIn field guide:
- Source: linkedin
- Medium: organic_social
- Campaign: lead_journey_oct26
- Content: stop_rule_post_01
Use the same spelling every time. Parameter values are case sensitive in Google Analytics. A campaign named “Lead_Journey” in one link and “lead_journey” in another can fragment your report.
UTM labels describe the link you distributed. They do not prove that the platform caused a sale or that every visitor saw the same journey. Only use labels that your actual reporting setup captures.
Preserve the difference between first touch and latest touch
In a fictional journey, someone first arrives from a LinkedIn article, returns through a newsletter and later submits an inquiry. Which channel gets credit?
That depends on the question and the attribution model. Do not silently replace the first recorded source with the latest campaign and call it complete history.
For a small system, consider these separate fields:
- First recorded touch: The earliest source your system actually captured, with a timestamp. It may not be the person's first real exposure.
- Latest recorded campaign: The most recent campaign your capture rule recognizes before the inquiry.
- Inquiry reference: A stable record identifier used for an internal match to the eventual outcome.
- Self-reported source: An optional answer to “How did you hear about us?” Keep it separate from observed tracking.
This is a suggested operating model, not a statement that your CRM already has these fields. Choose a retention period, consent approach and access rules appropriate to your business. Keep the system small enough to maintain.
Keep identity out of campaign URLs
Do not put a person's email, phone number, name or private customer details in UTM values. URLs can appear in analytics, logs, shared messages and browser history.
Google's Analytics policy prohibits sending personally identifiable information to Analytics, including through URLs and campaign dimensions. Keep any permitted identity-to-order matching inside an appropriately controlled business system. A public link is the wrong place to carry private information.
Test one complete route
- Open your labelled link: Use a controlled test visit. Confirm that the intended page loads and relevant parameters survive redirects.
- Take the intended action: Submit a clearly labelled fictional inquiry only in an approved test flow. Record its actual saved reference.
- Inspect the saved source: Check the record, not just the page URL. Compare the source, medium and campaign with the naming card.
- Test a return visit: Use a different campaign label. Check that first and latest touch follow the rules you chose.
- Match an outcome: In a payment sandbox, connect a confirmed test payment to its order and inquiry. Test failure and duplicate callbacks too. Do not make a live charge to prove a tracking idea.
- Check an unlabelled visit: Confirm that missing evidence stays unknown or is classified under your documented rules. Do not assign it to your preferred channel.
If payment testing or source persistence is unavailable, stop your claim at the last verified step. “Campaign visit captured” is useful evidence. It does not establish source-to-sale attribution.
Use a report that answers a decision
Start with one row per campaign and a consistent reporting period. Show recorded visits, valid inquiries, qualified inquiries and confirmed paid orders. Include test exclusions and the share of inquiries with unknown source.
Calculate a conversion rate only when numerator and denominator describe the same eligible group and period. If you do not have the required records, leave the rate unavailable. A small sample is a reason to inspect the journey, not a reason to announce a winning channel.
For organic search specifically, read how Search Console and GA4 work together. Search visibility and on-site actions answer different questions.
Your first useful result
Spend 20 minutes on one campaign. Write its naming card, the intended visitor action and the last step you can verify. Record every remaining gap as unknown. You now have a repair plan, rather than a dashboard full of confident labels.
Map the gaps: Write down the route on paper, one step at a time. If the gaps span several tools, a Hub Fit Call is the place to talk through what a connected setup would cover.
Sources and scope
- Google Analytics: Collect campaign data with custom URLs. Parameter meanings, naming consistency and campaign reports.
- Google Analytics: Avoid sending personally identifiable information. URL, title and campaign-data precautions.
Sources checked 24 October 2026. The naming card, field model, fictional journey and test sequence are Pro Mind Hub's practical synthesis. They do not establish that tracking, consent, CRM persistence or payment attribution is already configured on your site.
