For most people s.cmdchallenge.com/count.js
should be fine, but there are also
stable versions if you want to use subresource integrity (SRI). This will verify
the integrity of the script to ensure there are no changes, and browsers will
refuse to run it if there are.
You won’t get any updates, with this – the versioned script will always remain
the same. Any existing version of count.js
is guaranteed to remain compatible,
but you may need to update it in the future for new features.
No changes
<script data-goatcounter="https://s.cmdchallenge.com/count"
async src="//s.cmdchallenge.com/count.v4.js"
crossorigin="anonymous"
integrity="sha384-nRw6qfbWyJha9LhsOtSb2YJDyZdKvvCFh0fJYlkquSFjUxp9FVNugbfy8q1jdxI+"></script>
navigator.sendBeacon
when available.<script data-goatcounter="https://s.cmdchallenge.com/count"
async src="//s.cmdchallenge.com/count.v3.js"
crossorigin="anonymous"
integrity="sha384-QGgNMMRFTi8ul5kHJ+vXysPe8gySvSA/Y3rpXZiRLzKPIw8CWY+a3ObKmQsyDr+a"></script>
start
and end
in the visitor counter.0.0.0.0
<script data-goatcounter="https://s.cmdchallenge.com/count"
async src="//s.cmdchallenge.com/count.v2.js"
crossorigin="anonymous"
integrity="sha384-PeYXrhTyEaBBz91ANMgpSbfN1kjioQNPHNDbMvevUVLJoWrVEjDCpKb71TehNAlj"></script>
data-goatcounter-settings
on the script
tag.if
since some minifiers can’t deal with “dangling else”
well (the code is correct, it’s the minifier that’s broken).<script data-goatcounter="https://s.cmdchallenge.com/count"
async src="//s.cmdchallenge.com/count.v1.js"
crossorigin="anonymous"
integrity="sha384-RD/1OXO6tEoPGqxhwMKSsVlE5Y1g/pv/Pf2ZOcsIONjNf1O+HPABMM4MmHd3l5x4"></script>
Feel free to get in touch if you’ve got any questions or having any problems; a lot of times they can be resolved without too much problems.
Ways to contact me: show