Orchestration of booking matching

A system comprising:

• one or more processors;
• a data communications interface operably associated with the one or more processors;
• and
• at least one memory device coupled to the one or more processors, wherein the at least one memory device contains a plurality of program instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
• receiving, at a gateway server from a client device associated with a service provider, a matching event for the service provider, wherein the matching event is for reconciliation of booking events of a plurality of booking events with lead events of a plurality of lead events;
• managing, by the gateway server, the matching event using a redundant load-balancing system such that the matching event is handled by one data matching server of a plurality of data matching servers capable of servicing the matching event;
• receiving, at the one data matching server via the gateway server, the matching event;
• determining, at the one data matching server executing a matching instruction set comprising an events lookup module, an anonymity module, a booking matching module, and a tracking module, to initiate a matching event for a service provider associated with one or more booking events of a plurality of booking events;
• determining, at the one data matching server, a lead lookup timeframe and a booking lookup timeframe based on the matching event;
• obtaining, at the one data matching server via the events lookup module of the matching instruction set and based on the matching event and the booking lookup timeframe, booking event data for the plurality of booking events from a provider server associated with a first travel provider, wherein the booking event data comprises booking information and one or more sets of booking event attributes for the plurality of booking events, wherein the booking information corresponds to a user and comprises non-personal identifying information and behavioral data associated with each user, the behavioral data comprising interactions with one or more websites associated with an event, a session duration, content displayed during an interaction with one or more websites, or a combination thereof;
• obtaining, at the one data matching server via the events lookup module and based on the matching event and the lead lookup timeframe, lead data for one or more lead events of the plurality of lead events from a provider server associated with a second travel provider;
• determining, at the one data matching server via the booking matching module and based on a booking matching algorithm using on one or more criterion, eligible lead information for each booking event of the one or more booking events that is correlated with a corresponding lead from the lead data, wherein the booking matching algorithm determines eligible lead information based on at least:
• a provider identification associated with each booking event, an activity identification associated with each booking event, and a temporal-based booking threshold applied within a lead lookup timeframe and a booking lookup timeframe, and wherein determining eligible lead information for each booking event comprises grouping eligible leads by referral;
• in response to determining that a first subset of the plurality of eligible leads for the booking correspond to a single referral, selecting the eligible lead closest in time to the booking;
• in response to determining that a second subset of the plurality of eligible leads for the booking correspond to different referrals, generating no match indication for each of the second subset of the plurality of eligible leads;
• storing information associated with matched eligible leads in an eligible lead database;
• and
• providing, from the one data matching server via the gateway server to the client device associated with the service provider, the eligible lead information to the service provider.

A computer program product comprising:

• a non-transitory computer-readable storage medium;
• and
• program code stored on the non-transitory computer-readable storage medium that, when executed by one or more processors, causes the one or more processors to perform operations comprising:
• receiving, at a gateway server from a client device associated with a service provider, a matching event for the service provider, wherein the matching event is for reconciliation of booking events of a plurality of booking events with lead events of a plurality of lead events;
• managing, by the gateway server, the matching event using a redundant load-balancing system such that the matching event is handled by one data matching server of a plurality of data matching servers capable of servicing the matching event;
• receiving, at the one data matching server via the gateway server, the matching event;
• determining, at the one data matching server executing a matching instruction set comprising an events lookup module, an anonymity module, a booking matching module, and a tracking module, to initiate a matching event for a service provider associated with one or more booking events of a plurality of booking events;
• determining, at the one data matching server, a lead lookup timeframe and a booking lookup timeframe based on the matching event;
• obtaining, at the one data matching server via the events lookup module of the matching instruction set and based on the matching event and the booking lookup timeframe, booking event data for the plurality of booking events from a provider server associated with a first travel provider, wherein the booking event data comprises booking information and one or more sets of booking event attributes for the plurality of booking events, wherein the booking information corresponds to a user and comprises non-personal identifying information and behavioral data associated with each user, the behavioral data comprising interactions with one or more websites associated with an event, a session duration, content displayed during an interaction with one or more websites, or a combination thereof;
• obtaining, at the one data matching server via the events lookup module and based on the matching event and the lead lookup timeframe, lead data for one or more lead events of the plurality of lead events from a provider server associated with a second travel provider;
• determining, at the one data matching server via the booking matching module and based on a booking matching algorithm using on one or more criterion, eligible lead information for each booking event of the one or more booking events that is correlated with a corresponding lead from the lead data, wherein the booking matching algorithm determines eligible lead information based on at least:
• a provider identification associated with each booking event, an activity identification associated with each booking event, and a temporal-based booking threshold applied within a lead lookup timeframe and a booking lookup timeframe, and wherein determining eligible lead information for each booking event comprises grouping eligible leads by referral;
• in response to determining that a first subset of the plurality of eligible leads for the booking correspond to a single referral, selecting the eligible lead closest in time to the booking;
• in response to determining that a second subset of the plurality of eligible leads for the booking correspond to different referrals, generating no match indication for each of the second subset of the plurality of eligible leads;
• storing information associated with matched eligible leads in an eligible lead database;
• and
• providing, from the one data matching server via the gateway server to the client device associated with the service provider, the eligible lead information to the service provider.