Message pushing method and device, electronic equipment and storage medium

Abstract

The application discloses a message pushing method and device, electronic equipment and a storage medium. Specifically, the method comprises the following steps: obtaining a pushing template script and pushing configuration data; determining at least one pushing task information according to the pushing template script and the pushing configuration data; and performing message pushing on different target social group users according to different pushing task information. In the technical scheme of the embodiment of the application, different information is pushed to different users by obtaining the pushing template script and the pushing configuration data, different information is automatically pushed to different users at the same or different time, and the automation degree of social group operation and the efficiency of message pushing are greatly improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a message push method, apparatus, electronic device, and storage medium. Background Technology

[0002] In today's internet age, more and more manufacturers are realizing that building their own communities and coordinating and attracting users can increase user stickiness, better provide users with vertical and extended content push and services, and also widely receive user opinions, forming a virtuous cycle.

[0003] Pushing content to users within a community is a popular method for community building. There are many ways to push messages within a community. A common approach is for staff to edit messages in the backend, specifying the target audience (community and / or users) and the push time, and then sending the message to the target audience at the pre-set time. However, this becomes inefficient and inflexible when there are many messages to push, a complex community structure, and diverse user distribution, hindering the effective and flexible delivery of messages to the community. Summary of the Invention

[0004] This application provides a message push method, apparatus, electronic device, and storage medium to improve the efficiency and flexibility of social media message push.

[0005] According to one aspect of this application, a message push method is provided, the method comprising:

[0006] Retrieve push template script and push configuration data;

[0007] Based on the push template script and push configuration data, determine at least one push task information;

[0008] Based on different push task information, messages are pushed to different target community users.

[0009] According to another aspect of this application, a message push device is provided, comprising:

[0010] The template acquisition module is used to obtain push template scripts and push configuration data;

[0011] The task determination module is used to determine at least one push task information based on the push template script and push configuration data;

[0012] The message push module is used to push messages to different target community users based on different push task information.

[0013] According to another aspect of this application, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, which is then executed by the at least one processor to enable the at least one processor to perform the message push method described in any embodiment of this application.

[0017] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the message push method described in any embodiment of this application.

[0018] In the technical solution of this application embodiment, by acquiring push template scripts and push configuration data, different information is pushed to different users, automatically pushing different information to different users at the same or different times. This overcomes the shortcomings of existing technologies where different messages need to be pushed separately, greatly improving the automation level of community operations and the efficiency of message pushing. Furthermore, the same push template script can be used to send multiple different messages, offering better reusability. It is understandable that because it is in script form, it facilitates maintenance and iterative upgrades in subsequent community operations.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of a message push method provided according to Embodiment 1 of this application;

[0022] Figure 2 This is a schematic diagram of the script deployment method provided according to Embodiment 1 of this application;

[0023] Figure 3 This is a schematic diagram of a message push device according to Embodiment 2 of this application;

[0024] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the message push method of the embodiments of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Example 1

[0028] Figure 1 This application provides a flowchart of a message push method according to Embodiment 1. This embodiment is applicable to situations where targeted message pushes are made to different users. The method can be executed by a message push device, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1 As shown, the method includes:

[0029] S110. Obtain the push template script and push configuration data.

[0030] The push template script can be a script used for community operations. This script can carry multiple push messages, providing different messages to different users in the community. The push template script can be pre-stored in an operations script library for later use. The push configuration data can be flexible parameters set to run the push template script, such as the message push time, message push category, and whether there are global attribute restrictions. The push configuration data can be set by relevant technical personnel according to the specific needs of message push, and this embodiment of the application does not impose specific limitations on it.

[0031] In one alternative implementation, the push template script can be determined in the following way:

[0032] Obtain user tags for community users; determine target community users and their historical behavior data based on preset user tag filtering conditions; determine at least one push message for different target community users based on historical behavior data; determine the push template script based on each push message and different preset delay times.

[0033] In this context, community users can be any user within the community. Users can be individuals, organizations, or institutions. User tags can be attributes or categories used to distinguish each user, such as, but not limited to, user groups, gender, age, and place of origin, etc. These tags are generated after a user joins the community, and each user's tag is related to their own factual attributes.

[0034] User tag filtering conditions can be used to filter users based on tags. Correspondingly, these conditions can be pre-set by relevant personnel. It is understood that some parameters in the push template script can be pre-set or adjusted by relevant personnel, and multiple different scripts can be pre-set in the operation script library for different needs. Target community users can be the target users for the next message push; that is, the push template script will push messages to these target community users during the next community push. The historical behavior data of target community users can be records of their behavior over a past period. "Behavior" can refer to different operations performed within the community, and user behavior varies depending on the community's operation model, content, and user needs. The "period" can be pre-defined. It should be noted that historical behavior data can be recorded in various forms. Time-based records can record user actions in a time table; action-based records can record the time when a user performed that action in a behavior table. The format of historical behavior data recording is not limited in this embodiment. By using preset user tag filtering conditions, all users in the community can be filtered, thereby identifying target community users. Then, based on the target community users' information, the system retrieves the target community users' historical behavior data from the database storing this data. In a specific example, assuming the community operator sets community tasks for users, the historical behavior data could be whether the tasks were completed within the previous 24 hours.

[0035] By analyzing historical behavioral data and matching target community users with corresponding push notifications, it can be understood that pushing different messages based on different users' historical behaviors can help provide personalized services for community operations. Any of the relevant technologies can be used to analyze historical behavioral data, and this application embodiment does not limit this approach. Since the target community users for a single push are not unique, and the content pushed to different users may not be exactly the same, at least one message to be pushed must be determined based on historical behavioral data. That is, a single push template script can carry multiple messages to be pushed.

[0036] The preset delay time can be the delayed push time for each message to be pushed, and it varies for each different message. It's understood that since the push template script includes different messages to be pushed, the push time for each message will differ depending on the specific situation after the push template script is deployed. Therefore, it is necessary to preset the delay time for each message relative to the script deployment completion. The preset delay time can be set to a specific hour, minute, and second, for example, within a 24-hour period, indicating the exact hour, minute, and second after the script deployment. Therefore, the push template script is constructed by combining different messages to be pushed and their corresponding preset delay times. The specific construction method can employ any script generation method from related technologies; this application embodiment does not limit this approach.

[0037] In the above implementation, by analyzing the historical behavior data of the target community users, different messages to be pushed are determined for different users. Personalized message push based on the user's historical behavior data can better help users obtain usable messages. At the same time, by combining the preset delay time to generate push template scripts, the flexibility of message push is improved, which helps to enhance the flexibility of community operation.

[0038] Optionally, determining at least one message to be pushed to different target community users based on historical behavior data may include: matching pushable materials in a preset material library based on historical behavior data; and determining at least one message to be pushed to different target community users based on pushable materials corresponding to different historical behavior data.

[0039] The preset material library can be a database established in advance during community operation. This database stores various materials used to compose the push notifications, including but not limited to text, images, videos, and URL links. Historical behavior data represents what users in the target community have done or not done within a certain historical period. Based on this information, the preset material library is searched, and corresponding push notification materials are matched. For example, if a target community user did not complete their community assignment yesterday, the historical behavior data will show a record of this failure. Based on this record, corresponding materials are matched in the preset material library, such as text and images reminding the user to complete their assignment, or a URL link for the assignment. Different historical behavior data correspond to different push notification materials. Based on these different materials, different push notification messages are automatically generated for different target community users. Of course, any message generation method in related technologies can be used for automatic message generation; this embodiment is not limited here.

[0040] By matching historical behavioral data with a preset material library, different materials to be pushed can be determined and messages to be pushed can be generated. This can provide more accurate message pushes to different users, meet the targeting and flexibility of community operations, save resources that would otherwise be wasted by pushing the same message to all users, and help improve the efficiency of community operations.

[0041] In one optional implementation, the historical behavior data includes behavior tags and behavior time; the step of matching the material to be pushed in the preset material library based on the historical behavior data may include: determining the time association information of the material to be pushed based on the behavior time; and matching the material to be pushed in the preset material library based on the behavior tags and time association information.

[0042] Among these, behavioral tags can be data labels used to characterize specific behaviors; behavioral time can be used to record the moment a behavior occurs. Time-related information can be material information associated with the behavioral time. Continuing the previous example, if a user fails to complete a community assignment within the specified historical time limit, then the time-related information could be the expectation that the user will complete the community assignment within a certain period in the future. Based on this time-related information and the corresponding behavioral tags, the materials to be pushed are matched. It's conceivable that if the goal is to encourage the user to complete the assignment, the matching materials could include prompt text, prompt images, and links to the assignment.

[0043] In one optional implementation, determining the target community users and their historical behavior data based on preset user tag filtering conditions may include: filtering the target community users from the community users based on the user tag filtering conditions; and filtering historical behavior data from a preset behavior record database based on the target community users.

[0044] The preset user tag filtering criteria are used to select target users from all community users for message pushes. Therefore, these criteria can be based on specific user tags. For example, if the push message is only sent to female users, then the user tag "female user" could be used as the filtering criterion. Of course, the filtering criteria can be preset by technical personnel according to actual needs. The behavior record database is a database used to record user behavior data. Given the target community users, the historical behavior data of these users is retrieved and accessed.

[0045] S120. Determine at least one push task information based on the push template script and push configuration data.

[0046] The push configuration data can be parameters configured for the push template script, such as, but not limited to, information that needs to be recorded, including but not limited to, the configuration time (date and time) and the personnel configured. Using this information, different push tasks in the push template script are divided into different push tasks, so that the community can push messages according to these task information during operation.

[0047] In another optional implementation, the push configuration data includes global attribute differentiation conditions for target community users and push start time; the step of determining at least one push task information based on the push template script and push configuration data may include: determining different push times corresponding to each message to be pushed based on different preset delay times and push start times corresponding to each message to be pushed; and determining at least one push task information based on different push times, global attribute differentiation conditions, and each message to be pushed.

[0048] The global attribute differentiation criteria can be based on global attributes, which may include, but are not limited to, broad filtering criteria such as community activity period, community class (or group), and user gender. Optionally, the global attribute differentiation criteria can be preset global attributes as default values. These preset global attributes are global attributes that relevant personnel need to select in advance when configuring the script. For example, if class is selected as the global attribute, the corresponding default value could be all classes. If, before the script runs, the staff sets it to only send to classes A and B, then changing the preset global attributes will affect the script's message push.

[0049] The push start time can be the script's effective time set in the push configuration data when configuring the push template script. It's understood that after the script takes effect and starts timing, the push messages with different preset delay times carried in the script can be pushed at a precise time. Generally, the push start time is the sum of the push start time and the preset delay time. For example, if the push start time is set to 1:00 AM that day, and message A in the script has a preset delay time of 7.5 hours, while message B has a preset delay time of 12 hours, then message A will be pushed to the user corresponding to message A at 8:30 AM that day; similarly, message B will be pushed to the user corresponding to message B at 1:00 PM that day. It should be noted that the preset delay time can exceed 24 hours.

[0050] After determining the push time for each message to be pushed, target community users filtered according to global attribute differentiation conditions (of course, this also includes target community users filtered based on historical behavior data mentioned above) are formed into different push tasks for different users, so that messages can be pushed according to these push task information.

[0051] In the above implementation, the actual message push time is calculated by combining the push start time and the preset delay time. The time is divided into two parts, which makes it easier to push different messages at different times and improves the flexibility of message push.

[0052] S130. Based on different push task information, push messages to different target community users respectively.

[0053] Deploy the push template script obtained in the preceding steps to generate different push task information. Based on the target community users, corresponding messages to be pushed, and push time in each push task information, send community messages to users. Of course, when using the push template script determined in the preceding steps, you only need to set the push configuration data in advance and deploy it to the server. The script deployment process is as follows: Figure 2 As shown, the staff operating the community need to create a new operation script instance on the PC, select a push template script from the push template script library, set the start time of the script execution (i.e., the push start time), and set the global user attributes (i.e., the global attribute differentiation conditions mentioned above). After setting the script, save it and deploy it to the server.

[0054] In the technical solution of this application embodiment, by acquiring push template scripts and push configuration data, different information is pushed to different users, automatically pushing different information to different users at the same or different times. This overcomes the shortcomings of existing technologies where different messages need to be pushed separately, greatly improving the automation level of community operations and the efficiency of message pushing. Furthermore, the same push template script can be used to send multiple different messages, offering better reusability. It is understandable that because it is in script form, it facilitates maintenance and iterative upgrades in subsequent community operations.

[0055] Example 2

[0056] Figure 3 This is a schematic diagram of a message push device provided in Embodiment 2 of this application. Figure 3 As shown, the message push device 300 includes:

[0057] The template acquisition module 310 is used to acquire push template scripts and push configuration data;

[0058] The task determination module 320 is used to determine at least one push task information based on the push template script and push configuration data;

[0059] The message push module 330 is used to push messages to different target community users based on different push task information.

[0060] In the technical solution of this application embodiment, by acquiring push template scripts and push configuration data, different information is pushed to different users, automatically pushing different information to different users at the same or different times. This overcomes the shortcomings of existing technologies where different messages need to be pushed separately, greatly improving the automation level of community operations and the efficiency of message pushing. Furthermore, the same push template script can be used to send multiple different messages, offering better reusability. It is understandable that because it is in script form, it facilitates maintenance and iterative upgrades in subsequent community operations.

[0061] In one alternative embodiment, the device 300 may further include:

[0062] The user tag acquisition module is used to acquire user tags of community users;

[0063] The historical behavior determination module is used to determine the target community users and their historical behavior data based on preset user tag filtering conditions.

[0064] The push message determination module is used to determine at least one push message to different target community users based on historical behavior data.

[0065] The template script determination module is used to determine the push template script based on each message to be pushed and different preset delay times.

[0066] Optionally, the push message determination module may include:

[0067] The material matching unit is used to match the materials to be pushed from the preset material library based on historical behavior data;

[0068] The message determination unit is used to determine at least one message to be pushed to different target community users based on the pushable materials corresponding to different historical behavior data.

[0069] Optionally, the historical behavior data includes behavior tags and behavior time; the material matching unit includes:

[0070] The associated information determination sub-unit is used to determine the time-related information of the material to be pushed based on the behavior time;

[0071] The push material matching sub-unit is used to match the materials to be pushed in the preset material library based on behavior tags and time association information.

[0072] In one optional implementation, the historical behavior determination module may include:

[0073] The target user filtering unit is used to filter out target community users from community users based on user tag filtering criteria;

[0074] The behavior data filtering unit is used to filter historical behavior data from a preset behavior record database based on the target community users.

[0075] In one optional implementation, the push configuration data includes global attribute differentiation criteria for target community users and push start time; the task determination module 320 may include:

[0076] The push time determination unit is used to determine the different push times for each message to be pushed based on the different preset delay times and push start times corresponding to each message to be pushed.

[0077] The push task determination unit is used to determine at least one push task information based on different push times, global attribute distinction conditions, and each message to be pushed.

[0078] Optionally, the global attribute differentiation condition is that the global attribute is preset to a default value.

[0079] The message push device provided in this application embodiment can execute the message push method provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing each message push method.

[0080] Example 3

[0081] Figure 4 A schematic diagram of an electronic device 10, which can be used to implement embodiments of this application, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0082] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0083] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0084] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the message push method.

[0085] In some embodiments, the message push method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the message push method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the message push method by any other suitable means (e.g., by means of firmware).

[0086] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0087] Computer programs used to implement the methods of this application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0088] In the context of this application, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0089] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the 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 can be received in any form (including sound input, voice input, or tactile input).

[0090] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0091] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0092] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this application can be achieved, and this is not limited herein.

[0093] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A message push method, characterized in that, The method includes: Obtain the push template script and push configuration data; wherein, the push template script is pre-stored in the operation script library for later use; Based on the push template script and push configuration data, at least one push task information is determined; wherein, the push configuration data includes global attribute differentiation conditions for target community users and push start time; the global attribute differentiation conditions are differentiation conditions based on global attributes; the push start time is the script effective time set in the push configuration data when configuring the push template script; Based on different push task information, push messages to different target community users; The push template script is determined in the following way: Obtain user tags from community users; Based on preset user tag filtering conditions, determine the target community users and their historical behavior data; Based on the historical behavior data, at least one message to be pushed to different target community users is determined. The push template script is determined based on each message to be pushed and different preset delay times; The step of determining at least one message to be pushed to different target community users based on the historical behavior data includes: Based on the historical behavior data, match the materials to be pushed from the preset material library; Based on the pushable materials corresponding to different historical behavioral data, determine at least one pushable message for different target community users; The step of determining at least one push task information based on the push template script and push configuration data includes: Based on the different preset delay times corresponding to each message to be pushed and the push start time, the different push times corresponding to each message to be pushed are determined. Based on the different push times, the global attribute differentiation conditions, and each message to be pushed, at least one push task information is determined.

2. The method according to claim 1, characterized in that, The historical behavior data includes behavior tags and behavior time; the step of matching the content to be pushed in the preset content library based on the historical behavior data includes: Based on the time of the behavior, determine the time association information of the material to be pushed; Based on the behavior tags and the time association information, match the materials to be pushed in the preset material library.

3. The method according to claim 1, characterized in that, The step of determining the target community users and their historical behavior data based on preset user tag filtering conditions includes: Based on the user tag filtering criteria, the target community users are filtered out from the community users; Based on the target community users, the historical behavior data is filtered from a preset behavior record database.

4. The method according to claim 1, characterized in that, The distinguishing condition for global attributes is that the global attributes are preset to default values.

5. A message push device, characterized in that, include: The template acquisition module is used to acquire push template scripts and push configuration data; wherein, the push template scripts are pre-stored in the operation script library for later use. The task determination module is used to determine at least one push task information based on the push template script and push configuration data; wherein, the push configuration data includes global attribute differentiation conditions for target community users and push start time; the global attribute differentiation conditions are differentiation conditions based on global attributes; the push start time is the script effective time set in the push configuration data when configuring the push template script; The message push module is used to push messages to different target community users based on different push task information; The device further includes: The user tag acquisition module is used to acquire user tags of community users; The historical behavior determination module is used to determine the target community users and their historical behavior data based on preset user tag filtering conditions. The push message determination module is used to determine at least one push message to different target community users based on the historical behavior data. The template script determination module is used to determine the push template script based on each message to be pushed and different preset delay times; The push message determination module includes: The material matching unit is used to match the materials to be pushed in the preset material library based on the historical behavior data; The message determination unit is used to determine at least one message to be pushed to different target community users based on the pushable material corresponding to different historical behavior data. The task determination module includes: The push time determination unit is used to determine different push times for each message to be pushed based on different preset delay times and the push start time. The push task determination unit is used to determine at least one push task information based on the different push times, the global attribute differentiation conditions, and each message to be pushed.

6. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the message push method according to any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the message push method according to any one of claims 1-4.

Images