Scalable household transaction ingestion system and method

1 . A method comprising:

receiving first transaction data associated with a first plurality of transactions, wherein each of the plurality of first transactions was performed via a browser session initialized by a user via a respective browser on a user computing device, wherein the first transaction data comprises one or more of a time of each of the plurality of first transactions, first location data, a uniform resource locator (URL) associated with each of the plurality of first transactions, one or more items purchased, a payment method associated with each of the first plurality of transactions, or anonymous data associated with each of the plurality of first transactions;

determining a first latitude coordinate and a first longitude coordinate of each respective user computing device when each of the plurality of first transactions was performed, wherein the first latitude coordinate and first longitude coordinate are determined based on the anonymous data upon determining that the respective user opted-out of location tracking, or wherein the first latitude coordinate and the first longitude coordinate are determined based on geo-location data retrieved from the respective user computing device upon determining that the respective user opted-in to location tracking;

determining addresses of each household of each respective user based on the first latitude coordinate and the first longitude coordinate using a map application programming interface (API);

determining that resident density data associated with one or more households is not available in a household database;

upon determining that resident density data for the one or more households is not available, initiating a household computing shard for each of the one or more households;

determining, using the respective initiated household computing shards, resident density data for each of the one or more households at the determined addresses based on the first transaction data by determining a ratio of shoppers to bedrooms in each of the one or more households, wherein the resident density data is a measure of a number of shoppers in a respective household;

identifying each of the users associated with each of the plurality of first transactions;

determining that a first identified user is included in the resident density data when the first identified user is in the household database;

determining that a second identified user is not included in the resident density data when the second identified user is not in the household database;

updating the resident density data to include each identified user not included in the resident density data; and

pre-processing the first transaction data and the resident density data to determine filtering criteria for a campaign.

2 . The method of claim 1 , further comprising anonymizing the resident density data to remove any personally identifiable information (PII).

3 . The method of claim 1 , further comprising determining whether resident density data for a household of the one or more households is available.

4 . The method of claim 1 , wherein the anonymous data comprises one or more of the time of a first transaction of the plurality of transactions, a date of the first transaction, the URL associated with the first transaction, a referring URL, a browser type, a language, an internet protocol (IP) address, or the first location data.

5 . The method of claim 1 , wherein the resident density data is determined using parallel processing through horizontal warehouse scaling.

6 . The method of claim 1 , further comprising attributing the first transaction data to one or more households using a multi-dwelling learning algorithm.

7 . The method of claim 1 , further comprising updating the resident density data upon determining that a user in household performed a transaction.

8 . A non-transitory, machine-readable storage device that includes instructions that, when executed by a computing device, cause the computing device to:

receive first transaction data associated with a first plurality of transactions, wherein each of the plurality of first transactions was performed via a browser session initialized by a user via a respective browser on a user computing device, wherein the first transaction data comprises one or more of a time of each of the plurality of first transactions, first location data, a uniform resource locator (URL) associated with each of the plurality of first transactions, one or more items purchased, a payment method associated with each of the first plurality of transactions, or anonymous data associated with each of the plurality of first transactions;

determine a first latitude coordinate and a first longitude coordinate of each respective user computing device when each of the plurality of first transactions was performed, wherein the first latitude coordinate and first longitude coordinate are determined based on the anonymous data upon determining that the respective user opted-out of location tracking, or wherein the first latitude coordinate and the first longitude coordinate are determined based on geo-location data retrieved from the respective user computing device upon determining that the respective user opted-in to location tracking;

determine addresses of each household of each respective user based on the first latitude coordinate and the first longitude coordinate using a map application programming interface (API);

determine that resident density data associated with one or more households is not available in a household database;

upon determining that resident density data for the one or more households is not available, initiate a household computing shard for each of the one or more households;

determine, using the respective initiated household computing shards, resident density data for each of the one or more households at the determined addresses based on the first transaction data by determining a ratio of shoppers to bedrooms in each of the one or more households, wherein the resident density data is a measure of a number of shoppers in a respective household;

identify each of the users associated with each of the plurality of first transactions;

determine that a first identified user is included in the resident density data when the first identified user is in the household database;

determine that a second identified user is not included in the resident density data when the second identified user is not in the household database;

update the resident density data to include each identified user not included in the resident density data; and

pre-process the first transaction data and the resident density data to determine filtering criteria for a campaign.

9 . The non-transitory, machine-readable storage device of claim 8 , wherein the instructions, when executed by the computing device, cause the computing device to anonymize the resident density data to remove any personally identifiable information (PII).

10 . The non-transitory, machine-readable storage device of claim 8 , wherein the instructions, when executed by the computing device, cause the computing device to determine whether resident density data for a household of the one or more households is available.

11 . The non-transitory, machine-readable storage device of claim 8 , wherein the anonymous data comprises one or more of the time of a first transaction of the plurality of transactions, a date of the first transaction, the URL associated with the first transaction, a referring URL, a browser type, a language, an internet protocol (IP) address, or the first location data.

12 . The non-transitory, machine-readable storage device of claim 8 , wherein the resident density data is determined using parallel processing through horizontal warehouse scaling.

13 . The non-transitory, machine-readable storage device of claim 8 , wherein the instructions, when executed by the computing device, cause the computing device to attribute the first transaction data to the one or more households using a multi-dwelling learning algorithm.

14 . The non-transitory, machine-readable storage device of claim 8 , wherein the instructions, when executed by the computing device, cause the computing device to update the resident density data upon determining that a user in the household performed a transaction.

15 . A method comprising:

receiving transaction data associated with a plurality of transactions performed by a plurality of users at a plurality of households, wherein the transaction data comprises one or more of respective times of the plurality of transactions, location data for each of plurality of the transactions, respective uniform resource locators (URLs) associated with the each of the plurality of transactions, items purchased, respective payment methods associated with each of the plurality of transactions, or anonymous data associated with each of the plurality of transactions;

determining an address for each of the households based on the transaction data using a map application programming interface (API);

identifying users associated with each of the plurality of transactions;

determining that resident density data associated with one or more of the households is not available in a household database;

generating, using respective household shards for each of the one or more households, resident density data for each of the one or more households using the identified users and the transaction data by determining a ratio of shoppers to bedrooms in each of the one or more households, wherein the resident density data is a measure of a number of shoppers in the respective household;

anonymizing the resident density data and the transaction data to remove any personally identifiable information (PII); and

pre-processing the anonymized transaction data and the anonymized resident density data for analysis.

16 . The method of claim 15 , further comprising determining a latitude coordinate and a longitude coordinate of each of the plurality of users, wherein the latitude coordinates and the longitude coordinates are determined based on the anonymous data associated with each of the plurality of transactions upon determining that the respective user opted-out of location tracking, or wherein the latitude coordinate and the longitude coordinate are determined based on geo-location data retrieved from the respective user computing device upon determining that the respective user opted-in to location tracking.