Manage tracked property domains and URIs

[jwjimmy]

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...

[jwjimmy]

You need to figure out: do you want to pass in estate id via the image as a path param? Or do you want to pass in a string containing URI, if possible?

It looks like you want separate tracking pixels for emails vs websites...

Do some testing before you commit more code.

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. Also, can you even pass info through a path param? TEST THIS FIRST.

[jwjimmy]

Can you pass info through a path param? Yes. Do you want to pass in estate_uuid via the image as a path param? Yes.

Find some other way to get URL.