Systems and methods for targeted potential transaction delivery without using cookie data

A method, comprising:

• storing, by one or more processors in memory, a database comprising a plurality of accounts, each account corresponding to a different account identifier and a value and comprising historical transaction data of transactions performed through the account;
• receiving, by the one or more processors and from each of a plurality of computing devices executing a first application, potential transaction data corresponding to a potential transaction associated with the computing device;
• generating, by the one or more processors, a potential transaction identifier for each of the potential transactions;
• establishing, by the one or more processors, a connection with a client device through a second application executing on the client device, the second application corresponding to a first account of the plurality of accounts and a first account identifier;
• selecting, by the one or more processors, a subset of the potential transactions based on first historical transaction data of the first account satisfying a selection policy with each of the subset of potential transactions;
• presenting, by the one or more processors via the connection through the second application on the client device, the selected subset of the potential transactions on a user interface at the client device;
• receiving, by the one or more processors from the client device through the connection, a selection of a first potential transaction from the subset of the potential transactions;
• in response to the selection, generating, by the one or more processors, an account potential transaction code based on the first account identifier of the first user account and a first potential transaction identifier of the first potential transaction;
• transmitting, by the one or more processors, the account potential transaction code to a second computing device;
• subsequent to transmitting the account potential transaction code to the second computing device, receiving, by the one or more processors, a transaction request for a transaction, the transaction request comprising the account potential transaction code;
• and
• responsive to receiving the transaction request and based on the transaction request comprising the account potential transaction code, updating, by the one or more processors, the first user account to indicate the transaction.

A non-transitory computer-readable media comprising computer-executable instructions embodied thereon that, when executed by a processor, cause the processor to perform a process comprising:

• storing, in memory, a database comprising a plurality of accounts, each account corresponding to a different account identifier and a value and comprising historical transaction data of transactions performed through the account;
• receiving, from each of a plurality of computing devices executing a first application, potential transaction data corresponding to a potential transaction associated with the computing device;
• generating a potential transaction identifier for each of the potential transactions;
• establishing a connection with a client device through a second application executing on the client device, the second application corresponding to a first account of the plurality of accounts and a first account identifier;
• selecting a subset of the potential transactions based on first historical transaction data of the first account satisfying a selection policy with each of the subset of potential transactions;
• presenting, via the connection through the second application on the client device, the selected subset of the potential transactions on a user interface at the client device;
• receiving, from the client device through the connection, a selection of a first potential transaction from the subset of the potential transactions;
• in response to the selection, generating an account potential transaction code based on the first account identifier of the first user account and a first potential transaction identifier of the first potential transaction;
• transmitting the account potential transaction code to a second computing device;
• subsequent to transmitting the account potential transaction code to the second computing device, receiving a transaction request for a transaction, the transaction request comprising the account potential transaction code;
• and
• responsive to receiving the transaction request and based on the transaction request comprising the account potential transaction code, updating the first user account to indicate the transaction.