CN111581518A - Information pushing method and device - Google Patents
Information pushing method and device Download PDFInfo
- Publication number
- CN111581518A CN111581518A CN202010407523.3A CN202010407523A CN111581518A CN 111581518 A CN111581518 A CN 111581518A CN 202010407523 A CN202010407523 A CN 202010407523A CN 111581518 A CN111581518 A CN 111581518A
- Authority
- CN
- China
- Prior art keywords
- information
- trigger
- user
- operation behavior
- user operation
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
Abstract
The application discloses an information pushing method and device, and particularly relates to the technical field of information processing. One embodiment of the method comprises: receiving trigger rule information and trigger action information sent by a development end, wherein the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information; matching with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side; and responding to the successful matching, and pushing the trigger action information to the user terminal. The implementation mode effectively improves the pertinence and the effectiveness of information pushing.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to the field of information processing technologies, and in particular, to an information push method and apparatus.
Background
With the internet era entering the final stage of flow dividend, the operation is more and more difficult to continue depending on the extensive subsidy of large flow in the past. Meanwhile, the rise of big data technology enables the analysis of massive user behaviors to become practical. How to combine big data technology and operation means to activate the stock user is an urgent need.
At present, the general scheme in the industry is to store collected user behavior data, submit rules to screen out crowds when operation activities need to be performed, submit the crowds to corresponding developers according to a list to perform product development, and bring developed products on line.
Disclosure of Invention
The embodiment of the application provides an information pushing method, an information pushing device, information pushing equipment and a storage medium.
According to a first aspect, the present embodiment provides an information pushing method, including: receiving trigger rule information and trigger action information sent by a development end, wherein the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information; matching with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side; and responding to the successful matching, and pushing the trigger action information to the user terminal.
According to a second aspect, the present embodiment provides an information pushing method, including: sending user operation behavior information to a background server; receiving trigger action information pushed by a background server, wherein the trigger action information meets the trigger rule information pushing requirement by the background server based on user operation behavior information; and executing the action indicated by the trigger action information.
According to a third aspect, the present embodiment provides an information pushing method, including: receiving trigger rule information and trigger action information set by a user through a preset rule setting page; and sending the trigger rule information and the trigger action information to a background server so that the background server responds to the matching of the user operation behavior information acquired from the user side and the trigger rule information and pushes the trigger action information to the user side.
According to a fourth aspect, the present embodiment provides an information pushing apparatus, including: the receiving module is configured to receive trigger rule information and trigger action information sent by the development end, the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and trigger time, and the trigger action information is action information which is executed by a trigger user end when user operation behavior information meets the trigger rule information; the matching module is configured to respond to the received user operation behavior information collected by the user terminal and match the user operation behavior information with the trigger rule information; and the pushing module is configured to respond to the matching success and push the triggering action information to the user terminal.
According to a fifth aspect, the present embodiment provides an information pushing apparatus, including: a first sending module configured to send user operation behavior information to a background server; the first receiving module is configured to receive the triggering action information pushed by the background server, and the triggering action information meets triggering rule information pushing requirements by the background server based on the user operation behavior information; and the first execution module is configured to execute the action indicated by the trigger action information.
According to a sixth aspect, the present embodiment provides an information pushing apparatus, including: the second receiving module is configured to receive trigger rule information and trigger action information set by a setting user through a preset rule setting page; the second sending module is configured to send the trigger rule information and the trigger action information to the background server so that the background server pushes the trigger action information to the user side in response to the matching of the user operation behavior information collected from the user side and the trigger rule information.
According to a seventh aspect, the present embodiment provides an electronic device comprising one or more processors; a storage device having one or more programs stored thereon, which when executed by the one or more processors, cause the one or more processors to implement the method as described in any of the implementations of the first aspect or the method as described in any of the implementations of the second aspect or the method as described in any of the implementations of the third aspect.
According to an eighth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a method as described in any of the implementations of the first aspect or implements a method as described in any of the implementations of the second aspect or implements a method as described in any of the implementations of the third aspect.
The method comprises the steps that trigger rule information and trigger action information sent by a development end are received, the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information; matching with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side; and in response to successful matching, the triggering action information is pushed to the user side, so that the triggering action information is pushed to the user side corresponding to the user operation behavior information meeting the triggering rule information, the pushing range of the triggering action information is narrowed, and the pertinence and the effectiveness of information pushing are effectively improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of an information push method according to the present application;
FIG. 3 is a schematic diagram of an application scenario of an information push method according to the present application;
FIG. 4 is a flow diagram of another embodiment of an information push method according to the present application;
fig. 5 is a flowchart of an embodiment of a user side of an information pushing method according to the present application;
FIG. 6 is a flow diagram of one embodiment of an originating terminal of an information push method according to the present application;
FIG. 7 is a schematic diagram of one embodiment of an information pushing device according to the present application;
FIG. 8 is a schematic block diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the information push method of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as a search-type application, a shopping-type application, and the like.
The terminal apparatuses 101, 102, and 103 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like. When the terminal apparatuses 101, 102, 103 are software, they can be installed in the electronic apparatuses listed above. It may be implemented as a plurality of software or software modules (for example, for providing an information push service), or as a single software or software module. And is not particularly limited herein.
The server 105 may be a server providing various services, for example, receiving the trigger rule information, the trigger action information, and the user operation behavior information uploaded by the terminal devices 101, 102, 103, and matching the user operation behavior information with the trigger rule information; and responding to the successful matching of the user operation behavior information and the trigger rule information, and pushing the trigger action information to the user side.
It should be noted that the information pushing method provided in the embodiment of the present application is generally executed by the server 105, and accordingly, the information pushing apparatus is generally disposed in the server 105.
It should be noted that the terminal devices 101, 102, and 103 may also be installed with an information push application, and the terminal devices 101, 102, and 103 may also perform trigger action information push based on the trigger rule information and the user operation behavior information, in this case, the information push method may also be executed by the terminal devices 101, 102, and 103, and accordingly, the information push apparatus may also be installed in the terminal devices 101, 102, and 103. At this point, the exemplary system architecture 100 may also not include the server 105 and the network 104.
The server 105 may be hardware or software. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of a plurality of servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules (for example, for providing an information push service), or may be implemented as a single software or software module. And is not particularly limited herein.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 2 shows a schematic flow diagram 200 of an embodiment of an information pushing method that can be applied to the present application. The information pushing method comprises the following steps:
In this embodiment, the execution subject (for example, the server 105 or the terminal devices 101, 102, and 103 in fig. 1) may directly receive the trigger rule information and the trigger action information submitted by the user, or may monitor the trigger rule information and the trigger action information submitted by the user in real time, which is not limited in this application.
The manner in which the user submits the trigger rule information and the trigger action information may be a manner in which an instruction is submitted in the prior art or a technology developed in the future, which is not limited in the present application. For example, the trigger rule information and the trigger action information are submitted through a preset rule setting page, the trigger rule information and the trigger action information are submitted by inputting an instruction in an instruction bar, the trigger rule information and the trigger action information are submitted through a preset voice acquisition device, and the like.
Here, the trigger rule information may include a first trigger rule and a second trigger rule, where the first trigger rule includes a target user class group, that is, a group range to which the target user belongs, for example, a target user class, a target user attribute, a terminal class corresponding to the target user, and so on; the second trigger rule includes a trigger event and a trigger occasion. The trigger event is used for indicating a user operation behavior which can trigger the user side to execute the action information, for example, a specified application program is opened for the second time within 1 day, a preset button is clicked for the third time within one day, and the like. The trigger time is used to indicate a specific time that will trigger the user end to execute the action information, for example, a time when the trigger event occurs, a time after a preset time period after the trigger event occurs, and the like.
And the triggering action information is the action information which is executed by the triggering user terminal when the user operation behavior information meets the triggering rule information. Here, the action indicated by the action information may be action information that the ue can be triggered to execute by an external instruction in the prior art or in a future developed technology. The trigger action information may include various information, for example, show popup data, present a reminder, perform a preset content display, perform a default operation, and the like, which is not limited in the present application.
In some alternative implementations, the target user class may include: the target user type and the terminal type corresponding to the target user.
In this implementation manner, the target user category is used to indicate group information to which the user belongs, for example, a newly logged-in user, a member user, a user with different permissions, and the like, and the terminal category corresponding to the target user is used to indicate an operating system type and/or model of a terminal used by the user, for example, an android system, an IOS system, a saiban system, and the like.
After the execution main body obtains the user operation behavior information, the user operation behavior information can be matched with the target user category to determine the user operation behavior information meeting the target user category, and then the user operation behavior information meeting the target user category is matched with the terminal category corresponding to the target user; the user operation behavior information may also be matched with the terminal category corresponding to the target user, and then the user operation behavior information meeting the terminal category corresponding to the target user category may be matched with the target user category, which is not limited in the present application.
In one specific example, the target user class group in the first trigger rule includes: the target user category is a member user, and the terminal category corresponding to the target user is an android system. After the execution main body obtains the user operation behavior information, the user operation behavior information can be firstly matched with the target user category, namely whether the user is a member user or not is judged, if the matching fails, the user operation behavior information is directly filtered, and if the matching succeeds, the user operation behavior information is further matched with the terminal category corresponding to the target user.
According to the implementation mode, the user category of the target user group and the terminal category corresponding to the target user are subdivided, so that the first trigger rule is further refined, and the pertinence and the effectiveness of the pushed information are further promoted.
In some optional implementations, the second triggering rule further includes: the number of triggers.
In this implementation, the triggering number is used to indicate the number of times that the user terminal is triggered to execute the action information, for example, 1 time per day 1 time, 1 time per day 2 times, and so on.
The implementation mode sets the second trigger rule and further comprises the trigger times, the second trigger rule is further refined, the trigger action information can be sent to the user side according to needs, the trigger action information is prevented from being omitted or frequently pushed to the user side by the user, and further user experience is prevented from being influenced.
In this embodiment, after receiving the user operation behavior information collected by the user side, the execution main body may directly match all the received user operation behavior information with the first trigger rule and the second trigger rule at the same time.
Here, the user operation behavior information is used for user information indicating an operation behavior of the user in a website or an application and performing the operation behavior. For example, identification information of the user, operation behavior of the user, behavior time of the user, behavior frequency of the user, behavior result of the user, and the like.
The behavior time of the user is used to indicate time information of the user performing the operation behavior, and may specifically include start time, end time, time period information and the like of the user performing the operation, for example, start time, end time and the like of the user opening a session. The behavior frequency of the user is used to indicate the number of times that the user performs the operation within a preset time period, for example, the number of times that the user performs the click operation within the preset time period.
In addition, the user operation behavior information may further include historical user operation behavior information.
It should be noted that the manner of collecting the user operation behavior information at the user end may include various manners, for example, a manner of Web log, a point burying technique, and the like. Here, the user terminal may be various terminal devices with a user operation behavior information collection function in the prior art or future development technology, such as a mobile phone, a tablet computer, a smart watch, and the like, which is not limited in this application.
The Web log means that the user operation behavior information is obtained through a log file, for example, the sending request time, the request detailed information, the request return state, and the like are obtained. The Web log mode can conveniently realize the reprocessing of the historical data, but cannot capture the operation behavior information defined by the user.
Preferably, in order to capture the operation behavior information defined by the user, the user terminal may obtain the operation behavior information of the user in a buried point manner.
Here, the buried points may include: a front end buried point and a rear end buried point. The front-end buried point can collect more detailed user operation behavior information, particularly behavior data which does not need to request a server, such as: page dwell time, page browsing depth, video play time, etc. However, the reporting of the front end buried point generally has about 15% of delayed reporting and missing reporting. The back-end buried point can collect the user operation behavior information in real time without delayed reporting. However, since the code embedding point needs to go through a complete embedding point process including business combing, embedding point design and the like, the whole process is relatively inefficient.
In some optional manners, the matching, by the execution main body, based on the user operation behavior information and the trigger rule information in response to receiving the user operation behavior information collected by the user side includes: and matching the user operation behavior information with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side through the SDK arranged in the application program.
In the implementation mode, the operation behavior information of the user at the client can be acquired as comprehensively as possible through the full-automatic embedded point. The complete embedded point process is not needed to be carried out for each acquisition of user operation behavior information by the full embedded point, and as long as an SDK (Software Development kit) is embedded in a product, a uniform embedded point is made, so that the whole process is efficient and convenient. The user-side application developer can embed the SDK into the application program in advance to collect the user operation behavior information.
Here, the software development kit SDK is a software development module that can implement a specific service function. A preset embedded point position for detecting user operation behaviors is set in the SDK, and when the user operation triggers the preset embedded point position, information such as an object, a method and time of the user operation can be recorded and stored. The preset embedded point position can be set according to actual requirements and specific application scenes.
According to the implementation mode, the user operation behavior information acquired by the user side through the SDK arranged in the application program is received, and the matching is carried out based on the user operation behavior information and the trigger rule information, so that the effectiveness and the instantaneity of the received user operation behavior information are improved, and the improvement of the instantaneity and the effectiveness of the matching is facilitated.
And step 204, responding to the successful matching, and pushing the trigger action information to the user side.
In this embodiment, the execution main body matches the user operation behavior information with the first trigger rule and the second trigger rule, and if the matching is successful, pushes the trigger action information to the user side corresponding to the user operation behavior information. The user terminal can execute the action indicated by the trigger action information after receiving the trigger action information.
In a specific example, the target user group of the first trigger rule in the trigger rule information is a new login user, the trigger event of the second trigger rule is that the preset application program is opened for the second time within 1 day, the trigger time is that the time delay is 15s after the preset application program is opened for the second time within 1 day, and the corresponding trigger action information is a popup window for displaying the notification message. The execution main body receives 200 pieces of user operation behavior information collected by 100 user terminals in total, matches the 200 pieces of user operation behavior information with the first trigger rule and the second trigger rule at the same time, wherein 10 pieces of user operation behavior information simultaneously meet the first trigger rule and the second trigger rule, and then the execution main body can push the trigger action information corresponding to the trigger rule information to the user terminals corresponding to the determined 10 pieces of user operation behavior information. After receiving the trigger action information, the user side can execute the operation of displaying the popup window containing the notification message, which is indicated by the trigger action information.
With continuing reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the information push method according to the present embodiment.
In the application scenario of fig. 3, the execution main body 301 receives trigger rule information 304 and trigger action information 305, which are set by the user 302 through a rule setting web page preset on the terminal device 303, where the trigger rule information includes a first trigger rule and a second trigger rule, for example, the first trigger rule is a member user, and the second trigger rule is a time when the number of times of clicking the buy-adding button in one day is greater than or equal to two times. The execution main body receives first user operation behavior information 307 acquired by a first user terminal 306 in real time, second user operation behavior information 309 acquired by a second user terminal 308 in real time, and third user operation behavior information 311 acquired by a third user terminal 310 in real time, where the user operation behavior information may include user behavior times, behavior time, and the like, for example, the first user operation behavior information 307 is a time when a general user clicks a buy-add button twice a day, the second user operation behavior information 309 is a time when a member user clicks the buy-add button once a day, and the third user operation behavior information 311 is a time when the member user clicks the buy-add button twice a day. After receiving the first user operation behavior information 307, the second user operation behavior information 309, and the third user operation behavior information 311, the execution subject performs a matching operation 312 on the user operation behavior information, which specifically includes: meanwhile, the first user operation behavior information 306, the second user operation behavior information 308, and the third user operation behavior information 310 are matched with the first trigger rule and the second trigger rule, and if the matching is successful, the trigger action information is pushed to a user side corresponding to the user operation behavior information meeting the trigger rule information, for example, the user side 313 corresponding to the third user operation behavior information.
The information push method provided by the embodiment of the disclosure includes receiving trigger rule information and trigger action information sent by a development end, wherein the trigger rule information includes a first trigger rule and a second trigger rule, the first trigger rule includes a target user group, the second trigger rule includes a trigger event and a trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information; matching with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side; and responding to the successful matching, pushing the trigger action information to the user side, and effectively improving the pertinence and effectiveness of information pushing.
With further reference to fig. 4, a flow 400 of yet another embodiment of an information push method is shown. The process 400 of the information pushing method of the embodiment may include the following steps:
In this embodiment, details of implementation and technical effects of step 401 may refer to the description of step 201, and are not described herein again.
In this embodiment, after receiving the user operation behavior information collected by the user side, the execution main body first matches the user operation behavior information with the first trigger rule for the first time, that is, determines whether the user operation behavior information belongs to a target user group of the first trigger rule, if matching is successful, the user operation behavior information is retained, and if matching is unsuccessful, the user operation behavior information is filtered.
And step 403, in response to the successful first matching, performing second matching on the user operation behavior information meeting the first trigger rule and the second trigger rule.
In this embodiment, the reserved user operation behavior information successfully matched with the first trigger rule is matched with the second trigger rule for the second time, that is, whether the reserved user operation behavior information successfully matched with the first trigger rule meets the trigger event and trigger time of the second trigger rule is judged, and if the matching is successful, the user operation behavior information meeting the first trigger rule and the second trigger rule is determined.
In a specific example, the execution subject receives 100 pieces of user operation behavior information collected by 100 user terminals in real time, where the user operation behavior information may include a start time and an end time of opening a preset application by a user, a number of times of opening the preset application, user identification information, and the like. The first trigger rule in the trigger rule information is a new login user, the second trigger rule is the moment when the preset application program is opened for the second time within 1 day, the execution main body firstly matches 100 pieces of user operation behavior information with the first trigger rule for the first time, and 50 pieces of user operation behavior information meeting the first trigger rule, namely the new login user, are screened out. And then, matching the 50 pieces of user operation behavior information meeting the first trigger rule with the second trigger rule for the second time, screening out 10 pieces of user operation behavior information meeting the second trigger rule, namely at the moment of opening the preset application program for the second time, and further determining the user side corresponding to the 10 pieces of user operation behavior information meeting the second trigger rule.
In addition, it should be noted that, if the number of the received user operation behavior information collected by the user side is greater than or equal to the preset number threshold, the execution main body may synchronize the trigger rule information, the trigger action information, and the user operation behavior information to the data center station.
The data center station is used for acquiring, calculating, storing and processing mass data through a data technology, and meanwhile unifies standards and calibers. After the data are unified by the data center, standard data can be formed and stored to form a big data asset layer, and then high-efficiency service is provided for users. The data center station is closer to the service, can respond to the requirements of service and application development more quickly, and can be traced and is more accurate.
The data center can quickly determine the user operation behavior information meeting the preset trigger rule according to the preset trigger rule, and can perform deep data analysis and mining according to the user operation behavior information.
And step 404, in response to the successful matching, pushing the trigger action information to the user side.
In this embodiment, details of implementation and technical effects of step 404 may refer to the description of step 203, and are not described herein again.
In the embodiment of the application, the user operation behavior information and the first trigger rule are matched for the first time by responding to the received user operation behavior information collected by the user side; and responding to the successful first matching, matching the user operation behavior information meeting the first triggering rule with the second triggering rule for the second time, determining the user side meeting the user operation behavior information meeting the triggering rule information and pushing the triggering action information, effectively improving the effectiveness and pertinence of the pushing information, improving the matching efficiency and further improving the information pushing efficiency.
With further reference to fig. 5, a flow 500 of one embodiment of a user side of an information push method is shown. The method can be executed by the terminal device 101, 102, 103 in fig. 1, and accordingly, the apparatus for pushing information can be disposed in the terminal device 101, 102, 103.
The method comprises the following steps:
In this embodiment, the execution main body (for example, the terminal devices 101, 102, and 103 in fig. 1) may collect the user operation behavior information in various ways, and send the user operation behavior information to the background server.
The method for collecting the user operation behavior information by the user side may include: web log mode, point burying techniques, etc.
In some optional manners, the sending the user operation behavior information to the background server includes: and sending the user operation behavior information acquired by the SDK arranged in the application program to the background server.
In this implementation, the execution agent may embed the SDK in the application to collect the user operation behavior information.
Here, the software development kit SDK is a software development module that can implement a specific service function. A preset embedded point position for detecting user operation behaviors is set in the SDK, and when the user operation triggers the preset embedded point position, information such as an object, a method and time of the user operation can be recorded and stored. The preset embedded point position can be set according to actual requirements and specific application scenes.
According to the implementation mode, the user operation behavior information acquired by the SDK arranged in the application program is sent to the background server, so that the effectiveness and the instantaneity of the user operation behavior information sent to the background server are improved.
In this embodiment, the trigger action information is pushed by the background server based on the information that the user operation behavior satisfies the trigger rule information.
And the triggering action information is the action information which is executed by the triggering user terminal when the user operation behavior information meets the triggering rule information. Here, the action indicated by the action information may include various actions, for example, displaying popup data, presenting a reminder, performing a presentation of a preset content, performing a default operation, and the like, which is not limited in this application.
In this embodiment, after receiving the trigger action information pushed by the background server, the execution main body may execute an action indicated by the trigger action information.
In some optional manners, the performing the action indicated by the trigger action information includes:
and executing the display popup window data indicated by the trigger action information.
In this implementation, the execution main body executes the display popup data indicated by the trigger action information, where the popup data is used to indicate data included in an automatically popped up window, such as a picture, a dialog box, and a jump link, when a web page, software, or a mobile phone APP (Application) is opened.
According to the implementation mode, the popup window data are displayed through execution of the indication of the trigger action information, so that the pushed trigger action information is simpler and more clear, the user attention is more easily aroused, and the user behavior is guided.
In some alternatives, the pop-up window data includes: and the popup picture and/or the jump link corresponding to the popup.
In this implementation manner, the popup data includes a popup picture and/or a jump link corresponding to the popup. The popup picture and/or the skip link can be preset by the development end according to experience, a specific application scene, actual requirements and trigger rule information.
The pop-up picture can help to improve the aesthetic property of the displayed pop-up data.
The jump link is usually used in cooperation with the jump button to help guide the user to the page indicated by the jump link, so that the user can know more related content, and the user experience is improved.
In the embodiment of the application, the user operation behavior information is sent to the background server; receiving trigger action information pushed by a background server, wherein the trigger action information meets the trigger rule information pushing requirement by the background server based on user operation behavior information; and the action indicated by the trigger action information is executed, so that the instantaneity of push information response is effectively improved.
With further reference to fig. 6, a flow 600 of yet another embodiment of an originating side of an information push method is shown. The method can be executed by the terminal device 101, 102, 103 in fig. 1, and accordingly, the apparatus for pushing information can be disposed in the terminal device 101, 102, 103.
The method comprises the following steps:
In this embodiment, the execution body may receive trigger rule information and trigger action information set by the setting user through a preset rule setting page.
In this embodiment, after receiving the trigger rule information and the trigger action information, the execution main body may send the information to the background server in a wired or wireless manner, so that the background server pushes the trigger action information to the user side in response to matching of the user operation behavior information collected from the user side and the trigger rule information.
In addition, it should be noted that after receiving the trigger rule information and the trigger action information set by the user through the preset rule setting page, the execution main body may also store the trigger rule information and the trigger action information in a preset database. When the method is required to be used, the trigger rule and the trigger action information can be directly recalled from a preset database, and the trigger rule information and the trigger action information are sent to a background server.
The embodiment receives and sets the trigger rule information and the trigger action information set by a user through a preset rule setting page; the trigger rule information and the trigger action information are sent to the background server, so that the background server responds to the matching of the user operation behavior information collected from the user side and the trigger rule information, the trigger action information is pushed to the user side, the interaction with a set user is enhanced, and the flexibility of setting the trigger rule information is improved.
With further reference to fig. 7, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of an information pushing apparatus, which corresponds to the embodiment of the method shown in fig. 1, and which can be applied in various electronic devices.
As shown in fig. 7, the information pushing apparatus 700 of the present embodiment includes: a receiving module 701, a matching module 702, and a pushing module 703.
The receiving module 701 may be configured to receive trigger rule information and trigger action information pushed by the development end.
The matching module 702 may be configured to, in response to receiving the user operation behavior information collected by the user terminal, perform matching with the trigger rule information based on the user operation behavior information.
The pushing module 703 may be configured to, in response to the matching being successful, push the trigger action information to the user end.
In some optional manners of this embodiment, the matching module is further configured to, in response to receiving the user operation behavior information collected by the user side, perform first matching on the user operation behavior information and the first trigger rule; and responding to the successful matching of the first time, and performing second matching on the user operation behavior information meeting the first trigger rule and the second trigger rule.
In some optional manners of this embodiment, the matching module is further configured to, in response to receiving the user operation behavior information collected by the user end through the SDK provided in the application program, perform matching with the target user group based on the user operation behavior information.
In some optional manners of this embodiment, the second trigger rule further includes: the number of triggers.
In some optional manners of this embodiment, the target user group includes: the target user type and the terminal type corresponding to the target user.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 8 is a block diagram of an electronic device according to an information pushing method in an embodiment of the present application.
800 is a block diagram of an electronic device according to an information pushing method of an embodiment of the application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 8, the electronic apparatus includes: one or more processors 801, memory 802, and interfaces for connecting the various components, including a high speed interface and a low speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). Fig. 8 illustrates an example of a processor 801.
The memory 802 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by at least one processor, so that the at least one processor executes the information pushing method provided by the application. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to execute the information push method provided by the present application.
The memory 802 is a non-transitory computer readable storage medium, and can be used for storing non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the information pushing method in the embodiment of the present application (for example, the receiving module 701, the matching module 702, and the pushing module 703 shown in fig. 7). The processor 801 executes various functional applications of the server and data processing by running non-transitory software programs, instructions, and modules stored in the memory 802, that is, implements the information push method in the above-described method embodiment.
The memory 802 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created by use of the electronic device for information push, and the like. Further, the memory 802 may include high speed random access memory and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 802 may optionally include memory located remotely from the processor 801, which may be connected to an information-pushing electronic device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the information push method may further include: an input device 803 and an output device 804. The processor 801, the memory 802, the input device 803, and the output device 804 may be connected by a bus or other means, and are exemplified by a bus in fig. 8.
The input device 803 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic apparatus for quality monitoring of the live video stream, such as a touch screen, keypad, mouse, track pad, touch pad, pointer stick, one or more mouse buttons, track ball, joystick, or like input device. The output devices 804 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, the pertinence and the effectiveness of information pushing are effectively improved.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (22)
1. An information pushing method, the method comprising:
receiving trigger rule information and trigger action information sent by a development end, wherein the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information;
responding to the received user operation behavior information collected by the user side, and matching the user operation behavior information with the trigger rule information based on the user operation behavior information;
and responding to the successful matching, and pushing the trigger action information to the user side.
2. The method of claim 1, wherein the matching based on the user operation behavior information and trigger rule information in response to receiving the user operation behavior information collected by the user side comprises:
in response to receiving user operation behavior information collected by a user side, performing first matching on the user operation behavior information and the first trigger rule;
and responding to the successful matching of the first time, and performing second matching on the user operation behavior information meeting the first trigger rule and the second trigger rule.
3. The method of claim 1, wherein the matching based on the user operation behavior information and trigger rule information in response to receiving the user operation behavior information collected by the user side comprises:
and matching the user operation behavior information with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side through the SDK arranged in the application program.
4. The method of any of claims 1 or 2, wherein the second triggering rule further comprises: the number of triggers.
5. The method of claim 1, wherein the target user class group comprises: the target user type and the terminal type corresponding to the target user.
6. An information pushing method, the method comprising:
sending user operation behavior information to a background server;
receiving trigger action information pushed by a background server, wherein the trigger action information is pushed by the background server based on the information that the user operation behavior meets the trigger rule information;
and executing the action indicated by the trigger action information.
7. The method of claim 6, wherein the performing the action indicated by the trigger action information comprises:
and executing the display popup window data indicated by the trigger action information.
8. The method of claim 7, wherein the popup data comprises: and the popup picture and/or the jump link corresponding to the popup.
9. The method of claim 6, wherein the sending user operation behavior information to a backend server comprises: and sending the user operation behavior information acquired by the SDK arranged in the application program to the background server.
10. An information pushing method, the method comprising:
receiving trigger rule information and trigger action information set by a user through a preset rule setting page;
and sending the trigger rule information and the trigger action information to a background server so that the background server pushes the trigger action information to the user side in response to the matching of the user operation behavior information acquired from the user side and the trigger rule information.
11. An information push apparatus, the apparatus comprising:
the receiving module is configured to receive trigger rule information and trigger action information sent by a development end, wherein the trigger rule information comprises a first trigger rule and a second trigger rule, the first trigger rule comprises a target user class group, the second trigger rule comprises a trigger event and a trigger time, and the trigger action information is action information executed by a trigger user end when user operation behavior information meets the trigger rule information;
the matching module is configured to respond to the received user operation behavior information collected by the user terminal and match the user operation behavior information with the trigger rule information;
and the pushing module is configured to respond to the matching success and push the triggering action information to the user terminal.
12. The apparatus of claim 11, wherein the matching module is further configured to:
in response to receiving user operation behavior information collected by a user side, performing first matching on the user operation behavior information and the first trigger rule;
and responding to the successful matching of the first time, and performing second matching on the user operation behavior information meeting the first trigger rule and the second trigger rule.
13. The apparatus of claim 11, wherein the matching module is further configured to:
and matching the user operation behavior information with the trigger rule information based on the user operation behavior information in response to receiving the user operation behavior information acquired by the user side through the SDK arranged in the application program.
14. The apparatus of any of claims 11 or 12, wherein the second triggering rule further comprises: the number of triggers.
15. The apparatus of claim 11, wherein the target user class group comprises: the target user type and the terminal type corresponding to the target user.
16. An information push apparatus, the apparatus comprising:
a first sending module configured to send user operation behavior information to a background server;
the first receiving module is configured to receive trigger action information pushed by a background server, and the trigger action information is pushed by the background server based on the user operation behavior information meeting the trigger rule information;
a first execution module configured to execute the action indicated by the trigger action information.
17. The apparatus of claim 16, wherein the first execution module is further configured to:
and executing the display popup window data indicated by the trigger action information.
18. The apparatus of claim 17, wherein the popup data comprises: and the popup picture and/or the jump link corresponding to the popup.
19. The apparatus of claim 16, wherein the first transmitting module is further configured to: and sending the user operation behavior information acquired by the SDK arranged in the application program to the background server.
20. An information push apparatus, the apparatus comprising:
the second receiving module is configured to receive trigger rule information and trigger action information set by a setting user through a preset rule setting page;
the second sending module is configured to send the trigger rule information and the trigger action information to a background server so that the background server pushes the trigger action information to the user side in response to the matching of the user operation behavior information collected from the user side and the trigger rule information.
21. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory is stored with instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-5 or claims 6-9 or claim 10.
22. A non-transitory computer readable storage medium having computer instructions stored thereon for causing the computer to perform the method of any of claims 1-5 or claims 6-9 or claim 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010407523.3A CN111581518A (en) | 2020-05-14 | 2020-05-14 | Information pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010407523.3A CN111581518A (en) | 2020-05-14 | 2020-05-14 | Information pushing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111581518A true CN111581518A (en) | 2020-08-25 |
Family
ID=72113605
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010407523.3A Pending CN111581518A (en) | 2020-05-14 | 2020-05-14 | Information pushing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111581518A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112529640A (en) * | 2020-12-25 | 2021-03-19 | 深圳市顺易通信息科技有限公司 | Data pushing method, system and related equipment |
| CN114051052A (en) * | 2021-11-11 | 2022-02-15 | 北京淘友天下科技发展有限公司 | Behavior event configuration method, system, device, server and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102665177A (en) * | 2012-04-20 | 2012-09-12 | 北京慧创新盈科技有限公司 | Method, system and device for pushing application program information based on machine type matching information |
| CN106484858A (en) * | 2016-10-09 | 2017-03-08 | 腾讯科技（北京）有限公司 | Hot Contents method for pushing and device |
| CN107220852A (en) * | 2017-05-26 | 2017-09-29 | 北京小度信息科技有限公司 | Method, device and server for determining target recommended user |
| CN107911449A (en) * | 2017-11-15 | 2018-04-13 | 百度在线网络技术（北京）有限公司 | Method and apparatus for pushed information |
| CN108334516A (en) * | 2017-01-20 | 2018-07-27 | 百度在线网络技术（北京）有限公司 | Information-pushing method and device |
| CN108764994A (en) * | 2018-05-24 | 2018-11-06 | 深圳前海桔子信息技术有限公司 | A kind of user behavior guidance method, device, server and storage medium |
| CN109067990A (en) * | 2018-08-20 | 2018-12-21 | 麒麟合盛网络技术股份有限公司 | A kind of application service execution method and device |
| CN109242544A (en) * | 2018-08-20 | 2019-01-18 | 中国平安人寿保险股份有限公司 | Processing method, device, computer equipment and the storage medium of product information push |
| CN109582857A (en) * | 2018-10-15 | 2019-04-05 | 深圳壹账通智能科技有限公司 | Based on big data information-pushing method, device, computer equipment and storage medium |
| CN109672724A (en) * | 2018-11-01 | 2019-04-23 | 百度在线网络技术（北京）有限公司 | Information-pushing method, device and equipment |
| CN109726322A (en) * | 2019-01-28 | 2019-05-07 | 北京百度网讯科技有限公司 | Method and apparatus for pushed information |
| CN110471735A (en) * | 2019-08-21 | 2019-11-19 | 中国工商银行股份有限公司 | Operational view interface method for pushing and device |
| CN110569424A (en) * | 2018-05-18 | 2019-12-13 | 北京京东尚科信息技术有限公司 | Information recommendation method and device |
-
2020
- 2020-05-14 CN CN202010407523.3A patent/CN111581518A/en active Pending
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102665177A (en) * | 2012-04-20 | 2012-09-12 | 北京慧创新盈科技有限公司 | Method, system and device for pushing application program information based on machine type matching information |
| CN106484858A (en) * | 2016-10-09 | 2017-03-08 | 腾讯科技（北京）有限公司 | Hot Contents method for pushing and device |
| CN108334516A (en) * | 2017-01-20 | 2018-07-27 | 百度在线网络技术（北京）有限公司 | Information-pushing method and device |
| CN107220852A (en) * | 2017-05-26 | 2017-09-29 | 北京小度信息科技有限公司 | Method, device and server for determining target recommended user |
| CN107911449A (en) * | 2017-11-15 | 2018-04-13 | 百度在线网络技术（北京）有限公司 | Method and apparatus for pushed information |
| CN110569424A (en) * | 2018-05-18 | 2019-12-13 | 北京京东尚科信息技术有限公司 | Information recommendation method and device |
| CN108764994A (en) * | 2018-05-24 | 2018-11-06 | 深圳前海桔子信息技术有限公司 | A kind of user behavior guidance method, device, server and storage medium |
| CN109067990A (en) * | 2018-08-20 | 2018-12-21 | 麒麟合盛网络技术股份有限公司 | A kind of application service execution method and device |
| CN109242544A (en) * | 2018-08-20 | 2019-01-18 | 中国平安人寿保险股份有限公司 | Processing method, device, computer equipment and the storage medium of product information push |
| CN109582857A (en) * | 2018-10-15 | 2019-04-05 | 深圳壹账通智能科技有限公司 | Based on big data information-pushing method, device, computer equipment and storage medium |
| CN109672724A (en) * | 2018-11-01 | 2019-04-23 | 百度在线网络技术（北京）有限公司 | Information-pushing method, device and equipment |
| CN109726322A (en) * | 2019-01-28 | 2019-05-07 | 北京百度网讯科技有限公司 | Method and apparatus for pushed information |
| CN110471735A (en) * | 2019-08-21 | 2019-11-19 | 中国工商银行股份有限公司 | Operational view interface method for pushing and device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112529640A (en) * | 2020-12-25 | 2021-03-19 | 深圳市顺易通信息科技有限公司 | Data pushing method, system and related equipment |
| CN114051052A (en) * | 2021-11-11 | 2022-02-15 | 北京淘友天下科技发展有限公司 | Behavior event configuration method, system, device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108804299B (en) | Application program exception handling method and device | |
| WO2021082484A1 (en) | Awr report automatic acquisition method and apparatus, electronic device, and storage medium | |
| CN110532159B (en) | Data monitoring method, device, equipment and computer readable storage medium | |
| CN104866275B (en) | Method and device for acquiring image information | |
| CN110570217B (en) | Cheating detection method and device | |
| CN110544128A (en) | Channel information acquisition method and device, electronic equipment and storage medium | |
| CN111447507B (en) | Video production method and device, electronic equipment and storage medium | |
| CN112527748A (en) | Method, device, equipment and storage medium for analyzing user operation behaviors | |
| CN111913884A (en) | Distributed test method, device, equipment, system and readable storage medium | |
| CN110874307A (en) | Event buried point collecting and reporting method and device | |
| CN111581518A (en) | Information pushing method and device | |
| CN111582477B (en) | Training method and device for neural network model | |
| CN111881339A (en) | Resource information pushing and informing method and device, electronic equipment and storage medium | |
| CN109062799A (en) | Regression testing method, the apparatus and system of advertising scenarios | |
| CN111654495A (en) | Method, apparatus, device and storage medium for determining traffic generation source | |
| CN111460292A (en) | Model evaluation method, apparatus, device, and medium | |
| CN111178937A (en) | User reward method and device of application, electronic equipment and readable storage medium | |
| CN110477866B (en) | Method and device for detecting sleep quality, electronic equipment and storage medium | |
| CN112307386A (en) | Information monitoring method, system, electronic device and computer readable storage medium | |
| CN111813623A (en) | Page monitoring method and device, electronic equipment and storage medium | |
| CN111241396A (en) | Information pushing method and device, electronic equipment and storage medium | |
| CN113254315B (en) | Reporting method of embedded point information, embedded point method, device, medium and electronic equipment | |
| CN105262829B (en) | Geographical position monitoring method and system | |
| CN114035729A (en) | Electronic voting method and device and terminal equipment | |
| CN114661274A (en) | Method and device for generating intelligent contract |
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 |