jwjimmy/counsel

A web tracker for low-volume web properties.

counsel's Issues

Test tracking pixel behavior in different embedded mediums

Try embedding a tracking pixel in facebook and see what happens (facebook probably serves its own stored version of the image)
Try embedding a tracking pixel in tumblr and see what metadata you get.

Support multiple users

• Design onboarding flow #11
• Views for estate visits #12
• Permissions for estate views

Button to generate a pixel

Push notifications

On visit. How cool would that be?

Design onboarding flow

Android app download should trigger automatic user creation.

Devices should belong to users

How to extend the Device model:
https://django-fcm.readthedocs.io/en/latest/extending_device.html

This is an example of someone extending the Device model to have User as a foreign key: Chitrank-Dixit/django-fcm#29

Make request.META json-serializable

Views for estates

• Automated geolocation lookup of IPs

Log URI for DIRECT visits

This would be way more useful.

Integrate push notifications with estates

Continuing the good work done here: #2

Manage tracked property domains and URIs

Here's the idea:
We'll store estates in the Estates model.
You will now be able to specify estate via /requests/passive/<estate uuid>.
The uuid will be of the form a8098c1a-f86e-11da-bd1a-00112444be1e and be stored via UUIDField as a secondary key. (I might regret this later... but this is for low volume tracking so chill out!!)

Estate:

• uuid UUIDField (pk)
• estate_type IntegerField
• name CharField
• description CharField
• created_at DateTimeField

(incomplete. Wouldn't it be nice to formalize gmail and github estates?)

In the view, we log different info based on estate type.
If estate type is DIRECT then HTTP_REFERER will tell us the URL of the estate.
If estate type is GITHUB then we can fill in Visit.estate with the supplied user/repo info contained in the string.
If estate type is GMAIL then...

User identities

Eventually you'll want to extract some notion of user identity from the metadata.
Once you figure this out, it would be great to track self-hits in a separate table, or otherwise filter out self-hits for your own properties. You would need a safe way to register your own fingerprint.