Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs about plausible #219

Open
matheusgr opened this issue Dec 11, 2023 · 0 comments
Open

Add docs about plausible #219

matheusgr opened this issue Dec 11, 2023 · 0 comments

Comments

@matheusgr
Copy link
Contributor

See: https://www.deco.cx/en/blog/analytics.md

Also, add this information bellow:

--

Google ( with a capital G ) is your organic traffic and google ( lowecase g ) is your paid traffic. Same with Facebook vs facebook, Bing vs bing etc.

It's important to tag your link with a lowercase letter ( i.e utm_source=google ) so you can differentiate them because if you tag the links with a capital letter ( i.e utm_source=Google ) you'll merge your paid traffic with your organic traffic.

Also, another way to differentiate paid vs organic traffic is by the favicon of the source. For example: Google organic has the Google logo, while Google paid has a chain link icon.

That said, I don't see any "google" source in your client's dashboard. However I can see a "cpc" source which should be the Google Ads traffic.

Also, another thing that's important to note here:

You should not use the autotagging feature in Google Ads ( or other platforms that allows this ) because by default, Plausible strips all query parameters for privacy purposes.

GCLID/FBCLID etc are unique identifiers and illegal according to the GDPR unless sites get user consent to track them. Plausible is focused on being GDPR compliant and privacy first out of the box so we don't have any features that have to be put behind a cookie consent banner.

Only the ref , source , utm_source , utm_medium , utm_campaign , utm_content and utm_term parameters are supported. If you tag your paid campaigns with these, it's then possible to filter your dashboard by any custom event and see which of the parameters drove the most conversions. Perhaps you can use these to tag your Google paid campaigns too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant