Platform to influence channelization of customized information to a user

Abstract

Aggregated traveler data may be accessed by subscribers to a content management system. Subscriber data in access requests from one or more subscribers may be used to describe a pool of travelers in the aggregated traveler data that may be concentrated in a geographic location. Location data, temporal data or both, from one or more electronic sources and/or data stores may be processed to determine if a selected traveler will be positioned within a threshold of an allowable distance from an allowable event in the geographic location at a time coincident with an event time window for the allowable event. Selected travelers who meet location and/or temporal parameters may be targeted to receive customized content for events including activities, services, goods, suggestions, and recommendations from subscribers. A subscriber may own a rental property in the geographic location that is rented by a selected traveler.

1 .- 20 . (canceled) 
     
     
         21 . A system comprising:
 computer-readable memory storing executable instructions; and   one or more processors in communication with the computer-readable memory, wherein the one or more processors are configured by the executable instructions to at least:
 extract, from an access data file, access request data and proprietor data; 
 verify proprietor access credential data included in the proprietor data; 
 access, in response to verification of the proprietor access credential data, traveler data regarding a pool of travelers identified by the access request data, wherein individual travelers in the pool of travelers are not within a threshold distance of an event at a present time, and wherein the event is associated with a proprietor represented by the proprietor data; 
 analyze traveler data for a selected traveler of the pool of travelers, wherein the traveler data for the selected traveler represents a prior location of the selected traveler and a current location of the selected traveler; 
 determine, based at least partly on analyzing the traveler data for the selected traveler, that the selected traveler is likely to be positioned within a threshold distance of the event during an event time window associated with the event; 
 generate an event data file comprising data regarding the event; and 
 generate a transmission regarding the event data file prior to a future time at which the selected traveler is expected to be within the threshold distance of the event. 
   
     
     
         22 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least receive, from a computing device of the selected traveler, a time coincidence signal indicating that the selected traveler is likely to be positioned within the threshold distance of the event at a time coincident with the event time window. 
     
     
         23 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least:
 determine a velocity of a computing device of the selected traveler in a direction towards the event based at least partly on location data and temporal data received from the computing device of the selected traveler; and   determine an estimated time of arrival of the selected traveler within the threshold distance of the event based at least partly on the velocity.   
     
     
         24 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least receive, from a computing device of the selected traveler, a locus entry signal indicating that the selected traveler is positioned within the threshold distance of the event. 
     
     
         25 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least analyze one or more of geo-location data for travelers of the pool of travelers, temporal data for travelers of the pool of travelers, or location history data for travelers of the pool of travelers. 
     
     
         26 . The system of  claim 21 , wherein the event relates to one or more of an activity, an item, a service, or a rental property. 
     
     
         27 . The system of  claim 21 , wherein a computing device of the selected traveler is configured to at least execute the event data file. 
     
     
         28 . The system of  claim 21 , wherein the access data file is generated by a proprietor computing device associated with the proprietor. 
     
     
         29 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least:
 extract stay data from the traveler data for the selected traveler, wherein the stay data represents beginning and ending stay dates; and   generate customized content for the event data file based at least partly on the beginning stay date or the ending stay date.   
     
     
         30 . The system of  claim 21 , wherein the one or more processors are further configured by the executable instructions to at least determine a concentration of travelers within a locus, wherein the event data file is generated based at least partly on the concentration. 
     
     
         31 . A computer-implemented method comprising:
 under control of a computing system comprising one or more computing devices configured to execute specific computer-executable instructions,
 extracting, from an access data file, access request data and proprietor data; 
 verifying proprietor access credential data included in the proprietor data; 
 accessing, in response to verification of the proprietor access credential data, traveler data regarding a pool of travelers identified by the access request data, wherein individual travelers in the pool of travelers are not within a threshold distance of an event at a present time; 
   analyzing traveler data for a selected traveler of the pool of travelers, wherein the traveler data for the selected traveler represents a prior location of the selected traveler and a current location of the selected traveler;   determining, based at least partly on analyzing the traveler data for the selected traveler, that the selected traveler is likely to be positioned within a threshold distance of the event during an event time window associated with the event;   generating an event data file comprising data regarding the event; and   generating a transmission regarding the event data file prior to a time at which the selected traveler is expected to be within the threshold distance of the event.   
     
     
         32 . The computer-implemented method of  claim 31 , further comprising receiving, from a computing device of the selected traveler, a time coincidence signal indicating that the selected traveler is likely to be positioned within the threshold distance of the event extracted at a time coincident with the event time window. 
     
     
         33 . The computer-implemented method of  claim 31 , further comprising:
 determining a velocity of a computing device of the selected traveler in a direction towards the event based at least partly on location data and temporal data received from the computing device of the selected traveler; and   determining an estimated time of arrival of the selected traveler within the threshold distance of the event based at least partly on the velocity.   
     
     
         34 . The computer-implemented method of  claim 31 , further comprising analyzing one or more of geo-location data for travelers the pool of travelers, temporal data for travelers of the pool of travelers, or location history data for travelers of the pool of travelers. 
     
     
         35 . The computer-implemented method of  claim 31 , further comprising:
 extracting stay data from the traveler data for the selected traveler, wherein the stay data represents beginning and ending stay dates; and   generating customized content for the event data file based at least partly on the beginning stay date or the ending stay date.   
     
     
         36 . The computer-implemented method of  claim 31 , further comprising determining a concentration of travelers within a locus, wherein the event data file is generated based at least partly on the concentration. 
     
     
         37 . Non-transitory computer-readable storage comprising executable instructions that configure a computing system to at least:
 extract access request data from an access data file;   access traveler data regarding a pool of travelers identified by the access request data, wherein individual travelers in the pool of travelers are not within a threshold distance of an event at a present time;   determine that a selected traveler of the pool of travelers is expected to be within the threshold distance of the event at a future time based at least partly on an analysis of prior location data associated with the selected traveler and current location data associated with the selected traveler;   generate an event data file for the selected traveler; and   generate a transmission regarding the event data file prior to the future time at which the selected traveler is expected to be within the threshold distance of the event.   
     
     
         38 . The non-transitory computer-readable storage of  claim 37 , wherein the executable instructions further configure the computing system to at least:
 determine a velocity of a computing device of the selected traveler in a direction towards the event based at least partly on location data and temporal data received from the computing device of the selected traveler; and   determine an estimated time of arrival of the selected traveler within the threshold distance of the event based at least partly on the velocity.   
     
     
         39 . The non-transitory computer-readable storage of  claim 37 , wherein the executable instructions further configure the computing system to at least:
 extract stay data from the traveler data for the selected traveler, wherein the stay data represents beginning and ending stay dates; and   generate customized content for the event data file based at least partly on the beginning stay date or the ending stay date.   
     
     
         40 . The non-transitory computer-readable storage of  claim 37 , wherein the executable instructions further configure the computing system to at least determine a concentration of travelers within a locus, wherein the event data file is generated based at least partly on the concentration.