Network data processing method and network device

Abstract

The present application is about a network data processing method and a network device. The method includes: receiving a service confirmation request of a network service of at least one user; determining whether the service confirmation request carries a channel identifier; if the service confirmation request carries a channel identifier, saving the channel identifier in the service confirmation request as a formal channel identifier associated with the network service; if the service confirmation request does not carry a channel identifier, obtaining a temporary channel identifier corresponding to the network service cached in the server, and saving the temporary channel identifier as a formal channel identifier associated with the network service in the server. According to the solution provided in the embodiment of the present application, it is possible to ensure the correct attribution of the source of the service without using user browser cookies or cross-device.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a network data processing method and a network device. Background Art

[0002] E-commerce platforms are platforms that provide online transactions for enterprises or individuals. E-commerce platforms are virtual network spaces for business activities on the Internet and management environments that ensure smooth business operations. They are important places for coordinating and integrating the orderly, connected, and efficient flow of information, goods, and funds. Enterprises and merchants can make full use of the shared resources such as network infrastructure, payment platforms, security platforms, and management platforms provided by e-commerce platforms to carry out their own business activities effectively and at low cost.

[0003] Order attribution refers to the identification and differentiation of source channels for orders generated by a website. The traffic channels and structures of e-commerce platforms are complex and diverse, and the traffic billing models are also different. The quality of users guided by different traffic channels varies. By distinguishing the channels of orders, the traffic structure can be better optimized and the output-input ratio of the website can be improved. In addition, for channels with special traffic patterns, such as channels settled by order volume, it is also easier to filter out orders from the corresponding channels, reducing the workload of data statistics and analysis.

[0004] In a related technology, a data retention solution based on browser cookies is used. The channel identification parameter is entered in the address of the landing page, and then the channel identification parameter is set in the user's browser cookie through the front-end or back-end method. When the user completes the order, the channel identification parameter of the cookie in the user's browser is read again, and the order is associated with the channel identification, thereby realizing the attribution of the source of the order.

[0005] The above-mentioned related technologies have the following defects: First, they rely on the normal use of browser cookies. Once the cookie function is restricted, the channel information cannot be recorded in the cookie, and the order and channel cannot be associated; second, they cannot be recorded across devices, and there is a risk of losing channel parameters. When users switch to different browsers to complete the order, the channel parameters are lost on the link, and the source channel of the order cannot be recorded. Summary of the invention

[0006] In order to overcome the problems existing in the related art, the present application provides a network data processing method and a network device, which can ensure the correct attribution of business sources without using user browser cookies or cross-device.

[0007] On one hand, the present application provides a network data processing method, comprising:

[0008] receiving a service confirmation request for a network service of at least one user;

[0009] Determining whether the service confirmation request carries a channel identifier;

[0010] In the case where the service confirmation request carries a channel identifier, the channel identifier in the service confirmation request is stored as a formal channel identifier in association with the network service;

[0011] In the case that the service confirmation request does not carry a channel identifier, a temporary channel identifier corresponding to the network service cached in the server is obtained, and the temporary channel identifier is associated with the network service and stored in the server as a formal channel identifier.

[0012] In some embodiments, before receiving a service confirmation request for a network service of at least one user, the method further includes:

[0013] Receiving a service submission request of the network service from the user;

[0014] Determining whether the service submission request carries a channel identifier;

[0015] In the case where the service submission request carries a channel identifier, the channel identifier carried in the service submission request is used as a temporary channel identifier and is associated with the network service and cached in the server.

[0016] In some embodiments, after determining whether the service submission request carries a channel identifier, the method further includes:

[0017] In the case where the service submission request does not carry a channel identifier, determining whether the service submission request is an intra-site jump;

[0018] In the case where the service submission request does not belong to a same-site jump, in the server, a preset natural source identifier is cached in association with the network service as a temporary channel identifier;

[0019] When the service submission request belongs to a same-site jump, the channel identifier of the previous same-site page cached in the server is obtained, and the channel identifier of the previous same-site page is cached in the server as a temporary channel identifier associated with the network service.

[0020] In some embodiments, the temporary channel identifier and the network service association cache include:

[0021] Obtaining a page source of the network service and a user ID of the user;

[0022] The page source and the user ID are used as cache keys and cached in association with the official channel ID.

[0023] In some embodiments, the service confirmation request and the service submission request come from different terminal devices or from different browsers.

[0024] In some embodiments, the terminal device or browser does not store the channel identifier.

[0025] In some embodiments, obtaining a temporary channel identifier corresponding to the network service cached in the server includes:

[0026] Obtaining a page source of the network service and a user ID of the user;

[0027] The page source and the user identifier are used as cache keys, and a temporary channel identifier cached in association with the cache key is read from a server.

[0028] In some embodiments, the page source is the Request URI included in the HTTP referer part of the business confirmation request; and / or

[0029] The user identification is a user token generated according to the user name and user password of the user.

[0030] In some embodiments, the storing of the formal channel identifier in association with the network service includes:

[0031] Obtaining a service number for the network service;

[0032] The official channel identifier is associated with the business number and saved.

[0033] Another aspect of the present application provides a network device, including:

[0034] Processor; and

[0035] The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method as described above.

[0036] The technical solution provided by the embodiments of the present application may have the following beneficial effects:

[0037] In some embodiments of the present application, the source channel identifier of the network business is stored on the server side, without relying on the normal use of the user's browser cookie. In the absence of cookies, the correct business source attribution can still be achieved. In addition, by obtaining the channel identifier when processing the business submission request and caching it in the server, for cross-device situations, whether the user switches from the PC to the mobile terminal or switches to the browser incognito mode, the initial channel source tracking can be guaranteed to achieve correct business source attribution.

[0038] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The above and other objects, features and advantages of the present application will become more apparent through a more detailed description of exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0040] Figure 1 is a flowchart of a network data processing method according to an embodiment of the present application;

[0041] Figure 2 is a flowchart of a network data processing method according to another embodiment of the present application;

[0042] Figure 3 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0043] The preferred embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the preferred embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0044] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0045] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0046] The technical solution of the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0047] Figure 1 A schematic diagram showing a flow chart of a network data processing method according to an embodiment of the present application is shown. Figure 1 The network data processing method of this embodiment includes:

[0048] In step S11, a service confirmation request for a network service of at least one user is received.

[0049] In step S12, it is determined whether the service confirmation request carries a channel identifier. If so, step S13 is executed; otherwise, step S14 is executed.

[0050] In step S13, the channel identifier in the service confirmation request is associated with the network service as a formal channel identifier and saved, and the process ends.

[0051] In step S14, a temporary channel identifier corresponding to the network service cached in the server is obtained, and the temporary channel identifier is associated with the network service and stored in the server as a formal channel identifier.

[0052] In some embodiments, before receiving the service confirmation request of the network service of at least one user in step S11, the method further includes:

[0053] In step S21, receiving a service submission request of the network service of the user;

[0054] In step S22, it is determined whether the service submission request carries a channel identifier. If so, step S23 is executed; otherwise, step S24 is executed.

[0055] In step S23, the channel identifier carried in the service submission request is cached in association with the network service as a temporary channel identifier in the server, and the process goes to step S11.

[0056] In step S24, it is determined whether the service submission request belongs to a same-site jump. If so, step S25 is executed; otherwise, step S26 is executed.

[0057] In step S25, the channel identifier of the previous same-site page cached in the server is obtained, and the channel identifier of the previous same-site page is cached in the server as a temporary channel identifier associated with the network service, and the process goes to step S11.

[0058] In step S26, the preset natural source identifier is cached in the server as a temporary channel identifier associated with the network service, and the process goes to step S11.

[0059] The service confirmation request and service submission request in the embodiment of the present application may come from the same terminal device or the same browser. It is understandable that the present application is not limited thereto. In practical applications, the service confirmation request and service submission request may also come from different terminal devices or from different browsers. It is understandable that in some embodiments of the present application, the terminal device or browser does not store the channel identifier.

[0060] The source channel identifier of the network business is stored on the server side, without relying on the normal use of user browser cookies. In the absence of cookies, the correct business source attribution can still be achieved. In addition, by obtaining the channel identifier when processing the business submission request and caching it on the server, for cross-device situations, whether the user switches from the PC to the mobile terminal or switches to the browser incognito mode, the initial channel source tracking can be guaranteed to achieve correct business source attribution.

[0061] Figure 2 is a flow chart of a network data processing method according to another embodiment of the present application. In this embodiment, the network data processing method of the present application is described in more detail by taking the application in an online car rental application as an example. It can be understood that the present application is not limited thereto. Figure 2 , the method of the embodiment of the present application includes:

[0062] In step S101, the server receives a user's car rental order request sent by a terminal device.

[0063] In step S102, the server determines whether the received order request carries a channel identifier. If so, the channel identifier carried in the order request is cached as a temporary channel identifier in the server in association with the user's car rental business and step S103 is executed. If not, step S105 is executed.

[0064] In one implementation, the server determines whether a channel identifier is embedded in the landing page URL (Uniform Resource Locator) of the received order request. If so, the order request carries the channel identifier, otherwise, it does not.

[0065] In step S103, the server uses the channel identifier carried in the order request as a temporary channel identifier.

[0066] In step S104, the server parses the page source from the order request, obtains the user ID, and caches the page source and the user ID as cache keys in association with the temporary channel ID, and then proceeds to step S108.

[0067] In one implementation, the HTTP referer part of the order request received by the server includes the RequestURI, that is, the page source. The server parses the Request URI from the order request and can know which page the order request is linked from.

[0068] The user ID is used to indicate which user issued the order request. The user ID is unique, and may be, for example, a user token generated based on a user name and a user password.

[0069] In step S105, the server determines whether the order request is a same-site jump, and if so, executes step S106, otherwise, executes step S107.

[0070] When the order request received by the server does not carry a channel identifier, the server determines whether the order request is redirected from other pages of the same website, that is, determines whether it is a same-site redirect.

[0071] In step S106, the server obtains the channel identifier of the previous cached same-site page, uses the channel identifier of the previous same-site page as a temporary channel identifier, and executes step S104.

[0072] If the order request originates from a redirect to the same site, it means that the channel ID has been cached when processing the previous page on the same site. In this case, the page source and user ID are used as cache keys, and the channel ID of the previous page on the same site is cached as a temporary channel ID in the server in association with the cache key.

[0073] The method for the server to obtain the page source and user identification can be implemented by referring to step S103 and will not be described in detail.

[0074] In step S107, the server uses the preset natural source identifier as a temporary channel identifier and executes step S104.

[0075] If the order request does not carry a channel identifier and does not originate from a same-site redirect, the order request is from a natural source, and the preset natural source identifier will be used as a temporary channel identifier and the cache key will be associated with the cache.

[0076] In step S108, the server returns an order request response corresponding to the order request to the terminal device, and after receiving the order request response, the terminal device displays it accordingly.

[0077] In step S109, the server receives the order confirmation request for the car rental service of the user sent by the terminal device.

[0078] After the terminal device displays the corresponding response to the order request, it sends an order confirmation request to the server in response to the user completing the order operation.

[0079] In step S110, the server determines whether the received order confirmation request carries a channel identifier. If so, the server uses the channel identifier in the service confirmation request as the official channel identifier and executes step S111. Otherwise, the server executes step S112.

[0080] In one implementation, the server determines whether a channel identifier is embedded in the landing page URL (Uniform Resource Locator) of the received order confirmation request. If so, the order confirmation request carries the channel identifier, otherwise, it does not.

[0081] In step S111, the server associates and stores the order number of the user's car rental service with the official channel identifier, and ends the process.

[0082] When the order confirmation request received by the server carries a channel identifier, according to the last attribution principle, the order is directly considered to come from the channel corresponding to the channel identifier in the order confirmation request, and the channel identifier in the business confirmation request is used as the official channel identifier and saved in association with the order number of the user's car rental business.

[0083] In step S112, the server parses the page source from the order confirmation request, obtains the user ID, and uses the web page source and the user ID as cache keys to obtain the cached temporary channel ID corresponding to the cache key as the formal channel ID, and executes step S111.

[0084] When the order confirmation request received by the server does not carry the channel identifier, the cached temporary channel identifier associated with the order is marked as the official channel identifier and stored in association with the order number of the car rental business of the user.

[0085] Figure 3 It is a schematic diagram of the structure of a network device according to an embodiment of the present application.

[0086] See also Figure 3 , the network device 300 includes a memory 301 and a processor 302 .

[0087] The processor 302 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0088] The memory 301 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage. Among them, ROM can store static data or instructions required by the processor 302 or other modules of the computer. The permanent storage device can be a readable and writable storage device. The permanent storage device can be a non-volatile storage device that will not lose the stored instructions and data even if the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device can be a removable storage device (such as a floppy disk, an optical drive). The system memory can be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory can store some or all instructions and data required by the processor at run time. In addition, the memory 301 can include a combination of any computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks can also be used. In some embodiments, the memory 301 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (such as a DVD-ROM, a double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (such as an SD card, a mini SD card, a Micro-SD card, etc.), a magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and transient electronic signals transmitted wirelessly or wired.

[0089] The memory 301 stores executable codes, and when the executable codes are processed by the processor 602 , the processor 302 can execute part or all of the methods described above.

[0090] The scheme of the present application has been described in detail above with reference to the accompanying drawings. In the above embodiments, the description of each embodiment has its own emphasis. For the part that is not described in detail in a certain embodiment, refer to the relevant description of other embodiments. Those skilled in the art should also know that the actions and modules involved in the description are not necessarily required for the present application. In addition, it can be understood that the steps in the method of the embodiment of the present application can be adjusted in order, merged and deleted according to actual needs, and the modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0091] In addition, the method according to the present application may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing some or all of the steps in the above method of the present application.

[0092] Alternatively, the present application can also be implemented as a non-temporary machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) on which executable code (or computer program, or computer instruction code) is stored. When the executable code (or computer program, or computer instruction code) is executed by a processor of an electronic device (or computing device, server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.

[0093] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or a combination of both.

[0094] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system and method according to multiple embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a part of a module, a program segment or a code, and the part of the module, the program segment or the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or the flow chart, and the combination of the square boxes in the block diagram and / or the flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0095] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A network data processing method, characterized in that: include: Receiving a service submission request for a user's network service; Determining whether the service submission request carries a channel identifier; In the case where the service submission request carries a channel identifier, the channel identifier carried in the service submission request is used as a temporary channel identifier and is associated with the network service and cached in the server; receiving a service confirmation request for a network service of at least one user; Determining whether the service confirmation request carries a channel identifier; In the case where the service confirmation request carries a channel identifier, the channel identifier in the service confirmation request is stored as a formal channel identifier in association with the network service; In the case that the service confirmation request does not carry a channel identifier, a temporary channel identifier corresponding to the network service cached in the server is obtained, and the temporary channel identifier is associated with the network service and stored in the server as a formal channel identifier.

2. The network data processing method according to claim 1, characterized in that: After determining whether the service submission request carries a channel identifier, the method further includes: In the case where the service submission request does not carry a channel identifier, determining whether the service submission request belongs to a same-site jump; In the case where the service submission request does not belong to a same-site jump, a preset natural source identifier is cached in the server as a temporary channel identifier associated with the network service; When the service submission request belongs to a same-site jump, the channel identifier of the previous same-site page cached in the server is obtained, and the channel identifier of the previous same-site page is cached in the server as a temporary channel identifier associated with the network service.

3. The network data processing method according to claim 1, characterized in that: The temporary channel identifier and the network service association cache include: Obtaining a page source of the network service and a user ID of the user; The page source and the user ID are used as cache keys and cached in association with the official channel ID.

4. The network data processing method according to claim 1, characterized in that: The service confirmation request and the service submission request come from different terminal devices or from different browsers.

5. The network data processing method according to claim 4, characterized in that: The terminal device or browser does not store the channel identifier.

6. The network data processing method according to claim 1, characterized in that: Obtaining the temporary channel identifier corresponding to the network service cached in the server includes: Obtaining a page source of the network service and a user ID of the user; The page source and the user identifier are used as cache keys, and a temporary channel identifier cached in association with the cache key is read from a server.

7. The network data processing method according to claim 6, characterized in that: The page source is the Request URI included in the HTTP referer part of the service confirmation request; and / or The user identification is a user token generated according to the user name and user password of the user.

8. The network data processing method according to any one of claims 1 to 7, characterized in that: The storage of the association between the official channel identifier and the network service includes: Obtaining a service number for the network service; The official channel identifier is associated with the business number and saved.

9. A network device, characterized in that: include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 8.

Images