You can measure visits from marketing campaigns without analytics cookies by adding UTM parameters to your links and collecting them when a visitor lands. The important limit is attribution: reading a campaign from the current URL does not, by itself, connect that campaign to a purchase a week later or on another device.
This guide uses Databuddy to show the setup and the checks to run before you rely on a campaign report. Databuddy uses browser storage even though it does not use analytics cookies, so review your consent requirements before enabling it.
1. Decide which campaign question you need to answer
Start with a concrete question, such as “Which newsletter brought visits to our pricing page?” Landing-page campaign measurement can answer that with a tagged destination URL and a pageview.
“Which campaign led to a paid subscription?” needs a confirmed conversion event and a supported way to connect that event to the campaign. A button click is not a completed purchase. Cross-session and cross-device attribution require additional design and can change the personal data you process.
Write down the conversion definition and attribution window before comparing campaign results.
2. Build a tagged destination URL
For a newsletter linking to a synthetic example site, use:
https://example.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=autumn_launch&utm_content=pricing_link
Use the fields consistently:
| Parameter | What it identifies | Example |
|---|---|---|
utm_source | The publication, platform or partner sending traffic | newsletter |
utm_medium | The channel type | email |
utm_campaign | The campaign shared across its links | autumn_launch |
utm_content | A creative or link variation | pricing_link |
utm_term | A paid keyword or other planned campaign label | analytics_tools |
Keep a shared naming sheet, use lowercase consistently, and encode spaces or special characters with a URL builder. Do not put email addresses, customer IDs, access tokens or other personal information in campaign labels. URLs can appear in browser history, server logs and shared messages.
Use UTMs on inbound campaign links. Tagging links between pages on your own site can make internal navigation look like a new acquisition campaign.
3. Install the tracker once
Create a website in Databuddy, copy its website ID, and follow the installation guide. For a site that accepts a script snippet:
<script
async
src="https://cdn.databuddy.cc/databuddy.js"
data-client-id="YOUR_WEBSITE_ID"
></script>
Replace the placeholder and install the script once per page. If your configuration requires consent, use your consent manager to load the tracker only after the relevant consent. The async attribute changes loading behavior; it does not implement a consent decision.
Databuddy collects selected campaign parameters separately from the cleaned page URL. A page URL with its query string removed therefore does not mean the campaign parameters were discarded. Its tracker uses localStorage for a visitor ID and sessionStorage for session state; see how collection and privacy work.
4. Verify the landing visit before spending on the campaign
- Create a test link with a distinctive campaign value such as
utm_campaign=qa_autumn_launch. - Open the link in a browser where your permitted tracking configuration can run. Keep the consent behavior you intend to use in production.
- Check that redirects preserve the UTM parameters on the landing URL.
- In the browser Network panel, confirm the tracker loads and the analytics request contains the expected campaign fields and website ID.
- After processing, open that website's dashboard, select the test date, and check the UTM source, medium and campaign breakdowns.
- Navigate to an untagged page and check what the report records. Do not assume the original UTM values persist into later visits.
Databuddy's browser tracker reads UTM values from the URL; it does not persist those UTM fields in its stored advertising-click parameters. Establish the attribution shown by the report through a test journey rather than treating visitor storage as a guarantee of campaign continuity.
5. Add and test a real conversion
Use a confirmation page or a custom event emitted after the action succeeds. For example, record signup_completed after the application confirms account creation. For a form, use the form provider's success callback; a generic submit listener measures an attempt.
Follow the event-tracking reference, then complete a synthetic test journey from the tagged landing page to the confirmed action. Check both that the event arrived and that the campaign filtering or funnel gives the interpretation you expect. If the association is unavailable, report campaign visits and total conversions separately until you implement and verify the required attribution.
Troubleshooting missing or misleading UTMs
| Symptom | Check and recovery |
|---|---|
| Campaign is missing | Confirm the final landing URL still has the parameters and that tracking ran after the required consent. |
| Campaign names split into separate rows | Standardize capitalization and spelling for future links; document historical differences. |
| One visit produces duplicate pageviews | Remove a duplicate installation in the theme, plugin or tag manager. |
| Conversion appears without a campaign | Test navigation, session boundaries and the report's attribution behavior. Do not infer attribution from matching totals. |
| Browser request is blocked | Inspect consent, privacy preferences, content security policy and network errors. Do not bypass a visitor's refusal. |
Can cookieless UTM tracking replace an advertising pixel?
Not automatically. Measuring a campaign in your analytics dashboard is different from sending conversions to an advertising platform for bidding or audience matching. Assess that integration and its consent requirements separately.
Start with a tagged link, a verified landing visit and one confirmed conversion. Expand the attribution model only when those checks show that it answers a decision you need to make.
For a WordPress site, pair this measurement plan with the installation and verification walkthrough. Teams applying the same campaign conventions across client sites can use the agency analytics comparison to plan access and reporting.