Systems and methods for providing transaction affinity information
In certain aspects, the disclosed implementations include methods and systems for dynamically generating and providing transaction affinity recommendation data. In certain implementations, the transaction affinity recommendation data may include information that identifies a target merchant and associated merchant promotion data that may be generated based on a dynamic analysis of transaction data corresponding to an account record. The disclosed implementations may determine temporal relationships between pairs of sequential transactions corresponding to the account record, and based on such relationships, may identify pairs of transactions involving separate merchants. The disclosed implementations may determine affinity relationships associated with one or more pairs of the temporally related transactions and a target merchant, and based on such relationships, generate and provide the transaction affinity recommendation data.
1. A method, comprising:
determining, by a device, that an affinity relationship information request has been generated;
determining, by the device, a type of affinity relationship information request based on determining that the affinity relationship information request has been generated,
the type of affinity relationship information request being associated with at least one of:
a location based request,
a merchant hop count request, or
a merchant category request;
analyzing, by the device, transaction data associated with a set of transactions associated with a first account record to generate a transaction affinity data set,
the transaction affinity data set being associated with the type of affinity relationship information request;
determining, by the device, whether a temporal relationship between a first transaction and a second transaction associated with the transaction affinity data set meets a threshold value,
the threshold value being set based upon time variances associated with a location of the first transaction and a location of the second transaction,
the time variances being determined based upon predetermined location category information,
the predetermined location category information being associated with at least one of:
an urban location, or
a rural location;
generating, by the device, transaction affinity relationship data based on the temporal relationship;
generating, by the device and before a new transaction occurs after the second transaction, first merchant recommendation data associated with a set of merchants that have an affinity relationship with a target merchant associated at least one transaction in the first transaction or the second transaction; and
transmitting, by the device and to an interface of a user device associated with the first account record, at least one portion of the first merchant recommendation data.
2. The method of claim 1 , wherein the set of transactions occur within a specified time period during a transaction event,
wherein the at least one portion of the first merchant recommendation data is provided while the user device is in the transaction event and before the new transaction occurs, and
wherein the interface enables an associated selection, of the at least one portion of the first merchant recommendation data, within the interface of the user device while the user device accesses the transaction event.
3. The method of claim 1 , wherein the at least the portion of the first merchant recommendation data includes target merchant identification data that identifies the target merchant and target merchant promotion data that reflects a promotion offered by the target merchant for one or more items or services offered by the target merchant.
4. The method of claim 3 , wherein the at least one portion of the first merchant recommendation data includes at least one of:
at least one merchant logo,
map information, or
at least one hyperlink.
5. The method of claim 1 , wherein the transaction affinity relationship data includes a merchant affinity count value data set, and wherein
the merchant affinity count value data set includes:
first merchant data,
second merchant data, and
a merchant affinity count value.
6. The method of claim 5 , wherein the merchant affinity count value data set reflects how many times an account corresponding to the first account record was separately used in transactions involving a first merchant associated with the first transaction and a second merchant associated with the second transaction.
7. The method of claim 1 , further comprising:
assigning, based on the second transaction occurring subsequent to the first transaction, a merchant affinity relationship strength that reflects that a sequential relationship exists between the first transaction associated with a first merchant and the second transaction associated with a second merchant,
wherein the transaction affinity relationship data is based on the merchant affinity strength relationship.
8. A device, comprising:
one or more memories; and
one or more processors communicatively coupled to the one or more memories, configured to:
determine that an affinity relationship information request has been generated;
analyze transaction data associated with a set of transactions associated with a first account record to generate a transaction affinity data set;
determine whether a temporal relationship between a first transaction and a second transaction associated with the transaction affinity data set meets a threshold value,
the threshold value being set based upon time variances associated with a location of the first transaction and a location of the second transaction,
the time variances being determined based upon predetermined location category information,
the predetermined location category information being associated with at least one of:
an urban location, or
a rural location;
generate transaction affinity relationship data based on the temporal relationship;
generate, before a new transaction occurs after the second transaction, first merchant recommendation data associated with a set of merchants that have an affinity relationship with a target merchant associated at least one transaction in the first transaction or the second transaction; and
transmit, to an interface of a user device associated with the first account record, at least one portion of the first merchant recommendation data.
9. The device of claim 8 , where the one or more processors are further to:
determine an affinity count value associated with the first transaction and the second transaction; and
generate the transaction affinity relationship data based on the affinity count value.
10. The device of claim 9 , the affinity count value reflects a quantity of times an account corresponding to the first account record was separately used in transactions involving a first merchant associated with the first transaction and a second merchant associated with the second transaction.
11. The device of claim 8 , wherein the transaction affinity relationship data includes a merchant affinity count value data set, and
wherein the merchant affinity count value data set includes:
first merchant data,
second merchant data, and
a merchant affinity count value.
12. The device of claim 11 , wherein the at least one portion of the first merchant recommendation data includes at least one of:
at least one merchant logo,
map information, or
at least one hyperlink.
13. The device of claim 11 , wherein the one or more processors are further configured to:
provide the at least one portion of the first merchant recommendation data to a computing system component for displaying content in another interface that includes the at least one portion of the first merchant recommendation data.
14. The device of claim 8 , wherein the one or more processors are further configured to:
assign, based on the second transaction occurring subsequent to the first transaction, a merchant affinity relationship strength that reflects that a sequential relationship exists between the first transaction associated with a first merchant and the second transaction associated with a second merchant,
wherein the transaction affinity relationship data is based on the merchant affinity strength relationship.
15. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
determine that an affinity relationship information request has been generated;
determine a type of affinity relationship information request based on determining that the affinity relationship information request has been generated;
analyze transaction data associated with a set of transactions associated with a first account record to generate a transaction affinity data set,
the transaction affinity data set being associated with the type of affinity relationship information request;
determine whether a temporal relationship between a first transaction and a second transaction associated with the transaction affinity data set meets a threshold value,
the threshold value being set based upon time variances associated with a location of the first transaction and a location of the second transaction,
the time variances being determined based upon predetermined location category information,
the predetermined location category information being associated with at least one of:
an urban location, or
a rural location;
generate transaction affinity relationship data based on the temporal relationship;
generate, before a new transaction occurs after the second transaction, first merchant recommendation data associated with a set of merchants that have an affinity relationship with a target merchant associated at least one transaction in the first transaction or the second transaction; and
transmit, to an interface of a user device associated with the first account record, at least one portion of the first merchant recommendation data.
16. The non-transitory computer-readable medium of claim 15 , wherein the type of affinity relationship information request is associated with at least one of:
a location based request,
a merchant hop count request, or
a merchant category request.
17. The non-transitory computer-readable medium of claim 15 , wherein the transaction affinity relationship data includes a merchant affinity count value data set, and
wherein the merchant affinity count value data set includes:
first merchant data,
second merchant data, and
a merchant affinity count value.
18. The non-transitory computer-readable medium of claim 17 , wherein the merchant affinity count value data set reflects how many times an account corresponding to the first account record was separately used in transactions involving a first merchant associated with the first transaction and a second merchant associated with the second transaction.
19. The non-transitory computer-readable medium of claim 16 , wherein the at least one portion of the first merchant recommendation data includes target merchant identification data that identifies the target merchant and target merchant promotion data that reflects a promotion offered by the target merchant for one or more items or services offered by the target merchant.
20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
assign, based on the second transaction occurring subsequent to the first transaction, a merchant affinity relationship strength that reflects that a sequential relationship exists between the first transaction associated with a first merchant and the second transaction associated with a second merchant,
wherein the transaction affinity relationship data is based on the merchant affinity strength relationship.