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

Send more data via the image.gif through URL parameters #209

Closed
adriaanvanrossum opened this issue Jan 15, 2020 · 3 comments
Closed

Send more data via the image.gif through URL parameters #209

adriaanvanrossum opened this issue Jan 15, 2020 · 3 comments
Labels
customer request

Comments

@adriaanvanrossum
Copy link
Contributor

@adriaanvanrossum adriaanvanrossum commented Jan 15, 2020

One of our customers asked for a feature request and I think it's great:

You provide the alternative tracking code <img src="https://api.simpleanalytics.io/hello.gif" alt=""> in the "noscript" tag, which is great. Obviously, this will be used for users who have JavaScript disabled. And it could even be used for companies that are handling extremely sensitive data and don't want to allow third-party JavaScript. Browsers and countries can be collected via the image-based solution as well.

But today, it's more and more common to restrict how the referrer header is sent (to other origins, at least). One example of such a restriction is the HTML tag <meta name="referrer" content="origin"> that may be used in the "head" section of a document.

How does your image-based (1x1 GIF) tracking code work with such restrictions? I imagine the referrer header is the only way you can associate the recorded data with the correct account or site, right? If the referrer header is not sent (or trimmed), tracking does not work.

Couldn't you allow for the visited URL to be specified explicitly, instead of just accepting it implicitly from the referrer header?

<img src="https://api.simpleanalytics.io/hello.gif?url=https://www.example.com/visited/page?supplied=params" alt="">

The explicit value could even be used as a fallback only, i.e. when the implicit value is not available. Google Analytics includes the account's or site's unique tracking ID in the code as well, which simplifies associating visits with sites.

Let's put this on our roadmap and combine it when we work on our API. It's a nice Friday afternoon project.

@adriaanvanrossum adriaanvanrossum added the customer request label Jan 15, 2020
@adriaanvanrossum adriaanvanrossum added this to Features & bugs in Public roadmap via automation Jan 15, 2020
@jakejarvis
Copy link

@jakejarvis jakejarvis commented Feb 1, 2020

This would be great, since the GIF is the best way I could figure out how to collect stats from my AMP pages! (They're very picky about scripts.)

https://amp.dev/documentation/components/amp-pixel/

@adriaanvanrossum
Copy link
Contributor Author

@adriaanvanrossum adriaanvanrossum commented Feb 3, 2020

Ah cool, this makes the use of it more clear.

Public roadmap automation moved this from Features & bugs to Implemented Apr 24, 2020
@adriaanvanrossum
Copy link
Contributor Author

@adriaanvanrossum adriaanvanrossum commented Apr 25, 2020

This is now implemented!

See our documentation: https://docs.simpleanalytics.com/without-javascript

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer request
Projects
Public roadmap
  
Implemented
Development

No branches or pull requests

2 participants