Support TaggingDocs

TaggingDocs is a free, open-source resource maintained by practitioners in their own time. If the site has saved you hours of debugging, helped you set up a tracking implementation correctly, or kept you from making an expensive mistake — consider supporting the project.

Sponsor on GitHub

The best way to support TaggingDocs financially is through GitHub Sponsors. Sponsorships directly fund writing time, hosting costs, and keeping content current as platforms change.

GitHub absorbs all payment processing fees, so 100% of your sponsorship goes to maintaining the project.

Tip

Even small monthly sponsorships make a meaningful difference. A $5/month sponsorship helps cover hosting and domain costs. A $25/month sponsorship funds dedicated writing time for new articles.

What funding covers

Writing time

Each article takes hours of research, testing, and writing. New GA4 features, sGTM updates, and platform changes need to be documented as they ship.

Hosting & infrastructure

Domain registration, hosting, build pipelines, and keeping the site fast and available.

Tool subscriptions

GA4 properties, GTM containers, sGTM instances, ad platform test accounts, and BigQuery access used to verify every code example and configuration.

Independence

Financial support from the community means TaggingDocs never needs to accept vendor sponsorships that could compromise editorial independence.

Support without spending

Not everyone can contribute financially, and that is completely fine. Here are other ways to help:

Star the repo — A star on GitHub helps with visibility and signals to others that the project is worth checking out.

Share articles — If an article helped you, share it with your team or on social media. Word of mouth is how most people find TaggingDocs.

Fix what you find — Every page has an “Edit page” link. Spotted a typo, an outdated screenshot, or a broken code example? Fix it directly.

Contribute content — Have expertise in an area we have not covered? Open a pull request. Some of the best content comes from practitioners who just solved a hard problem and want to document the solution.

Report issues — Found something wrong or missing? Open a GitHub issue. Even a one-line report helps us prioritize what to fix next.