CN114726874A

CN114726874A - Network data processing method and network equipment

Info

Publication number: CN114726874A
Application number: CN202011523997.0A
Authority: CN
Inventors: 许齐卫
Original assignee: Guangzhou Tianxia Technology Co ltd
Current assignee: Guangzhou Tianxia Technology Co ltd
Priority date: 2020-12-22
Filing date: 2020-12-22
Publication date: 2022-07-08

Abstract

The application relates to a network data processing method and network equipment. The method comprises the following steps: receiving a service confirmation request of network service of at least one user; judging whether the service confirmation request carries a channel identifier or not; under the condition that the service confirmation request carries a channel identifier, storing the channel identifier in the service confirmation request as a formal channel identifier in association with the network service; and under the condition that the service confirmation request does not carry a channel identifier, acquiring a temporary channel identifier which is cached in the server and corresponds to the network service, and storing the temporary channel identifier as a formal channel identifier in the server in association with the network service. According to the scheme provided by the embodiment of the application, the correct attribution of the service source can be ensured under the condition that the Cookie of the user browser or the cross-device is not used.

Description

Network data processing method and network equipment

Technical Field

The present application relates to the field of internet technologies, and in particular, to a network data processing method and a network device.

Background

The e-commerce platform is a platform for providing online transactions for businesses or individuals. The e-commerce platform is a management environment which establishes a virtual network space for carrying out business activities on the Internet and ensures the smooth operation of the business; the system is an important place for coordinating and integrating information flow, goods flow and fund flow in order, relevance and high-efficiency flow. Enterprises and merchants can effectively develop their own business activities at low cost by fully utilizing shared resources such as network infrastructure, payment platform, security platform, management platform and the like provided by the merchant platform.

Order attribution refers to identification and differentiation of source channels for orders generated by a website. The flow channels and structures of the e-commerce platform are complex and various, and the flow charging modes are different. The user quality guided by different flow channels is uneven, and the flow structure can be better optimized by distinguishing the channels of the order, so that the output-input ratio of the website is improved. In addition, the order of the corresponding channel can be conveniently screened out aiming at the channel with a special flow mode, such as the channel for settlement according to the single amount, and the workload of data statistics and analysis is reduced.

In a related art, a data retention scheme implemented based on a browser Cookie is used. And bringing in the channel identification parameter on the address of the landing page, and then setting the channel identification parameter in the Cookie of the user browser in a front-end or back-end mode. When the user finishes placing an order, reading the channel identification parameter of the Cookie in the user browser, and associating the order with the channel identification, thereby realizing the reason of the order source.

The above related art has the following drawbacks: firstly, depending on the normal use of Cookie of a browser, once the function of the Cookie is limited, channel information cannot be recorded in the Cookie, and an order and a channel cannot be associated; secondly, cross-device recording cannot be performed, and the risk of channel parameter loss exists. When the user switches different browsers to complete ordering, the channel parameters are lost on the links, and the source channel of the order cannot be recorded.

Disclosure of Invention

In order to overcome the problems in the related art, the application provides a network data processing method and network equipment, which can ensure that the correct attribution of the service source is realized under the condition of not using a user browser Cookie or crossing equipment.

One aspect of the present application provides a network data processing method, including:

receiving a service confirmation request of network service of at least one user;

judging whether the service confirmation request carries a channel identifier or not;

under the condition that the service confirmation request carries a channel identifier, storing the channel identifier in the service confirmation request as a formal channel identifier in association with the network service;

and under the condition that the service confirmation request does not carry a channel identifier, acquiring a temporary channel identifier which is cached in the server and corresponds to the network service, and storing the temporary channel identifier as a formal channel identifier in the server in association with the network service.

In some embodiments, before receiving the service confirmation request of the network service of the at least one user, further comprising:

receiving a service submission request of the network service of the user;

judging whether the service submission request carries a channel identifier or not;

and under the condition that the service submission request carries a channel identifier, the channel identifier carried in the service submission request is taken as a temporary channel identifier in a server to be in associated cache with the network service.

In some embodiments, after determining whether the channel identifier is carried in the service submission request, the method further includes:

under the condition that the service submission request does not carry a channel identifier, judging whether the service submission request belongs to intra-site skipping or not;

under the condition that the service submission request does not belong to the same-station skip, in a server, a preset natural source identifier is taken as a temporary channel identifier and is cached in association with the network service;

and under the condition that the service submitting request belongs to the same-station skip, obtaining a channel identifier of a previous same-station page cached in the server, and caching the channel identifier of the previous same-station page in the server as a temporary channel identifier in association with the network service.

In some embodiments, the caching of the temporary channel identification in association with the network traffic comprises:

acquiring a page source of the network service and a user identifier of the user;

and performing associated cache on the page source and the user identifier as cache keys and the formal channel identifier.

In some embodiments, the service confirmation request and the service submission request are from different terminal devices or from different browsers.

In some embodiments, the terminal device or browser does not store a channel identification.

In some embodiments, obtaining the temporary channel identification corresponding to the network traffic cached in the server comprises:

and taking the page source and the user identification as cache keys, and reading temporary channel identifications cached in association with the cache keys from a server.

In some embodiments, the page source is a Request URI included in the HTTP referrer part of the service confirmation Request; and/or

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

In some embodiments, the storing of the formal channel identification in association with the network traffic comprises:

acquiring a service number of the network service;

and associating and storing the formal channel identification and the service number.

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

a processor; and

a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method as described above.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

in some embodiments of the application, the source channel identifier of the network service is stored in the server side, and the user does not depend on the normal use of Cookie of a browser of the user, so that the correct service source attribution can be still achieved under the condition that the Cookie is not used. In addition, by acquiring the channel identifier and caching the channel identifier in the server when processing the service submission request, for the cross-device condition, no matter the user switches the mobile terminal from the PC terminal or switches the mobile terminal to the traceless browser mode, the initial channel source tracking can be ensured, and the correct service source attribution is realized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The foregoing and other objects, features and advantages of the application will be apparent from the following more particular descriptions of exemplary embodiments of the application, as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout the exemplary embodiments of the application.

Fig. 1 is a schematic flow chart of a network data processing method according to an embodiment of the present application;

FIG. 2 is a schematic flow chart diagram of a network data processing method according to another embodiment of the present application;

fig. 3 is a schematic diagram of a network device according to an embodiment of the present application.

Detailed Description

Preferred embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.

The technical solutions of the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic flow chart illustrating a network data processing method according to an embodiment of the present application. Referring to fig. 1, the network data processing method of the present embodiment includes:

in step S11, a service confirmation request of the network service of at least one user is received.

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.

In step S13, the channel identifier in the service confirmation request is stored as a formal channel identifier in association with the network service, and the process is terminated.

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

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

receiving a service submission request of the network service of the user in step S21;

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.

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

In step S24, it is determined whether the service submission request belongs to a co-site jump, if so, step S25 is performed, otherwise, step S26 is performed.

In step S25, the channel identifier of the previous co-located page cached in the server is obtained, and the channel identifier of the previous co-located page is cached in the server as a temporary channel identifier in association with the network service, and the process goes to step S11.

In step S26, the server caches a preset natural source identifier as a temporary channel identifier in association with the network traffic, and the process goes to step S11.

The service confirmation request and the service submission request in the embodiment of the present application may be from the same terminal device or the same browser. It should be understood that the present application is not limited thereto, and in practical applications, the service confirmation request and the service submission request may be from different terminal devices or from different browsers. It is to be understood that in some embodiments of the present application, the terminal device or browser does not store the channel identification.

The source channel identification of the network service is stored in the server side without depending on the normal use of Cookie of a user browser, and the correct service source attribution can still be achieved under the condition of not using the Cookie. In addition, by acquiring the channel identifier and caching the channel identifier in the server when the service submission request is processed, for the cross-device condition, no matter the user switches from the PC end to the mobile end or switches to the browser traceless mode, the initial channel source tracking can be ensured, and the correct service source attribution is realized.

Fig. 2 is a schematic flow chart of a network data processing method according to another embodiment of the present application, and in this embodiment, the network data processing method of the present application is described in more detail by taking an application to an online car rental application as an example, which can be understood that the present application is not limited thereto. Referring to fig. 2, a method of an embodiment of the present application includes:

in step S101, the server receives a request for placing an order of a car rental service of a user, which is sent by the terminal device.

In step S102, the server determines whether the received order placing request carries a channel identifier, if so, the channel identifier carried in the order placing request is cached in association with the car rental service of the user as a temporary channel identifier in the server, and step S103 is executed, otherwise, step S105 is executed.

In one implementation, the server determines whether a channel identifier is embedded in a landing page URL (Uniform Resource Locator) of the received order request, and if so, the order request carries the channel identifier, otherwise, the order request is not carried.

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

In step S104, the server parses the page source from the ordering request, obtains the user identifier, and caches the page source and the user identifier as a cache key in association with the temporary channel identifier, and continues to execute step S108.

In one implementation, the HTTP referrer part in the order Request received by the server contains the Request URI, that is, the page source, and the server parses the Request URI from the order Request to know from which page the order Request is linked.

The user identifier is used to indicate which user issued the order placing request, and the user identifier is unique, and may be a user token generated according to a user name and a user password, for example.

In step S105, the server determines whether the order placing request is a co-site skip, if so, step S106 is executed, otherwise, step S107 is executed.

Under the condition that the order placing request received by the server does not carry the channel identification, the server judges whether the order placing request is jumped from other pages of the same website, namely whether the order placing request is jumped from the same site.

In step S106, the server obtains the cached channel identifier of the previous co-located page, and performs step S104 by using the channel identifier of the previous co-located page as a temporary channel identifier.

If the ordering request is from the same-station jump, which indicates that the channel identification is cached when the previous same-station page is processed, the page source and the user identification are used as cache keys, and the channel identification of the previous same-station page is used as a temporary channel identification and is cached in the server in a correlation mode with the cache keys.

The method for the server to obtain the page source and the user identifier can be implemented with reference to step S103, and is not described again.

In step S107, the server performs step S104 by using the preset natural source identifier as a temporary channel identifier.

If the order placing request does not carry the channel identification and is not originated from the same-station skip, the order placing request belongs to a natural source, and the preset natural source identification is taken as the temporary channel identification and the cache key is subjected to associated cache.

In step S108, the server returns an order request response corresponding to the order request to the terminal device, and the terminal device performs corresponding display after receiving the order request response.

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

And after the terminal equipment correspondingly displays according to the order placing request response, responding to the completion of the order placing operation of the user and sending an order confirmation request to the server.

In step S110, the server determines whether the received order confirmation request carries a channel identifier, if so, the server takes the channel identifier in the service confirmation request as a formal channel identifier, and executes step S111, otherwise, executes step S112.

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

In step S111, the server associates and stores the order number of the rental service of the user with the formal channel identifier, and ends the process.

Under the condition that the order confirmation request received by the server carries the channel identification, directly considering that the order comes from the channel corresponding to the channel identification in the order confirmation request according to the last attribution principle, and taking the channel identification in the service confirmation request as a formal channel identification to be stored in association with the order number of the taxi renting service of the user.

In step S112, the server parses the page source from the order confirmation request, obtains the user identifier, and uses the page source and the user identifier as a cache key, obtains a cached temporary channel identifier corresponding to the cache key, and uses the temporary channel identifier as a formal channel identifier, and executes step S111.

Under the condition that 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 a formal channel identifier, and the formal channel identifier is stored in association with the order number of the car renting service of the user.

Fig. 3 is a schematic structural diagram of a network device according to an embodiment of the present application.

Referring to fig. 3, a network device 300 includes a memory 301 and a processor 302.

The Processor 302 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 301 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions for the processor 302 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. In addition, the memory 301 may comprise any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic and/or optical disks, may also be employed. In some embodiments, memory 301 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, dual layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disc, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.

The memory 301 has stored thereon executable code that, when processed by the processor 602, may cause the processor 302 to perform some or all of the methods described above.

The aspects of the present application have been described in detail hereinabove with reference to the accompanying drawings. In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. Those skilled in the art should also appreciate that acts and modules referred to in the specification are not necessarily required in the present application. In addition, it can be understood that the steps in the method of the embodiment of the present application may be sequentially adjusted, combined, and deleted according to actual needs, and the modules in the device of the embodiment of the present application may be combined, divided, and deleted according to actual needs.

Furthermore, the method according to the present application may also be implemented as a computer program or computer program product comprising computer program code instructions for performing some or all of the steps of the above-described method of the present application.

Alternatively, the present application may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) which, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform some or all of the various steps of the above-described method according to the present application.

Those of skill would 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 combinations of both.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Having described embodiments of the present application, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or improvements to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for processing network data, comprising:

2. The network data processing method of claim 1, further comprising, prior to receiving a service confirmation request for network service of at least one user:

receiving a service submission request of the network service of the user;

3. The network data processing method of claim 2, further comprising after determining whether the service submission request carries a channel identifier:

under the condition that the service submission request does not carry a channel identifier, judging whether the service submission request belongs to the same-station skip;

under the condition that the service submission request does not belong to the same-station skip, a preset natural source identifier is taken as a temporary channel identifier in a server and is cached in association with the network service;

4. The network data processing method of claim 2, wherein the caching of the temporary channel identification in association with the network traffic comprises:

and performing associated cache on the page source and the user identification as cache keys and the formal channel identification.

5. The network data processing method of claim 2, wherein the service confirmation request and the service submission request are from different terminal devices or from different browsers.

6. The network data processing method of claim 5, wherein the terminal device or browser does not store a channel identification.

7. The network data processing method of claim 1, wherein obtaining the temporary channel identification corresponding to the network traffic cached in a server comprises:

8. The network data processing method of claim 7,

the page source is a Request URI contained in an HTTP referrer part of the service confirmation Request; and/or

9. The network data processing method of any of claims 1 to 8, wherein the formal channel identification being stored in association with the network service comprises:

acquiring a service number of the network service;

10. A network device, comprising:

a processor; and

a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any one of claims 1 to 9.