Conversation
|
So this is something that we might ... put in an incoming auth URL's query string? |
There was a problem hiding this comment.
pretty_name might be a bit verbose; (I hope it's pretty, but at least it'll be a name).
Of course, slug is fine, especially if we might be putting these in URLs. (code, et al, work too.) Regardless, you might want to enforce sluginess with a SlugField.
|
Sure. We may keep more detailed information in the query string, but when we create a ClientAppUser record we decide on a bucket, represented by the FBAuthSource. |
|
I'm not sure I understand "we may keep more detailed information in the query string", but yeah, I'm just asking how we might decide on the bucket – from some information stored on the campaign? from an auth query string param? |
|
Either the URL or a campaign could work. I think the flexibility afforded by encoding in the URL would be preferable to creating different campaigns for different sources, if making it work doesn't end up being too tough. |
|
Sure. Also, in case there's as much overlap as I imagine there is, we have the idea of |
We want to record the referral source of the authorized users we get (email, Facebook, etc). That'll be something to add later, but for now I wanted a convenient place to put it for the Reports page.