Gather information about user location

[reginafcompton]

The tool needs to gather information about user location for analytics. (In part, this will help the city track "hotspots" – zones of activity where people facing homelessness are – and it will help CSH refine their marketing strategy.)

Currently, we only ask the user if they are in the city or the suburbs. We can get more precise location information by doing the following:

Make the trigger word a code that corresponds with a location.

The code can be either a specific code or a code that corresponds with a group of codes. (Stephanie wants us to do whatever is easiest.) In either case, we'd need to create anywhere from 5-100+ Tree objects, each with a different trigger word, but then one of three root states, depending on if it's a city or suburban code.

Here are the three trigger words with corresponding root states:

(1) "connect," i.e., the user does not provide a code, since the user did not have access to marketing materials (e.g., they found the website online somehow) or the user saw CSH's generic marketing materials. This leads to a survey with the question about "are you in the city or suburbs."

(2) a code for a location in the city. This leads to the a survey that assumes the user is in the city and thus omits the question about "are you in the city or suburbs."

(3) a code for a location in the suburbs. This leads to a survey that assumes the user is in the suburbs and thus omits the question about "are you in the city or suburbs."

I will need to re-work the Tree logic slightly, but I think it should be relatively painless to implement.

[reginafcompton]

Update on suburban partners! They do not want to use numerical codes. Instead, they will invite users to text the name of the suburb – or they will use "connect" (i.e., not track location data at all).

Stephanie will let us know by January 31.