JP2021039769A - System, device, and method for associating online action with offline payment transaction - Google Patents

Abstract

To identify association between online action and offline transaction.SOLUTION: Disclosed is a system, a method, and a device for associating an online action of a consumer with offline payment transaction. A first mapping is generated between an identifier of the consumer and an identifier of a payment card of the consumer. A second mapping is generated between the identifier of the consumer and an identifier of the online action of the consumer in association with visit to a web page. Data reflecting the offline payment transaction is received, and the data includes the identifier of the payment card. The association between the online action and the offline transaction is identified by processing the generated first mapping, the generated second mapping, and the received data.SELECTED DRAWING: Figure 8

Description

The disclosure relates to tracking consumer behavior and, more specifically, to associating consumer online behavior with their offline payment transactions.

Various methods are known to track consumer online behavior (eg, contact with online advertising activities, online payment transactions, etc.). Various methods of tracking consumer offline payment transactions are also known.

The consumer intelligence that can be obtained from tracking a given consumer's online behavior and that consumer's offline payment transaction separately is limited.

Therefore, there is a need for improved tracking methods, systems, and devices, or at least alternatives.

In one aspect, a computer execution method is provided that associates a consumer's online behavior with an offline payment transaction. The method is to generate a first mapping between the consumer's identifier and the consumer's payment card identifier on at least one processor, the consumer's identifier, and the consumer's online behavioral identifier. In the meantime, to generate a second mapping in connection with visiting a web page and to receive data that reflects an offline payment transaction, the data containing the payment card identifier. Includes identifying the association between online behavior and offline transactions by processing the generated first mapping, the generated second mapping, and the received data.

In another aspect, a computer system is provided that associates a consumer's online behavior with an offline payment transaction. The system includes at least one processor and memory for storing instructions, and when the instructions are executed on at least one processor, the system is in between the consumer's identifier and the consumer's payment card identifier. Generates a first mapping between the consumer's identifier and the consumer's online behavior identifier in connection with visiting a web page, reflecting offline payment transactions. By receiving data that includes the pay card identifier and processing the generated first mapping, the generated second mapping, and the received data, online actions and offline transactions Identify the association between.

Many additional features and combinations thereof for embodiments described herein will become apparent to those skilled in the art after reading this disclosure.

FIG. 5 is a network diagram showing a network that interconnects a link server, a partner server, a plurality of consumer devices, and a plurality of data sources according to an embodiment. It is a high-level block diagram of the hardware component of the link server of FIG. 1 according to the embodiment. FIG. 5 is a high-level block diagram of the software component of the link server of FIG. FIG. 5 is a diagram schematically showing an association between a user and a payment card according to an embodiment. FIG. 5 is a diagram schematically showing an association between a user and an offline payment transaction according to an embodiment. FIG. 5 is a diagram schematically showing a data flow for associating a user with an offline payment transaction according to an embodiment. FIG. 5 is a diagram schematically showing a data flow for associating a user with an offline payment transaction according to an embodiment. FIG. 5 is a diagram schematically showing a data flow for associating a user with an offline payment transaction according to an embodiment. FIG. 5 is a diagram schematically showing an association between a user and an offline payment transaction with respect to measuring the effectiveness of advertising activity according to an embodiment. FIG. 5 is a diagram schematically showing a data flow for associating a user with an offline payment transaction with respect to measuring the effectiveness of advertising activity according to an embodiment.

FIG. 1 shows a network 8 that interconnects a link server 10, a partner server 14, a plurality of consumer devices 16, and a plurality of data sources 18 according to an embodiment. As detailed herein, the link server 10 is configured to generate data records that reflect the links between the online behavior of multiple consumers and their offline payment transactions.

In embodiments, the link server 10 may be operated by a payment processor and may be configured to process online payment transactions in a known manner. In one example, the link server 10 may be used by a vendor partner to process an online payment transaction, one or more payment processing application programming interfaces (APIs), and / or one or more hosted payment pages (HPP). ) Can be provided in a known manner.

The link server 10 is connected to the partner server 14 and interoperates with the partner server 14 in the manner detailed herein. The partner server 14 may be operated by the partner (or client) of the operator of the link server 10. Such partners may be, for example, vendors, demand-side platform operators, ad exchange platform operators, and the like. For clarity of illustration, only one partner server 14 is shown. However, for example, there may be a plurality of partner servers 14 operated by different partners.

The link server 10 is interconnected with a plurality of consumer devices 16 each of which can be operated by the consumer. Each consumer device 16 may be any networked computing device capable of accessing web content. For example, the consumer device 16 may be a personal computer, workstation, server, portable computer, mobile device, laptop computer, and the like.

The link server 10 is interconnected to a plurality of data sources 18. The link server 10 may be connected to the data source 18 via the network 8. The link server 10 may also be connected directly to the data source 18 (eg, via a port or wired link). The data source 18 is configured to maintain data that reflects offline transactions performed by consumers. Therefore, the data source 18 includes a storage medium suitable for storing such data. The data source 18 may also be configured with a suitable network interface for transmitting data reflecting offline transactions to the link server 10 over, for example, the network 8.

The network 8 includes the Internet, Ethernet (registered trademark), conventional telephone service (POTS) line, public switched telephone network (PSTN), integrated services digital network (ISDN), digital subscriber line (DSL), coaxial cable, and optical fiber. Can carry data, including satellite, mobile, wireless (eg Wi-Fi, WiMAX), SS7 signaling networks, fixed lines, local area networks, wide area networks, and others, including any combination thereof. It can be any possible network.

The link server 10 may be connected to the electronic data store 12. The data store 12 is configured to store data received by the link server 10 or generated by the link server 10. For example, the data store 12 can store, for example, data received from the data source 18 that reflects an offline transaction. The data store 12 can also store various tables, including, for example, user identifiers and mappings, their online transactions, payment cards, partners, advertising campaigns, etc., as detailed below.

The data store 12 may include conventional relational databases such as MySQL ™, Microsoft ™ SQL, and Oracle ™ database. The datastore 12 may also include another type of database, such as an object-oriented database or a NoSQL database. Thus, the link server 10 includes a conventional database engine (not shown) for accessing the datastore 12 using, for example, a query expressed using a conventional query language such as SQL, OQL, etc. be able to.

In embodiments, the link server 10 exchanges web content (eg, user identifiers, pixel tags, etc.) with one or more partner servers 14 or one or more consumer devices 16 (eg, transmission and). / Or receive). In this embodiment, the link server 10 implements a conventional HTTP server application (eg, Apache® HTTP server, nginx, Microsoft IIS, etc.) that adapts the link server 10 to exchange such web content. Can include.

The link server 10 may be embodied in any networked computing device, such as a personal computer, workstation, server, portable computer, mobile device, laptop computer, and the like. In embodiments, the link server 10 can be implemented as a physical or virtual instance that uses various distributed resource technologies such as "cloud computing". Potential benefits to "cloud computing" include ease of adding / removing resources, load balancing, and so on.

FIG. 2 is a block diagram illustrating the hardware components of the link server 10 according to the embodiment. As shown, the link server 10 includes at least one processor 130, memory 132, at least one I / O interface 134, and at least one network interface 136.

Each processor 130 may include, for example, any type of general purpose microprocessor or microcontroller, digital signal processing (DSP) processor, integrated circuit, field programmable gate array (FPGA), reconfigurable processor, or any combination thereof. It can be any type of processor.

The memory 132 includes, for example, random access memory (RAM), read-only memory (ROM), compact disk read-only memory (CDROM), electro-optical memory, magnetic-optical memory, erasable programmable read-only memory (EPROM), and electrical. It may be any type of electronic memory located internally or externally, such as an erasable programmable read-only memory (EEPROM), a ferroelectric RAM (FRAM®). In the embodiment, the data store 12 can reside in the memory 132.

Each I / O interface 134 allows the link server 10 to communicate with input and output devices, such as peripheral devices or external storage devices. Such peripheral devices can include one or more input devices such as keyboards, mice, cameras, touch screens and microphones, and can also include one or more output devices such as display screens and speakers. .. In embodiments, the I / O interface 134 can function as a data communication interface that allows the link server 10 to receive, for example, data from a data source 18.

Each network interface 136 allows the link server 10 to communicate with other components (eg, one or more partner servers 14 and / or data sources 18) to send data to such other components, and / Or receive data from such other components and allow them to access and connect to network resources via one or more networks (eg, network 8).

FIG. 3 shows various application modules that can be run on the link server 10 and adapted to function in the manner disclosed herein. As shown, these modules include a tracker generation module 110, a card matching module 112, a partner matching module 114, an offline data matching module 116, and a report generation module 118.

Each of these modules may be implemented in a high-level programming language, such as a procedural language, an object-oriented language, a scripting language, or any combination thereof. For example, each of these modules may be implemented using C, C ++, C #, Perl, Java, Javascript, and the like. Each of these modules may also be implemented in assembly or machine language. Each module may be in the form of an executable program, a script, a statically linkable library, or a dynamically linkable library.

The tracker generation module 110 is configured to generate one or more tracking elements for tracking a consumer's online behavior.

The tracker generation module 110 generates a unique identifier, which may be referred to herein as "PayID", for each consumer device to be tracked (eg, each consumer device 16). The PayID may be generated in any conventional way and may be, for example, a numeric identifier, an alphanumeric identifier, or the like.

The tracker generation module 110 allows the consumer to visit a web page hosted on the link server 10 (eg, a hosted payment page) or a web page hosted on a third party server (which may be a partner server 14). At that time, the PayID can be provided to the card verification module 112 or the partner verification module 114 for the purpose of creating a cookie containing the PayID on the consumer's browser. In certain embodiments, the tracker generation module 110 creates a cookie containing a PayID on the consumer's browser when the consumer visits a web page hosted on a third-party server (partner server). The PayID can be provided to the third party server (which may be 14).

The card matching module 112 is configured to generate a mapping between consumers and their payment cards. In particular, the card matching module 112 generates a card matching table 500 (FIG. 5), which is the identifier of a particular consumer (ie, PayID) and the unique identifier of the payment card used by that consumer (ie, PayID). That is, the mapping that maps to and from the Card ID) is stored. The card matching table 500 may be stored, for example, in the data store 12 (FIG. 1).

The card matching module 112 is configured to generate such mappings in a variety of ways. As an example, two such practices are detailed below. (I) When a third party server (eg, acting as a vendor website) uses the hosted payment page provided by the link server 10, and (ii) (eg, acting as a vendor website). When the person server uses the payment application programming interface provided by the link server 10.

In the hosted payment page example, when the hosted payment page is loaded by the consumer operating the consumer device 16, the card verification module 112 reads the PayID from the cookie stored in the consumer's browser, or the cookie is If not present, the card matching module 112 calls the tracker generation module 110 to generate a new PayID for the consumer, and the cookie with the PayID is consumed (assuming that the cookie is enabled). It is stored on the consumer's browser.

A hidden field tag can be included on the hosted payment page to hold the PayID value. When the payment form is submitted, the Card ID registered by the consumer and the PayID in the hidden field tag are passed to the card verification module 112.

The card verification module 112 then stores both the PayID and the payment card information (“Card ID”) that the consumer has entered on the hosted payment page in the card matching table 500.

In an example of an application programming interface, pixel tags are fed onto web page 400 (eg, by a third party server) in the payment flow, as shown in FIG. When this web page is accessed by a consumer using the consumer device 16, the pixel tag, along with other relevant information, generates a request to the link server 10, as detailed below. In the illustrated embodiment, the pixel tag is image based and requires a 1x1 pixel size image. This image may be invisible to the user (eg, transparent or hidden from the view). In other embodiments, Javascript-based pixel tags may be used. In yet other embodiments, other types of tags may be used.

When a consumer operating a consumer device 16 loads a web page 400 having a pixel tag, a unique identifier for a particular online transaction (ie, transaction ID or "T.ID") is generated and the pixel tag is T. A request is sent to the card verification module 112 together with the ID.

In one example, the pixel tag may be in the form:

Thus, in this example, the pixel tag is the URL of the link server 10 and the parameter T.I. Includes ID. Other parameters may also be included in the pixel tag and passed to the card matching module 112.

When the card matching module 112 receives the pixel request, the card matching module 112 generates (or reads) a PayID and T.I. The ID and PayID are stored in table 402 (eg, in datastore 12) and respond with a 1x1 pixel size image. If it was necessary to create a new PayID for the consumer (eg, by calling the tracker generation module 110), the PayID will be stored in the consumer's browser as a cookie.

When the payment page form is submitted by the consumer, the Card ID and T.I. The ID is sent to the card matching module 112 through the application programming interface and stored in a separate table 404 (eg, in the datastore 12).

Periodically, the card collation module 112 was subjected to T.I. It initiates the process of associating IDs, thereby creating a mapping between Pay IDs and Card IDs for a particular consumer. If a particular Pay ID to Card ID mapping no longer exists in the card matching table 500, the card matching module 112 creates a new record in the card matching table 500 and stores the mapping.

In embodiments, as an alternative to using cookies, device fingerprinting may be utilized to create a unique PayID for each consumer device 16 that needs to be tracked. Device fingerprinting includes, for example, the device's medium access control (MAC) address, the particular operating system (and version) running on the device, the particular browser (and version) running on the device, and combinations thereof. It may be based on others. Such information for generating device fingerprints may be collected in a known manner.

The PayID generated using device fingerprinting may be stored in the card match table 500 and the partner match table 502.

The partner matching module 114 is configured to generate a mapping between consumers and their online behavior. In particular, the partner matching module 114 generates a partner match table 502 (FIG. 5) that stores the mappings, and each mapping is assigned by a particular consumer identifier (ie, PayID), assigned by the link server 10. The unique identifier of the consumer (ie, the partner's unique user / consumer ID, or "PUID"), and the identifier of a particular online action performed by a particular consumer (behavior ID or "BhID"). )including. The mapping can also include the name of the partner.

As shown in FIG. 6A, the pixel tag 60 is provided to a third party server (which may be the partner server 14). The pixel tag 60 is supplied by a third party server to the consumer operating the consumer device 16 on the corresponding online page 62, where the consumer sees various online activities, such as advertising. Watching videos, reading articles, playing games, conducting online searches, researching, purchasing products / services, or browsing about products / services, online services (eg, instant) Communicate through messaging services) and do other things.

In one example, the pixel tag 60 may be in the following format.

Thus, in this example, the pixel tag 60 includes the URL of the link server 10, the parameter P (partner name), the parameter PUID, and the parameter BhID passed to the partner matching module 114 via the pixel request 64. Other parameters may also be included in the pixel tag 60 and passed to the partner matching module 114.

In embodiments, the partner may choose to omit the parameter PUID in order to escape the generation of PUID. In this case, the partner can utilize the pixel tag 60 in the manner described above without inserting the value of the parameter PUID. In this situation, the partner matching module 114 would assume that any request received from that partner would be associated with the behavior being tracked and would use the NIL value for the PUID.

In the embodiment, the pixel request 64 can omit the parameter BhID. In this embodiment, the partner matching module 114 can instead receive BhID information from a partner (eg, the partner who generated the PUID described above) via the action log file 66. For example, action log file 6
6 may be received from the partner server 14 operated by the partner. The action log file 66 contains a BhID to PUID mapping logged by the partner.

Upon receiving the action log file 66, the partner matching module 114 processes the action log file 66 and populates the partner match table 502 with a mapping between BhID and PUID. Optionally, in this embodiment, the partner matching module 114 replaces the partner match table 502 with two tables, i.e. one table for storing the BhID to PUID mapping, and the PUID to PayID mapping. You can use a separate table to store.

Fortunately, in this embodiment, it is not necessary to supply the pixel tag 60 in connection with each action. Alternatively, the pixel tag 60 may be supplied in the first instance or periodically.

As will be appreciated, the third party server referenced in connection with the partner matching module 114 may be different from the third party server referenced in connection with the card matching module 112.

As noted, when a particular consumer visits a web page 62 with a pixel tag 60, the pixel request 64 is sent to the partner matching module 114.

The partner matching module 114 receives the pixel request 64. In response, the following actions by the partner matching module 114 can be considered. Operation A. If it is a new consumer (ie, the link server 10 cookie does not exist) : 1. The tracker generation module 110 is called to generate a new unique PayID. 2. Create a link server 10 cookie (with PayID stored) on the consumer's browser. 3. 3. The partner match table 502 stores the following: partner name (P), PayID, PUID, BhID (if BhID was received in pixel request 64) and any other information related to that partner (eg, request date). And time stamp). Respond with a 4.1x1 pixel size image (or redirect to partner server 14). Operation B. If it is an existing consumer (ie, the link server 10 cookie is present in the consumer's browser) : 1. Link server 10 Reads the cookie and acquires the PayID stored in the cookie. 2. The partner match table 502 is searched to determine whether there is already a match between PUID and PayID. 3. 3. If no match exists: -Remember in the partner match table 502: partner name (P), PayID, PUID, BhID (if BhID was received in pixel request 64) and any other related to that partner. Information (eg, request date and time stamp). -Respond with a 1x1 pixel size image (or redirect to partner server 14). 4. If a match exists: -Remember in the partner match table 502: partner name (P), PayID, PUID, BhID (if BhID was received in pixel request 64), and any other related to that partner. Information (eg, request date and time stamp). As recognized, this allows the number of actions that have occurred (eg, ads are seen) to be determined, so it may be desirable to keep separate records for matching of the same action. .. -Respond with a 1x1 pixel size image (or redirect to partner server 14).

As shown in FIG. 6B, in embodiments, the pixel tag 60 can be replaced by a partner pixel tag 60'. In particular, this embodiment evades any requirement for a third party server (which may be partner server 14) to directly supply the pixel tags associated with the link server 10 on the web page 62. Instead, the third-party server (which may be the partner server 14) supplies the pixel tag 60'associated with the partner server 14 on the web page 62 and then redirects the web page 62 to make the request. It can be sent to the link server 10.

In one example, the partner pixel tag 60'may have the following format:

Thus, in this example, the pixel tag 60'includes the URL of the partner server 14 and the parameter partner id that identifies the entity to which redirection should be provided (eg, the behavior of the link server 10). When the pixel tag 60'is loaded onto the consumer's browser on the consumer device 16, the browser sends a request to the partner server 14 using the URL above (along with the parameter partner id). The partner server 14 generates / reads the PUID for the consumer and stores the PUID in a cookie on the consumer's browser. The partner server 14 provides and returns a response 68 to the consumer's browser in a redirect pixel request (rather than a 1x1 pixel size image).

The consumer browser response 68 is configured to redirect the consumer browser to the link server 10 in order to initiate the pixel request 70.

In one example, the pixel request 70 may be made using a URL of the form:

Thus, in a manner similar to pixel request 64, the redirected pixel request 70 includes the URL of the link server 10, the parameter P (partner name), the parameter PUID, and the parameter BhID passed to the partner matching module 114. Upon receiving the redirected pixel request 70, the partner matching module 114 can perform the above-mentioned action A or action B.

In the embodiment, the redirect pixel request 70 can omit the action ID (BhID). The partner matching module 114 can use the action log file 66 to generate a mapping between BhID and PUID in the manner described above.

As shown in FIG. 6C, in embodiments, a particular consumer identifier (ie, "Common ID") common to a number of partners may be used in place of the PUID. For example, the Common ID may be an identifier from an ad exchange such as Google® Doubleclick, Facebook® Exchange, and others.

In this embodiment, the operation of the partner matching module 114 is substantially the same as described above in relation to PUID, except for the following differences.

As shown, the pixel tag 60 can be replaced by the pixel tag 60 ". In one example, the pixel tag 60" may be of the form:

Thus, in this example, the pixel tag 60 ”includes a COMON ID instead of a PUID. As recognized, the format of the Comon ID varies, for example, depending on the particular ad exchange involved. This Common ID is passed to the partner matching module 114 via pixel request 64. The pixel tag 60 "also includes parameter P (partner name).

The partner matching module 114 records the parameters P, PayID, and Common ID, as well as any other relevant information, in the partner match table 502.

The pixel tag 60 ”omits the BhID. The partner matching module 114 can use the action log file 66 to generate a mapping between the BhID and the Common ID, as shown. The partner can maintain a match table 72 containing a mapping between PUID and Common ID that can be used by the partner to generate the action log file 66.

In embodiments, the pixel tag 60 "can be replaced by a common partner pixel tag (not shown), which is configured to redirect pixel requests to the link server 10 in the manner described above. The URL of the common partner server to be obtained can be included.

The offline data matching module 116 is configured to generate a mapping between consumers' online behavior and their offline payment transactions. In particular, the offline data matching module 116 uses the card match table 500 and the partner match table 502, as well as the offline transaction data received from one or more data sources 18 to generate such a mapping.

The offline transaction data may be stored in the transaction data table 504 and may include the consumer's Card Id, purchase price and other relevant information.

FIG. 5 shows an exemplary mapping generated by the offline data matching module 116. For example, as shown, a consumer with PayID XYZAB may be mapped to Card ID 5xx5678 in the card matching table 500 (eg, mapped by the card matching module 112). The same consumer may be matched with a particular online action "X" as shown in the partner match table 502 (eg, mapped by partner matching module 114). For example, a particular online behavior may correspond to visiting a particular web page represented by a particular BhID in the partner match table 502. The same consumer may also be matched to a particular offline transaction (for an amount of $ 60), as shown in transaction data table 504, based on the consumer's associated Card ID. In this way, the consumer's online behavior is mapped to his / her offline transactions.

In a particular embodiment, the link server 10 may be configured to facilitate the measurement of advertising activity effectiveness. In this embodiment, the particular online behavior of interest is, for example, to see ads from a particular advertising campaign promoted by a particular ad exchange.

In this embodiment, the partner matching module 114 is configured to generate a mapping between consumers and the particular advertising activity campaign seen by those consumers. As described above, the partner matching module 114 is configured to use the ad campaign ID (Ad.ID) instead of the action ID (BhID). In another embodiment, an Ad ID that uniquely identifies a particular ad, or an Ad ID that uniquely identifies a particular ad supplied by a particular partner, is an ad campaign ID to provide greater tracking particle size. May be used instead of.

Therefore, pixel tags of the following formats may be used to provide the partner matching module 114 with an ad campaign ID and PUID and to allow a match between them.

In addition, the partner match table 502, as shown in FIG. 7, instead of BhID, Ad. It can be replaced by a partner match table 502'configured to store the ID.

In embodiments, if a partner (eg, a demand-side platform) cannot directly supply pixel tags, but can maintain a match table with an ad exchange (eg, with Google's DoubleClick Ad Exchange), the partner is offline. In the data collation module 116, Ad. Data holding an ID and a corresponding Common ID can be provided. Using the Common ID, the offline data matching module 116 determines the associated PayID in the partner match table 502/502'and matches it with the Card ID in the card match table 500 for each record.

Once the corresponding Card IDs are known for a particular ad campaign being tracked, these Card IDs are, for example, offline (eg, in-store, through a phone call) of the same vendor participating in the ad campaign. , In-app, and other) payment transaction data can be matched.

As described above, FIG. 8 schematically shows the operation of the link server 10 with respect to measuring the advertising activity effect.

As shown, various entities (eg, vendors / ad agencies, data providers, campaign platforms / demand-side platform operators, ad exchanges) can interoperate in known ways to implement advertising campaigns. it can. The operation of the link server 10 is substantially similar to that described with reference to FIG. 6C for an embodiment using a Common ID.

As will be appreciated, a particular ad exchange can use a number of Common IDs for a particular consumer. For example, as shown in FIG. 8, the ad exchange has two different Conmon IDs for a particular consumer, namely G.M. ID (P1) and G.I. ID (P2) can be used. In this case, a unique one of the Common IDs may be selected for use associated with the link server 10. The selected Common ID, eg, G.M. The ID (P1) may be used in both the pixel request to the link server 10 and the action log file sent to the link server 10 to facilitate matching in the manner disclosed above.

Referring again to FIG. 3, the report generation module 118 may be configured to generate various reports based on associating a consumer's online behavior with an offline payment transaction. For example, the report generation module 118 can generate one or more reports that have the following information: -Total number of identifiable individuals who made offline purchases (relative to total number of identifiable individuals who did not purchase) -Classification by source of transaction (eg, online vs. in-store vs. phone), -Total sales of offline transactions Includes amount and return on investment determination (assuming costing information that will be provided by the vendor or business partner), and-over time at the vendor and benchmarked trends for all shoppers. But a "share of wallet" that shows the average percentage of consumers' total spending at identifiable vendors.

Other relevant information may also be included in the report.

Such reports may be presented electronically by the report generation module 118, for example via a partner web portal. Such reports may also be presented in paper format.

In embodiments, the operation of the link server 10 allows consumers to perform online actions or actions offline (eg, in-store or by mail order / telephone order) without the direct involvement of the consumer and / or the vendor. Associate with the payment transaction.

In embodiments, the operation of the link server 10 can facilitate the measurement of the vendor's online advertising activity, which contributes to offline (eg, in-store or mail order / telephone order) sales.

In embodiments, the behavior of Link Server 10 is for the trader or other client to understand how the various online behaviors and behaviors of consumers visiting online / mobile sites relate to their offline spending. Can facilitate the generation of analytical reports.

In embodiments, the operation of the link server 10 can facilitate the targeting of online advertisements to the customers of the traders who trade with them offline.

In an embodiment, the operation of the link server 10 is for a trader to provide their customers with a seamless shopping experience, whether they are shopping online from a desktop or mobile device, by phone, or in a physical store. A low friction omni-channel approach can be facilitated.

Therefore, the link server 10 may be operated in multiple contexts and for multiple purposes, including, for example, ad campaign effectiveness measurement, analytical theory for vendors or business partners, targeted advertising activities, and the like.

The device, system and method embodiments described herein can be implemented in both hardware and software combinations. These embodiments may be implemented on programmable computers, where each computer comprises at least one processor and a data storage system (volatile or non-volatile memory, or other data storage element, or a combination thereof. ) And at least one communication interface.

Program code is applied to the input data to perform the functions described herein and generate output information. The output information applies to one or more output devices. In certain embodiments, the communication interface may be a network communication interface. In embodiments in which the elements can be combined, the communication interface may be a software communication interface, such as for interprocess communication. In yet other embodiments, there may be a combination of hardware, software, and communication interfaces implemented as a combination thereof.

Throughout the discussion above, numerous references will be made regarding servers, services, interfaces, portals, platforms, or other systems formed from computing devices. The use of such terms refers to one or more computing devices with at least one processor configured to execute software instructions stored on computer-readable, tangible, non-temporary media. It should be recognized that it is considered as. For example, a server can include one or more computers that act as web servers, database servers, or other types of computer servers in a manner that fulfills the roles, responsibilities, or functions described.

The following discussion provides many exemplary embodiments. Although each embodiment represents a single combination of inventive elements, other examples may include all possible combinations of disclosed elements. Therefore, if one embodiment comprises elements A, B and C and the second embodiment comprises elements B and D, the other remaining combinations of A, B, C or D are also used. There is.

The terms "connected" or "coupled to" are either direct (two elements that are connected to each other touch each other) and non-directly (at least one between the two elements). It may contain both (two additional elements are positioned).

The technical solution of the embodiment may be in the form of a software product. The software product may be stored in a non-volatile or non-temporary storage medium, which may be a compact disc read-only memory (CD-ROM), a USB flash disk, or a removable hard disk. The software product includes several instructions that allow a computer device (personal computer, server, or network device) to perform the methods provided by the embodiments.

The embodiments described herein are implemented by physical computer hardware including computing devices, servers, receivers, transmitters, processors, memory, displays and networks. The embodiments described herein provide useful physical machines, and in particular computer hardware equipment configured. The embodiments described herein are directed to electronic machines and methods implemented by electronic machines adapted for processing and transforming electromagnetic signals representing various types of information. The embodiments described herein broadly and collectively relate to machines and their use, the embodiments described herein are those with computer hardware, machines, and various hardware components. Has no meaning or de facto applicability outside the scope of its use. For example, using mental steps to substitute physical hardware specifically configured to implement various actions instead of non-physical hardware has a substantial effect on how the embodiment works. Sometimes. Such computer hardware limitations are a clear essential element of the embodiments described herein, without having a significant impact on the operation and structure of the embodiments described herein. They cannot be omitted or replaced by mental means. Computer hardware is essential for implementing the various embodiments described herein and is not merely used to perform steps in a fast and efficient manner.

Although embodiments have been described in detail, it should be understood that various modifications, substitutions and modifications can be made herein without departing from the scope defined by the appended claims. Is.

Moreover, the scope of this application is not intended to be limited to specific embodiments of the processes, machines, products, compositions, means, methods and steps described herein. As will be readily appreciated by those skilled in the art from the disclosure of the present invention, there are presently present that perform substantially the same functions or achieve substantially the same results as the corresponding embodiments described herein. Processes, machines, products, compositions, means, methods or steps that are or will be developed later may be utilized. Therefore, the appended claims are intended to include such processes, machines, products, compositions, means, methods or steps within them.

As can be understood, the examples described and shown above are intended to be exemplary only.

Below, the contents of the scope of claims at the time of filing are described as examples. [Example 1] A computer execution method for associating a consumer's online behavior with an offline payment transaction, wherein in at least one processor, between the consumer's identifier and the consumer's payment card identifier. Generating a mapping of one and generating a second mapping in connection with visiting a web page between the identifier of the consumer and the identifier of the consumer's online behavior. Receiving data that reflects an offline payment transaction, wherein the data includes the identifier of the payment card, the generated first mapping, the generated second mapping, and said. A method that includes identifying the association between the online activity and the offline payment transaction by processing the received data. [Example 2] The method of Example 1, further comprising receiving the consumer's identifier via a browser cookie. [Example 3] The method of Example 1, further comprising receiving the identifier of the consumer via a hosted payment page. [Example 4] The method of Example 1, further comprising receiving the identifier of the consumer via an application programming interface for processing an online payment transaction. [Example 5] The method of Example 4, wherein the consumer's identifier is received in connection with a transaction identifier for an online payment transaction. [Example 6] The method of Example 4, wherein the identifier of the transaction is received via a pixel tag. [Example 7] The method of Example 6, wherein the pixel tag includes an image-based pixel tag. [Example 8] The method of Example 6, wherein the pixel tag includes a Javascript-based pixel tag. [Example 9] The method of Example 1, further comprising generating the identifier of the consumer. [Example 10] The method of Example 1, further comprising receiving the identifier of the online action via a pixel tag. [Example 11] The method of Example 1, further comprising receiving the identifier of the online action via a log file. [Example 12] The method of Example 1, wherein the first mapping is generated in connection with an online payment transaction. [Example 13] The method of the first embodiment, wherein the online action includes viewing an advertisement, and the identifier of the online action includes an identifier of an advertising activity campaign. [Example 14] The method of Example 1, further comprising generating a report based on the association between the online action and the offline payment transaction. [Example 15] The method of Example 1 in which the data is received via a network interface. [Example 16] A computer system that associates a consumer's online behavior with an offline payment transaction, at least one processor and a memory that stores an instruction, the instruction being executed by the at least one processor. Then, the computer system is made to generate a first mapping between the consumer's identifier and the consumer's payment card identifier, and the consumer's identifier and the consumer's online behavior. A second mapping is generated between the identifier and the web page in connection with the visit to receive the data that reflects the offline payment transaction and includes the identifier of the payment card. Includes a memory that identifies the association between the online activity and the offline payment transaction by processing the generated first mapping, the generated second mapping, and the received data. system. [Example 17] The system of the sixteenth embodiment, wherein the online action includes viewing an advertisement, and the identifier of the online action includes an identifier of an advertising activity campaign. [Example 18] The system of Example 16 in which the first mapping is generated in connection with an online payment transaction.

Claims (20)

A computer execution method that associates consumer online behavior with offline payment transactions.
On at least one processor
The first mapping between the consumer device identifier and the consumer payment card identifier corresponds to a particular online transaction and at least one hosting the online payment page associated with the online payment transaction. Generated using a unique identifier generated by a vendor, partner, or payment processor,
Generating a second mapping in connection with visiting a web page between the consumer's identifier and the consumer's online behavioral identifier.
Receiving data that reflects an offline payment transaction, said data including said identifier of said payment card.
Identifying the association between the online behavior and the offline payment transaction by processing the generated first mapping, the generated second mapping, and the received data.
How to include. The method of claim 1, wherein the identifier of the consumer's device is an identifier (PUID) generated by a partner or an identifier (PayID) generated by a tracker generation module. The method of claim 1, further comprising receiving the consumer's identifier via a browser cookie. The method of claim 1, further comprising receiving the identifier of the consumer via a hosted payment page. The method of claim 1, further comprising receiving said identifier of said consumer via an application programming interface for processing an online payment transaction. The method of claim 5, wherein the consumer's identifier is received when receiving a transaction identifier for an online payment transaction. The method of claim 6, wherein the identifier of the transaction is included in a pixel tag. The method of claim 7, wherein the pixel tag comprises an image-based pixel tag. The method of claim 7, wherein the pixel tag comprises a Javascript-based pixel tag. The method of claim 1, further comprising generating the identifier of the consumer. The method of claim 7, further comprising receiving the identifier of the online action after receiving the pixel tag. The method of claim 1, further comprising receiving the identifier of the online activity contained in a log file. The method of claim 1, wherein the first mapping is generated in connection with an online payment transaction. The method according to claim 1, wherein the online behavior includes viewing an advertisement, and the identifier of the online behavior includes an identifier of an advertising activity campaign. The method of claim 1, further comprising generating a report based on the association between the online behavior and the offline payment transaction. The method of claim 1, wherein the data is received via a network interface. A computer system that associates consumer online behavior with offline payment transactions.
With at least one processor
A memory that stores instructions that, when executed by the at least one processor, are stored in the computer system.
The first mapping between the consumer device identifier and the consumer payment card identifier corresponds to a particular online transaction and at least one hosting the online payment page associated with the online payment transaction. Generated using a unique identifier generated by a vendor, partner, or payment processor
Generate a second mapping between the consumer's identifier and the consumer's online behavioral identifier in connection with visiting a web page.
Data that reflects an offline payment transaction, including the identifier of the payment card, is received.
By processing the generated first mapping, the generated second mapping, and the received data, the association between the online behavior and the offline payment transaction is identified.
A system that includes memory. The system according to claim 17, wherein the identifier of the device of the consumer is an identifier (PUID) generated by a partner or an identifier (PayID) generated by a tracker generation module. The system according to claim 17, wherein the online action includes viewing an advertisement, and the identifier of the online action includes an identifier of an advertising activity campaign. 17. The system of claim 17, wherein the first mapping is generated in connection with an online payment transaction.

Images