Loading tutorials…
Loading tutorials…
Plausible does not have a native Google Ads integration like GA4 does. It tracks UTMs on inbound links, full stop. Get the UTM templates right and Plausible delivers cleaner ad attribution than GA4. Get them wrong and your spend looks attributed to '(direct) / (none).'
Who this is forOwners running Google Ads (or any paid channel) who use Plausible as their primary analytics tool. Especially relevant if you came from GA4's auto-import and are surprised Plausible does not do the same — it is a different attribution model entirely.
What you'll need
Step 1
Plausible reads UTM parameters on inbound URLs. It does NOT pull data from Google Ads, push conversions to Google Ads, or do auto-attribution beyond UTM matching.
WHAT PLAUSIBLE DOES: reads utm_source, utm_medium, utm_campaign, utm_content, utm_term from inbound URLs. Categorizes traffic into Channels (Paid Search, Organic, Direct, Social, Referral, etc.) based on those values.
WHAT PLAUSIBLE DOES NOT DO: pull cost/CTR/impression data from Google Ads (no Google Ads API integration). Push conversions back to Google Ads (no Conversion Import like GA4). Multi-touch attribution (Plausible is last-non-direct click attribution).
For Smart Bidding to work on Google Ads, you STILL need the Google Ads conversion tag firing on your site OR the GA4 → Google Ads import path. Plausible is your reporting and dashboarding tool; Google Ads still needs its own conversion signal.
This is fine for most teams. Plausible gives you clean dashboards on what TRAFFIC came from where; Google Ads remains the optimization layer. Use both.
If you need single-source attribution that also drives Smart Bidding optimization, GA4 is still the right choice for ad-heavy workflows. Plausible is for owners who prioritize privacy + simplicity + dashboard clarity over ad-platform integration depth.
Step 2
Google Ads → Admin → Account settings → Auto-tagging: ON. This adds GCLID to ad-click URLs. Plausible ignores GCLID but it's required for the conversion tag.
Sign in to Google Ads. Click Admin (left sidebar) → Account settings.
Find Auto-tagging. Toggle ON if not already.
Auto-tagging adds ?gclid=... to every ad-click URL. The Google Ads conversion tag uses this to attribute conversions back to ad clicks.
Plausible IGNORES gclid (it is not a UTM parameter). But you still want auto-tagging ON because the Google Ads conversion tag needs it.
This is a one-time setting. Once on, every ad clicks gets a gclid added automatically.
Step 3
Google Ads → Account/Campaign/Ad-group level Tracking Templates. Use ValueTrack parameters so utm_campaign/utm_content auto-fill per ad.
Google Ads → Admin → Account Settings → Tracking. Or set per-campaign in Campaign Settings → Additional URL options.
Tracking template: {lpurl}?utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_content={adgroupid}&utm_term={keyword}
{lpurl} is the placeholder for the ad's final URL. {campaignid} resolves to the Google Ads campaign ID at click time. Same for {adgroupid} and {keyword}.
Or for human-readable values, use {_campaign} and {_adgroup} (account-level custom parameters you define).
Save. From this point forward, every ad click URL will include the UTM params.
For Performance Max and Display campaigns, ValueTrack {keyword} resolves to nothing — that is expected. Use {placement} or {creative} instead where it makes sense.
Step 4
Plausible categorizes traffic by utm_source + utm_medium. Use exact canonical values so Channel rules apply correctly.
Canonical UTM values Plausible expects (matching its Channel rules):
- Paid Search: utm_source=google, utm_medium=cpc (or paid_search)
- Paid Social: utm_source=facebook|instagram|tiktok|linkedin, utm_medium=paid_social (or cpc)
- Organic Search: NO UTM needed — Plausible detects from referrer
- Organic Social: utm_source=facebook|instagram, utm_medium=social
- Email: utm_source=newsletter|drip|brevo, utm_medium=email
- Affiliate: utm_source=AFFILIATE_NAME, utm_medium=affiliate
Use these exact values. utm_medium=paid_search is treated differently from utm_medium=cpc — pick one and use it everywhere.
Document your UTM convention in a team wiki page. Every new ad campaign, email blast, and affiliate link references the canonical doc.
Step 5
Use Google Ads ad preview tool. Click the preview. Land on your site. Check Plausible Realtime + URL params.
In Google Ads, navigate to a campaign → Ads → click any active ad.
Click the three-dot menu → View ad. This opens a preview of the ad.
Click the ad in preview mode. You will be redirected to your site with the full UTM-tagged URL.
Check the URL bar — you should see ?utm_source=google&utm_medium=cpc&utm_campaign=... appended.
Plausible → Realtime. Within 30 seconds, your visit should appear with the correct source/medium/campaign in the breakdowns.
Plausible → Sources → Campaigns. The campaign name from utm_campaign should appear within 1-5 minutes.
Step 6
Plausible's default Channel rules cover common cases. For unusual setups (paid sponsorships, programmatic, custom referral classes), you may need custom channel rules.
Plausible has built-in Channel categorization based on utm_source + utm_medium + referrer. Default rules are documented at plausible.io/docs/sources-and-channels.
Default behavior: utm_source=google + utm_medium=cpc → Paid Search. utm_source=facebook + utm_medium=paid_social → Paid Social. No UTM + referrer=google.com → Organic Search.
For unusual channels (e.g. sponsored newsletter mentions, podcast plugs, programmatic display), Plausible does NOT auto-categorize them — they fall into "Other" or "Referral."
Plausible does not currently support fully custom channel rule editing — you cannot define 'utm_medium=podcast → Podcast Sponsorships' as a built-in channel. Work around this by filtering the dashboard by utm_medium=podcast directly.
If channel customization is critical, consider Plausible's API + a custom dashboard, or revisit whether Plausible is the right tool for the level of attribution depth you need.
Step 7
On Plausible Business plan with a Purchase revenue goal: filter by utm_source/utm_campaign and Plausible shows revenue per source.
Once revenue tracking is set up (see tutorial #3), Plausible shows total revenue per source/campaign in the dashboard.
Sources → Channels → click "Paid Search" → see revenue total for paid Google traffic.
Sources → Campaigns → see revenue per utm_campaign value.
This is the moment Plausible becomes a real ad-attribution tool: you can answer "Which Google Ads campaign drove the most revenue this month?" directly in the Plausible dashboard.
Cross-check against Google Ads conversion data. Expect Plausible to show slightly LOWER revenue than Google Ads (because Plausible is last-non-direct attribution and Google Ads is last-click). 5-15% gap is normal.
Common mistakes
Assuming Plausible auto-imports from Google Ads
What goes wrong: You install Plausible expecting cost/CTR/conversion data to flow in like GA4 does. It does not. You stare at the dashboard looking for the missing Google Ads section. There isn't one. Plausible only reads UTM parameters — never queries the Google Ads API.
How to avoid: Treat Plausible and Google Ads as separate tools. Plausible shows traffic + revenue. Google Ads shows spend + CTR + CPC. Cross-reference manually. For owners who want a single source-of-truth dashboard, GA4 is the right tool.
Inconsistent utm_medium values
What goes wrong: Some campaigns use utm_medium=cpc, others use utm_medium=paid_search, others use utm_medium=ppc. Plausible treats each as a separate medium. Your channel breakdown fragments into 6 paid-search rows instead of one.
How to avoid: Pick ONE canonical value per medium (utm_medium=cpc for paid search is the standard). Use it across every campaign in every platform. Document it.
Using ValueTrack IDs instead of names
What goes wrong: Your Plausible dashboard shows utm_campaign = 12345678901 instead of 'Spring Sale 2026 - Search.' You cannot tell which campaign is which without manually mapping IDs to names.
How to avoid: Use the {_campaign} custom parameter at the campaign level in Google Ads with a human-readable name. Or rename your campaigns to make the IDs interpretable.
Uninstalling the Google Ads conversion tag
What goes wrong: You switch from GA4 to Plausible. You uninstall the Google Ads conversion tag thinking 'Plausible covers conversions now.' It does not. Smart Bidding loses its conversion signal. Your CPA inflates 30-50% over the next 14 days.
How to avoid: Keep the Google Ads conversion tag firing on your site regardless of which analytics tool you use. Conversions for Smart Bidding are separate from analytics reporting.
Forgetting to apply UTM templates to all campaign types
What goes wrong: Search campaigns have UTM tracking; Performance Max and YouTube campaigns do not. PMax traffic shows up in Plausible as utm_source=google + utm_medium=cpc only on some clicks — others are direct/none.
How to avoid: Apply tracking templates at the ACCOUNT level so they propagate to all campaign types automatically. Audit per-campaign settings monthly.
Not validating tracking templates after launch
What goes wrong: You set up tracking templates. You launch the campaign. You assume it works. Two weeks later you discover the template had a typo ({_keyword} instead of {keyword}) and all your utm_term values are empty. Two weeks of attribution data is unusable.
How to avoid: After every template change, click a real ad in the preview tool. Inspect the landing URL. Confirm every UTM parameter is populated. Re-validate quarterly.
Recap
Done — what's next
How to install Plausible tracking on any site
Read the next tutorial
Hand it off
UTM hygiene is one of those things that pays back forever but takes a focused day to set up right. A vetted specialist familiar with both Plausible and Google Ads can audit your tracking templates, normalize your UTM convention, set up revenue goals, and validate end-to-end attribution in 1-2 days — typically $200-400 total at $14-16/hr.
See specialist rates
For dashboard reporting on which traffic + revenue came from where, yes. For pushing conversion signals back to Google Ads Smart Bidding, no — you still need the Google Ads conversion tag (or GA4 import). Most teams run Plausible alongside the Google Ads conversion tag and never use GA4.
Plausible uses last-non-direct click attribution and only counts visits where the UTM survives the landing. Google Ads uses last-click and counts the click event itself. A 5-15% gap is normal. Larger gaps mean broken UTMs, redirects stripping params, or referral exclusions misconfigured.
Same approach as Google Ads — set up UTM tracking templates in each platform with your canonical utm_source/utm_medium values. Microsoft Ads has auto-tagging (msclkid) that Plausible ignores; same for Meta (fbclid) and TikTok (ttclid). UTM is the universal language.
Gclid is Google's internal click ID — used by Google Ads conversion tracking and Google Analytics. It is ad-platform-specific and Plausible ignores it. UTM parameters are an open standard (Urchin Tracking Module) that any analytics tool can read. Plausible reads UTMs only.
No. Plausible uses last-non-direct click attribution only. For multi-touch (first-touch, time-decay, linear, position-based), you need GA4, Mixpanel, Amplitude, or a dedicated attribution tool like Northbeam / Triple Whale. Plausible's simplicity is the point — multi-touch is GA4's domain.
Add UTMs to every link in your YouTube video descriptions: utm_source=youtube&utm_medium=social&utm_campaign=video_title. For YouTube Ads, the Google Ads tracking template handles it automatically (utm_medium=cpc, utm_source=google or youtube depending on placement).
Plausible Analytics
Plausible has the simplest install of any analytics tool — one script tag. That's also why it's the easiest to install wrong: pick the wrong script variant, miss the data-domain attribute, or install through GTM without unblocking outbound clicks, and half your tracking silently breaks.
Plausible Analytics
Plausible's goal system is brutally simple — and that simplicity is what makes it powerful. Three types: pageview goals, custom events, and revenue goals. Most owners set up the wrong type, fire too many events, and blow past their plan. This is the discipline that prevents both.
Plausible Analytics
Plausible funnels are deceptively simple — you pick 3-8 goals, click Save, and it draws the chart. The real work is upstream: do the goals exist, are they ordered correctly, and is the funnel actually answering a question the team will act on?
Plausible Analytics
Most GA4 → Plausible migrations fail because owners flip the switch on day 1 and lose historical context. The right pattern is a 30-60 day parallel run: both tools firing, both dashboards monitored, then a clean cutover. This is the playbook.