CN113986954B - User event acquisition method and device, intelligent terminal and readable storage medium - Google Patents

User event acquisition method and device, intelligent terminal and readable storage medium Download PDF

Info

Publication number
CN113986954B
CN113986954B CN202111637086.5A CN202111637086A CN113986954B CN 113986954 B CN113986954 B CN 113986954B CN 202111637086 A CN202111637086 A CN 202111637086A CN 113986954 B CN113986954 B CN 113986954B
Authority
CN
China
Prior art keywords
user
rule
event
target
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111637086.5A
Other languages
Chinese (zh)
Other versions
CN113986954A (en
Inventor
陈洪权
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Mingyuan Cloud Technology Co Ltd
Original Assignee
Shenzhen Mingyuan Cloud Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Mingyuan Cloud Technology Co Ltd filed Critical Shenzhen Mingyuan Cloud Technology Co Ltd
Priority to CN202111637086.5A priority Critical patent/CN113986954B/en
Publication of CN113986954A publication Critical patent/CN113986954A/en
Application granted granted Critical
Publication of CN113986954B publication Critical patent/CN113986954B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/242Query formulation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/215Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/242Query formulation
    • G06F16/2433Query languages

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Computational Linguistics (AREA)
  • Quality & Reliability (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The invention discloses a user event acquisition method and device, an intelligent terminal and a readable storage medium, and belongs to the field of data analysis. The method comprises the following steps: recording the full event data of a user, and cleaning the full event data according to a preset service logic to obtain a full fact table; when an input user rule switching instruction is received, determining a target rule corresponding to the user rule switching instruction in preset user rules; and acquiring target event data corresponding to the target rule in the total fact table according to the target rule. By applying the user event acquisition method to the intelligent terminal, the efficiency of analyzing the user event can be greatly improved, and the target event data can be acquired in a multi-dimensional manner, so that the user behavior is analyzed more flexibly and changeably.

Description

User event acquisition method and device, intelligent terminal and readable storage medium
Technical Field
The invention relates to the field of data analysis, in particular to a user event acquisition method and device, an intelligent terminal and a readable storage medium.
Background
In the big data age, analysis of user behavior is becoming more and more critical, as it concerns the positioning of software products and the trend of the industry into the future. Various behaviors of the user are defined and analyzed through events, and the events record various specific operations of the user in the process of using the software/website, such as clicking of a button and displaying of a page. In the field of data analysis, one or more events are often used to table user behavior. The premise of analyzing various behaviors of the user is that various event rules or behavior rules need to be configured, and the specific behaviors of the user are recorded in a database when the specific behaviors of the user meet preset event rules, so that the user and developers can analyze the behaviors of the user conveniently. Therefore, the event rule making is important for analyzing user behavior data, and for the user event rule making for analyzing specific user behaviors, the following two schemes are available:
and in the first scheme, after a brand-new rule is formulated or the original rule is modified, the user behavior data is traced and cleaned again. The disadvantages of this solution are: performance is less than ideal and resource consumption is high and time consuming.
Scheme two, the fixed rule does not change. The disadvantages of this solution are: and the method does not support multi-dimensional rule switching and is not flexible enough.
The two common existing schemes are inconvenient for a user to obtain target data required by analyzing user behaviors, so that a technical scheme capable of efficiently and accurately obtaining the target data is urgently needed to overcome the defects of the existing technical scheme.
Disclosure of Invention
The invention provides a user event acquisition method, a user event acquisition device, an intelligent terminal and a readable storage medium, and aims to solve the technical problem of how to efficiently and accurately acquire target data required by analyzing a user event.
In order to achieve the above object, the present invention provides a user event acquiring method, which comprises the following steps:
recording the full event data of a user, and cleaning the full event data according to a preset service logic to obtain a full fact table;
when an input user rule switching instruction is received, determining a target rule corresponding to the user rule switching instruction in preset user rules;
and acquiring target event data corresponding to the target rule in the total fact table according to the target rule.
Optionally, the step of obtaining, according to the target rule, target event data corresponding to the target rule in the total fact table includes:
determining a structured query statement template corresponding to the target rule according to the target rule;
extracting keyword fields in the target rule, and filling the keyword fields into the structured query statement template to obtain a target structured query statement;
and acquiring target event data corresponding to the target rule in the full-scale fact table according to the target structured query statement.
Optionally, before the step of determining the target rule corresponding to the user rule switching instruction in the preset user rule when the input user rule switching instruction is received, the method includes:
receiving input event type, event times, user active time and rule name, and packaging the event type, the event times, the user active time and the rule name into a preset user rule.
Optionally, after the step of obtaining the target event data corresponding to the target rule in the total fact table according to the target rule, the method includes:
and when an input query instruction is received, converting the target event data into visual data corresponding to the query instruction.
Optionally, after the step of obtaining the target event data corresponding to the target rule in the total fact table, the method further includes:
receiving an input user switching instruction, and determining a cleaning condition corresponding to the user switching instruction;
and acquiring event cleaning data corresponding to the cleaning conditions in the target event data according to the cleaning conditions.
Optionally, after the step of obtaining event cleansing data corresponding to the cleansing condition in the target event data, the method includes:
and when an input query instruction is received, converting the event cleaning data into visual data corresponding to the query instruction.
Optionally, the step of recording the full amount of event data of the user includes:
determining an output current page, and collecting all behavior data corresponding to the current page;
and acquiring a recording rule corresponding to the current page, and recording the full event data corresponding to the recording rule in all the behavior data.
In addition, to achieve the above object, the present invention provides a user event acquiring apparatus, including:
the data acquisition module is used for recording the full event data of a user and cleaning the full event data according to preset service logic to obtain a full fact table;
the data filtering module is used for determining a target rule corresponding to the user rule switching instruction in preset user rules when receiving the input user rule switching instruction; and acquiring target event data corresponding to the target rule in the total fact table according to the target rule.
In addition, to achieve the above object, the present invention further provides an intelligent terminal, including a memory, a processor, and a user event acquisition program stored in the memory and executable on the processor, wherein: the user event acquisition program, when executed by the processor, implements the steps of the user event acquisition method as described above.
In addition, to achieve the above object, the present invention further provides a readable storage medium, on which a user event acquisition program is stored, the user event acquisition program, when executed by a processor, implementing the steps of the user event acquisition method as described above.
According to the user event acquisition method, the step of acquiring the total fact table is firstly carried out by recording the total event data of the user and cleaning the total event data according to the preset service logic, all event data required by all enterprises or individuals can be cleaned and sorted to obtain the corresponding total fact table before the user configures various user rules (user attributes), the situation that a large amount of original all user data needs to be read, analyzed and backtracked and cleaned every time when the rules are slightly changed is avoided, the resource occupancy rate during each data processing is greatly reduced, the data processing efficiency is improved, the required event data are presented in the form of the data table, and the reading and the analysis of the event data are facilitated. And through the step of determining the target rule corresponding to the user rule switching instruction in the preset user rule when receiving the input user rule switching instruction, the user can randomly change the analysis rule when analyzing the event data of the user, so that all the event data in the total fact table can be comprehensively analyzed, the behavior of the user can be more flexibly analyzed, the user is not limited to the specific user rule, and even a common user without development experience can easily take the place and apply the user. And finally, the target event data required by the user can be quickly read from the full-scale fact table through the step of acquiring the target event data corresponding to the target rule from the full-scale fact table according to the target rule, so that the user can conveniently and efficiently analyze the target data.
Drawings
Fig. 1 is a schematic terminal structure diagram of a hardware operating environment of an intelligent terminal according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a user event obtaining method according to a first embodiment of the present invention;
fig. 3 is a schematic diagram of a user rule configuration interface according to a first embodiment of the user event obtaining method of the present invention;
fig. 4 is a frame structure diagram of a user event acquisition apparatus according to the user event acquisition method of the present invention.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, fig. 1 is a schematic terminal structure diagram of a hardware operating environment of an intelligent terminal according to an embodiment of the present invention.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may comprise a Display (Display), an input unit such as a control panel, and the optional user interface 1003 may also comprise a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a 5G interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001. A user event acquisition program may be included in the memory 1005, which is a kind of computer storage medium.
Optionally, the terminal may further include a microphone, a speaker, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a wireless module, and the like. The sensors, such as light sensors, acceleration sensors, image sensors, and other sensors, are not described in detail herein.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 2, fig. 2 is a schematic flow chart of a first embodiment of a user event obtaining method of the present invention, and in this embodiment, the method includes:
step S10, recording the full event data of the user, and cleaning the full event data according to the preset service logic to obtain a full fact table;
in this embodiment, the intelligent terminal or the server may store all behavior data records predefined as events when the user uses various web pages or various software, perform data cleaning on the stored full amount of event data according to the business direction and the business type related to each enterprise or individual user, and obtain the full amount fact table after the data cleaning processing. For example, a DataWorks tool of the arrik cloud can be used to wash the full amount of event data according to the business logic to obtain a full amount of event table and store the full amount of event table in the DataWorks, and when a local server or an intelligent terminal needs to call related data, the full amount of event table can be directly called from the DataWorks and used.
In actual work, a product will define all user behavior events related to the enterprise service as much as possible, make a text form, deliver the text form to developers, and finally convert the text content of the events of the text form into computer language program codes, specifically, the bottom form of character strings is presented generally. Therefore, the business logic herein may be considered to include character strings corresponding to all events related to the business of the enterprise as much as possible, for example, for a room enterprise, if a user event such as a daily, weekly, monthly access frequency of a client or a website of the room enterprise software, a room-viewing button in a click page, a business consultant contact button, etc. is regarded as more important by an enterprise user, the preset character string corresponding to the user event can be set in the business logic.
Compared with the conventional means corresponding to the above technical means in this embodiment, all original user data are usually cleaned back after determining a user rule or a user attribute, but the data volume of the original user data is very large and cumbersome, and the efficiency is very affected in the whole process, and if all the original user data are stored for a long time, the resource occupation is accumulated to a very terrorist degree. It should be noted that the full event data is different from the original user data, where the original user data includes some data that cannot or is not suitable for defining an event, such as user account data, user instruction data, text data input by a user, and various behavior data that can be defined as an event, and so on, so the full event data belongs to the child data of the original user data, that is, various sets of behavior data that can be defined as an event.
In an embodiment, specifically, for the full amount of event data, the step of recording the full amount of event data of the user includes:
step a, determining an output current page, and collecting all behavior data corresponding to the current page;
and b, acquiring a recording rule corresponding to the current page, and recording the full event data corresponding to the recording rule in all the behavior data.
The current pages output may be web pages currently browsed by the user or software user interfaces currently browsed by the user, because each current page implies various user events that may be triggered, such as in an application example: the current user interface of a certain software comprises click events and corresponding character strings click: clicking a page front-end error event and a corresponding character string error by a user mouse: the front-end page console reports errors and corresponding character strings Console; APP crash event and corresponding string crash: the APP crash forces exit of the page loading event and the corresponding character string page _ load: front page loading page stop and corresponding character string page _ stay: triggering a first screen loading event and a corresponding character string fmp during page switching: page elements are first actively drawn, etc. The above-mentioned character strings corresponding to the events are behavior data corresponding to the current page, and the aggregate of them is all behavior data, it should be noted that the events corresponding to different pages may be repeated but generally not identical, and the corresponding triggerable events and the corresponding behavior data are also generally different in quantity.
No matter a user jumps to any other page from the current page through clicking or other commands, all the network pages and the software user interfaces are determined, and then based on the determination, a record rule corresponding to each determined network page or software user interface is determined. It should be noted that the recording rule refers to a rule for filtering all behavior data, that is, not all the acquired full event data are recorded, because such a change would cause a large pressure on the load of the system, which would affect the analysis efficiency and also have no help on analyzing the user behavior data, and the specific recording rule is related to the current focused business project of the enterprise, and may also be set according to actual needs, that is, not all the behavior data of each current page need to be recorded, for example, corresponding behavior data of a user returning to the previous page and exiting all pages may not be recorded, because it is not useful even for analyzing the user behavior focused on the current project.
In this embodiment, all user behavior data in the original user data can be screened and filtered to obtain all event data most useful for the currently addressed project, i.e., the total amount of event data to be recorded, so as to enhance the attentiveness of data processing, thereby increasing the speed of data processing.
Step S20, when receiving an input user rule switching instruction, determining a target rule corresponding to the user rule switching instruction in preset user rules;
after the user has personalized configuration or defaulted preset user rules (user attributes), the preset user rules can be directly selected or the current user rules can be switched on a visual interface, any user rule is selected on the basis of a user rule list presented by a plurality of preset user rules, namely, the system can be considered to input a corresponding user rule switching instruction, and the preset user rules selected by the user are determined.
In an embodiment, before the step of determining, when receiving an input user rule switching instruction, a target rule corresponding to the user rule switching instruction in a preset user rule, the method includes:
and c, receiving the input event type, event times, user active time and rule name, and packaging the event type, the event times, the user active time and the rule name into a preset user rule.
The user rules for configuring the preset user rules individually can be displayed in an intuitive and visual manner. Referring to fig. 3, fig. 3 is a schematic diagram of a user rule configuration interface according to a first embodiment of the user event obtaining method of the present invention. As shown, the user may directly select an event in the border option corresponding to the "trigger event", and may select all events stored in the full fact table in the border option. The "trigger event" herein corresponds to an event type. The event types here can be various page access events, network interface events, and various buried point events and non-buried point events. The user may then also configure the number of events, such as at least 5 in the graph. Additionally, multiple event types may be entered by clicking on the add event when configuring the user rules. Finally, the minimum activity duration of the user is set, namely the active duration of the user is set, for example, 5 minutes, the active user with the activity duration being more than or equal to the active duration of the user can be reserved, the rule name can be input randomly when being input, the personalized requirements of the user are met to the maximum extent, after the rule is set, the user rule can be automatically generated by clicking and determining without specially configuring underlying computer codes by the user, and the generated user rule is stored in an RDS (Relational Database Service) table to form a user rule table. Great convenience is brought to users. Or clicking cancel, the user rule configuration interface can be exited.
Step S30, according to the target rule, obtaining target event data corresponding to the target rule in the total fact table.
After the user rule is selected or switched by the user, the current target rule is determined, and all event data meeting the target rule, that is, target event data, are obtained in the total fact table by using the current target rule, for example, one user rule is: if the A button element is clicked more than 5 times in more than 3 minutes, all the event data of more than 5 times of clicking the A button element in more than 3 minutes is obtained from the full data table, the target event data is not only the purely recorded event, which is meaningless, but the event and the user information are stored in the full fact table in an associated manner, so that the characteristics of the user, such as the living city of the user, the gender of the user, the age of the user and the like, can be known when analyzing the specific event. The user information is saved to the full fact table when the full event data of the user is collected, or the user information can be saved to the full fact table before the full event data of the user is collected.
In an embodiment, after the step S30, the method further includes:
step d, receiving an input user switching instruction, and determining a cleaning condition corresponding to the user switching instruction;
and e, acquiring event cleaning data corresponding to the cleaning conditions in the target event data according to the cleaning conditions.
The user switching instruction comprises an actual user instruction and a device user instruction, wherein when the actual user instruction is received, the user is correspondingly switched to a service system user, namely an actual real user. When receiving the device user instruction, the corresponding is the user event data counted by taking the device commonly used by one or more real users as a unit for switching to the device identification user. For example, the character string corresponding to the actual user command in a specific application scenario is fct _ custom _ active _ real _ user _ v3, and the character string corresponding to the device user command is fct _ custom _ active _ user _ v 3. The character strings corresponding to the specific instructions can be used as cleaning conditions corresponding to user switching instructions, target event data are cleaned again according to the cleaning conditions, and only cleaned event data matched with the corresponding character strings in the target event data, namely event cleaning data, are reserved. It should be noted that, the user switching instruction may also add other instructions according to actual needs, such as user switching instructions corresponding to different operating systems: MacOs user instructions and Windows user instructions.
In this embodiment, event data corresponding to different user types are analyzed in a targeted manner, which can help users and related technicians to improve the level of analyzing data, so that the analyzing data is more flexible and diversified.
According to the user event acquisition method, the step of acquiring the total fact table is firstly carried out by recording the total event data of the user and cleaning the total event data according to the preset service logic, all event data required by all enterprises or individuals can be cleaned and sorted to obtain the corresponding total fact table before the user configures various user rules (user attributes), the situation that a large amount of original all user data needs to be read, analyzed and backtracked and cleaned every time when the rules are slightly changed is avoided, the resource occupancy rate during each data processing is greatly reduced, the data processing efficiency is improved, the required event data are presented in the form of the data table, and the reading and the analysis of the event data are facilitated. And through the step of determining the target rule corresponding to the user rule switching instruction in the preset user rule when receiving the input user rule switching instruction, the user can randomly change the analysis rule when analyzing the event data of the user, so that all the event data in the total fact table can be comprehensively analyzed, the behavior of the user can be more flexibly analyzed, the user is not limited to the specific user rule, and even a common user without development experience can easily take the place and apply the user. And finally, the target event data required by the user can be quickly read from the full-scale fact table through the step of acquiring the target event data corresponding to the target rule from the full-scale fact table according to the target rule, so that the user can conveniently and efficiently analyze the target data.
Further, a second embodiment of the user event obtaining method of the present invention is proposed based on the first embodiment of the user event obtaining method of the present invention, and in this embodiment, the step S30 includes:
step f, determining a structured query statement template corresponding to the target rule according to the target rule;
step g, extracting keyword fields in the target rule, and filling the keyword fields into the structured query statement template to obtain a target structured query statement;
and h, acquiring target event data corresponding to the target rule in the full-scale fact table according to the target structured query statement.
In a preset query statement template mapping table, the event type corresponding to the target rule is stored in association with the structured query statement template, and when the target rule is determined, the structured query statement can be obtained from the mapping table. For example, the target rule is that an active user with an active duration of more than 10 minutes (600 s) browses a B web page more than 20 times, the extracted event type is "browse B web page", and the corresponding template of the structured query statement is select from app _ custom _ analysis _ rules where name = a and time > a and active _ time = a, where a in the template represents content to be filled. Extracting the keyword fields 10, page _ state, and 20 in the target rule, and filling the keyword fields into the content to be filled in the structured query statement template to obtain the target structured query statement select from app _ store _ analysis _ rules where name = page _ state and times > 20 and active _ time = 600.
After the target structured query statement is obtained through automatic filling, target event data can be queried in the full fact table through the target structured query statement, and the queried target event data is presented to a user or a related development technician for specific user behavior analysis.
In the embodiment, a user does not need to understand or skillfully master the structured query statement to query and acquire data, and only needs to simply configure the user rule on the visual rule configuration interface, the structured query statement can be automatically generated according to the user rule, and the target event data can be found according to the structured query statement.
In one embodiment, after step S30 and also after step h, the method includes:
step i, when an input query instruction is received, converting the target event data into visual data corresponding to the query instruction.
In this embodiment, the query instruction also refers to various analysis instructions, such as analysis instructions including trend analysis instructions, usage proportion analysis instructions, regional distribution analysis instructions, and the like. According to different analysis instructions, the corresponding visualization model is different, wherein the visualization model is an icon model. For example, the region distribution analysis instruction mainly converts target event data into an intuitive map region model, so that targeted region-by-region analysis can be performed on users in various regions. And the visualization model corresponding to the proportion analysis instruction can be a pie chart or a bar chart and the like.
By the embodiment, the target event data with poor readability can be converted into various visual data, multi-dimensional analysis of user behaviors by a user is greatly facilitated, and analysis efficiency is improved.
After the step of acquiring event cleansing data corresponding to the cleansing condition in the target event data, the method includes:
and j, when receiving an input query instruction, converting the event cleaning data into visual data corresponding to the query instruction.
Similarly, the specific expansion step of step j may refer to the above embodiments, and is not described herein again.
As shown in fig. 4, fig. 4 is a frame structure diagram of a user event acquiring device according to the user event acquiring method of the present invention. In addition, the present invention further provides a user event acquiring apparatus, including:
the data acquisition module A10 is used for recording the full event data of a user and cleaning the full event data according to preset service logic to obtain a full fact table;
the data filtering module A20 is configured to, when receiving an input user rule switching instruction, determine a target rule corresponding to the user rule switching instruction in a preset user rule; and acquiring target event data corresponding to the target rule in the total fact table according to the target rule.
Optionally, the data filtering module a20 is further configured to:
determining a structured query statement template corresponding to the target rule according to the target rule;
extracting keyword fields in the target rule, and filling the keyword fields into the structured query statement template to obtain a target structured query statement;
and acquiring target event data corresponding to the target rule in the full-scale fact table according to the target structured query statement.
Optionally, the data filtering module a20 is further configured to:
receiving input event type, event times, user active time and rule name, and packaging the event type, the event times, the user active time and the rule name into a preset user rule.
Optionally, the data filtering module a20 is further configured to:
and when an input query instruction is received, converting the target event data into visual data corresponding to the query instruction.
Optionally, the data filtering module a20 is further configured to:
receiving an input user switching instruction, and determining a cleaning condition corresponding to the user switching instruction;
and acquiring event cleaning data corresponding to the cleaning conditions in the target event data according to the cleaning conditions.
Optionally, the data filtering module a20 is further configured to:
and when an input query instruction is received, converting the event cleaning data into visual data corresponding to the query instruction.
Optionally, the data acquisition module a10 is further configured to:
determining an output current page, collecting all behavior data corresponding to the current page,
and acquiring a recording rule corresponding to the current page, and recording the full event data corresponding to the recording rule in all the behavior data.
The specific implementation of the user event obtaining device of the present invention is basically the same as that of the above-mentioned user event obtaining method, and is not described herein again.
In addition, the present invention further provides an intelligent terminal, where the intelligent terminal includes a memory, a processor, and a user event acquisition program stored in the memory and operable on the processor, and the processor implements the steps of the user event acquisition method according to the above embodiment when executing the user event acquisition program.
The specific implementation of the intelligent terminal of the present invention is basically the same as the embodiments of the user event obtaining method described above, and is not described herein again.
Furthermore, the present invention also provides a readable storage medium, which may be a computer readable storage medium, and includes a user event acquiring program, and when the user event acquiring program is executed by a processor, the user event acquiring program implements the steps of the user event acquiring method according to the above embodiment.
The specific implementation of the readable storage medium of the present invention is substantially the same as the embodiments of the user event obtaining method described above, and is not described herein again.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a television, a mobile phone, a computer, a server, a vehicle machine, or a network device) to execute the method according to the embodiments of the present invention.
In the present invention, the terms "first", "second", "third", "fourth" and "fifth" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, and those skilled in the art can understand the specific meanings of the above terms in the present invention according to specific situations.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although the embodiment of the present invention has been shown and described, the scope of the present invention is not limited thereto, it should be understood that the above embodiment is illustrative and not to be construed as limiting the present invention, and that those skilled in the art can make changes, modifications and substitutions to the above embodiment within the scope of the present invention, and that these changes, modifications and substitutions should be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (7)

1. A user event acquisition method is characterized by comprising the following steps:
recording the full event data of a user, and cleaning the full event data through a DataWorks tool and preset business logic to obtain a full fact table;
when an input user rule switching instruction is received, determining a target rule corresponding to the user rule switching instruction in preset user rules;
acquiring target event data corresponding to the target rule in the total fact table according to the target rule;
the step of recording the full amount of event data of the user comprises the following steps:
determining an output current page, and collecting all behavior data corresponding to the current page;
determining a mark code of the current page, and acquiring a recording rule corresponding to the mark code in a preset recording rule mapping table according to the mark code;
recording the full event data corresponding to the recording rule in all the behavior data according to the recording rule;
after the step of obtaining the target event data corresponding to the target rule in the total fact table, the method further includes:
receiving an input user switching instruction, and determining a cleaning condition corresponding to the user switching instruction, wherein the user switching instruction comprises: actual user instructions, device user instructions, MacOs user instructions, and Windows user instructions; the cleaning condition comprises a character string fct _ custom _ active _ real _ user _ v3 corresponding to the actual user instruction and a character string fct _ custom _ active _ user _ v3 corresponding to the equipment user instruction;
acquiring event cleaning data corresponding to the cleaning conditions in the target event data according to the cleaning conditions;
after the step of obtaining event cleansing data corresponding to the cleansing condition in the target event data, the method includes:
when an input query instruction is received, determining a visual model corresponding to the query instruction;
according to the visualization model, the event cleaning data are converted into visualization data corresponding to the query instruction, wherein the query instruction comprises: trend analysis instructions, usage proportion analysis instructions, and regional distribution analysis instructions.
2. The method for acquiring user event according to claim 1, wherein the step of acquiring target event data corresponding to the target rule in the total fact table according to the target rule includes:
determining a structured query statement template corresponding to the target rule according to the target rule;
extracting keyword fields in the target rule, and filling the keyword fields into the structured query statement template to obtain a target structured query statement;
and acquiring target event data corresponding to the target rule in the full-scale fact table according to the target structured query statement.
3. The method for acquiring a user event according to claim 1, wherein before the step of determining the target rule corresponding to the user rule switching instruction in the preset user rule when receiving the input user rule switching instruction, the method comprises:
receiving input event type, event times, user active time and rule name, and packaging the event type, the event times, the user active time and the rule name into a preset user rule.
4. The method for acquiring user event according to claim 1, wherein the step of acquiring target event data corresponding to the target rule in the total fact table according to the target rule is followed by:
and when an input query instruction is received, converting the target event data into visual data corresponding to the query instruction.
5. A user event acquisition apparatus, characterized in that the user event acquisition apparatus comprises:
the data acquisition module is used for recording the full event data of the user and cleaning the full event data through a DataWorks tool and preset business logic to obtain a full fact table;
the step of recording the full amount of event data of the user comprises the following steps:
determining an output current page, and collecting all behavior data corresponding to the current page;
determining a mark code of the current page, and acquiring a recording rule corresponding to the mark code in a preset recording rule mapping table according to the mark code;
recording the full event data corresponding to the recording rule in all the behavior data according to the recording rule;
the data filtering module is used for determining a target rule corresponding to the user rule switching instruction in preset user rules when receiving the input user rule switching instruction; acquiring target event data corresponding to the target rule in the total fact table according to the target rule;
after the step of obtaining the target event data corresponding to the target rule in the total fact table, the method further includes:
receiving an input user switching instruction, and determining a cleaning condition corresponding to the user switching instruction, wherein the user switching instruction comprises: actual user instructions, device user instructions, MacOs user instructions, and Windows user instructions; the cleaning condition comprises a character string fct _ custom _ active _ real _ user _ v3 corresponding to the actual user instruction and a character string fct _ custom _ active _ user _ v3 corresponding to the equipment user instruction;
acquiring event cleaning data corresponding to the cleaning conditions in the target event data according to the cleaning conditions;
after the step of obtaining event cleansing data corresponding to the cleansing condition in the target event data, the method includes:
when an input query instruction is received, determining a visual model corresponding to the query instruction;
according to the visualization model, the event cleaning data are converted into visualization data corresponding to the query instruction, wherein the query instruction comprises: trend analysis instructions, usage proportion analysis instructions, and regional distribution analysis instructions.
6. An intelligent terminal, comprising a memory, a processor, and a user event acquisition program stored on the memory and executable on the processor, wherein: the user event acquisition program, when executed by the processor, implements the steps of the user event acquisition method of any one of claims 1 to 4.
7. A readable storage medium, having a user event acquisition program stored thereon, which when executed by a processor implements the steps of the user event acquisition method according to any one of claims 1 to 4.
CN202111637086.5A 2021-12-30 2021-12-30 User event acquisition method and device, intelligent terminal and readable storage medium Active CN113986954B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111637086.5A CN113986954B (en) 2021-12-30 2021-12-30 User event acquisition method and device, intelligent terminal and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111637086.5A CN113986954B (en) 2021-12-30 2021-12-30 User event acquisition method and device, intelligent terminal and readable storage medium

Publications (2)

Publication Number Publication Date
CN113986954A CN113986954A (en) 2022-01-28
CN113986954B true CN113986954B (en) 2022-04-08

Family

ID=79734912

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111637086.5A Active CN113986954B (en) 2021-12-30 2021-12-30 User event acquisition method and device, intelligent terminal and readable storage medium

Country Status (1)

Country Link
CN (1) CN113986954B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117014247A (en) * 2023-08-28 2023-11-07 广东金朋科技有限公司 Scene generation method, system and storage medium based on state learning

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105183489A (en) * 2015-10-10 2015-12-23 南京国电南自轨道交通工程有限公司 Extjs frame based intelligent data analysis system and method
CN106649718A (en) * 2016-12-22 2017-05-10 盐城工学院 Large data acquisition and processing method for PDM system
CN111177180A (en) * 2019-12-11 2020-05-19 北京百分点信息科技有限公司 Data query method and device and electronic equipment
CN111767201A (en) * 2020-06-29 2020-10-13 百度在线网络技术(北京)有限公司 User behavior analysis method, terminal device, server and storage medium
CN112948226A (en) * 2021-02-05 2021-06-11 中国建设银行股份有限公司 User portrait drawing method and device
CN113609158A (en) * 2021-08-12 2021-11-05 国家电网有限公司大数据中心 SQL statement generation method, device, equipment and medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3814820B2 (en) * 1999-08-10 2006-08-30 セイコーエプソン株式会社 Image input / output device
CN107807764B (en) * 2017-10-27 2020-10-13 优酷网络技术(北京)有限公司 Page display method and client
CN108347652B (en) * 2018-02-24 2020-01-14 华南理工大学 Method and system for recommending IPTV live broadcast channel by using artificial neural network
CN111629406B (en) * 2019-02-28 2021-09-07 华为技术有限公司 Method for switching processing, related device, program product and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105183489A (en) * 2015-10-10 2015-12-23 南京国电南自轨道交通工程有限公司 Extjs frame based intelligent data analysis system and method
CN106649718A (en) * 2016-12-22 2017-05-10 盐城工学院 Large data acquisition and processing method for PDM system
CN111177180A (en) * 2019-12-11 2020-05-19 北京百分点信息科技有限公司 Data query method and device and electronic equipment
CN111767201A (en) * 2020-06-29 2020-10-13 百度在线网络技术(北京)有限公司 User behavior analysis method, terminal device, server and storage medium
CN112948226A (en) * 2021-02-05 2021-06-11 中国建设银行股份有限公司 User portrait drawing method and device
CN113609158A (en) * 2021-08-12 2021-11-05 国家电网有限公司大数据中心 SQL statement generation method, device, equipment and medium

Also Published As

Publication number Publication date
CN113986954A (en) 2022-01-28

Similar Documents

Publication Publication Date Title
CN109739717B (en) Page data acquisition method and device and server
US7917815B2 (en) Multi-layer context parsing and incident model construction for software support
CN111818123B (en) Network front-end remote playback method, device, equipment and storage medium
US20140006000A1 (en) Built-in response time analytics for business applications
CN112433712A (en) Report display method and device, computer equipment and storage medium
CN113986954B (en) User event acquisition method and device, intelligent terminal and readable storage medium
CN112667716A (en) Data processing method and device, electronic equipment and storage medium
CN110266555B (en) Method for analyzing website service request
CN111581067A (en) Data acquisition method and device
CN114185750A (en) Process monitoring method, device, equipment and storage medium
CN110674404A (en) Link information generation method, device, system, storage medium and electronic equipment
CN110955438A (en) Method, device and equipment for monitoring performance of small program and storage medium
CN113535135A (en) Software development method and device, computer equipment and storage medium
CN112817817A (en) Buried point information query method and device, computer equipment and storage medium
CN110457089B (en) Data acquisition method, data acquisition device, computer readable storage medium and computer equipment
CN115981643A (en) Configuration method, system, equipment and storage medium of business association component
CN115794545A (en) Automatic processing method of operation and maintenance data and related equipment thereof
CN114691837B (en) Insurance business data processing method and processing system based on big data
CN113674023A (en) Rights upgrading method, device, equipment and storage medium based on member level
CN109992614B (en) Data acquisition method, device and server
CN112785418A (en) Credit risk modeling method, credit risk modeling device, credit risk modeling equipment and computer readable storage medium
CN111553749A (en) Activity push strategy configuration method and device
CN112835774A (en) Visualization method and device for performance of display card, equipment and computer-readable storage medium
CN113704288A (en) Data display method and device, computer readable medium and electronic equipment
CN112416699A (en) Index data collection method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant