CN112651772A

CN112651772A - Event touch method, device, equipment and storage medium

Info

Publication number: CN112651772A
Application number: CN202011502834.4A
Authority: CN
Inventors: 谌明; 王佳思
Original assignee: Zhejiang Tonghuashun Intelligent Technology Co Ltd
Current assignee: Zhejiang Tonghuashun Intelligent Technology Co Ltd
Priority date: 2020-12-18
Filing date: 2020-12-18
Publication date: 2021-04-13
Anticipated expiration: 2040-12-18
Also published as: CN112651772B

Abstract

The application relates to an event touch method, which is applied to a server and comprises the following steps: receiving user touch data, wherein the user touch data comprises a terminal identifier and/or a user account; acquiring a historical user account corresponding to the terminal identification and/or a historical terminal identification corresponding to the user account based on the user contact data; establishing a mapping table representing the association relationship between the terminal identification and the user account based on the historical user account corresponding to the terminal identification and/or the historical terminal identification corresponding to the user account; and determining a target terminal identifier associated with the target terminal and/or a target user account by using the mapping table so as to send a touch event aiming at the target terminal. Meanwhile, the application also provides an event touch device, equipment and a storage medium.

Description

Event touch method, device, equipment and storage medium

Technical Field

The present application relates to the field of event reach, and in particular, to an event reach method, apparatus, device, and storage medium.

Background

In the automatic marketing process, customer data can come from different systems, and due to the fact that account systems used among the systems are inconsistent, joint marketing cannot be conducted on different account numbers of the same customer, wherein the different account systems are aimed at by different systems. For example: in the securities industry, a user account rate of return event usually takes a fund account number as a user identifier, and a user behavior event usually takes a device unique identification number of a device where an application program is located as a user identifier. Because the fund account number and the unique equipment identification number belong to two different system systems, joint marketing of the same user of the two different systems cannot be realized. Therefore, it is urgently needed to provide a new automatic marketing scheme to find different accounts of the same user, so as to solve the problem that joint marketing for a multi-account system cannot be realized in the prior art.

Disclosure of Invention

In order to solve the above problems, the present invention provides an event reaching method, apparatus, device and storage medium, including the following aspects:

in a first aspect, an embodiment of the present application provides an event reaching method, where the method includes:

receiving user touch data, wherein the user touch data comprises a terminal identifier and/or a user account;

acquiring a historical user account corresponding to the terminal identification and/or a historical terminal identification corresponding to the user account based on the user contact data;

establishing a mapping table representing the association relationship between the terminal identification and the user account based on the historical user account corresponding to the terminal identification and/or the historical terminal identification corresponding to the user account;

and determining a target terminal identifier and/or a target user account associated with the target terminal by using the mapping table so as to send a touch event aiming at the target terminal.

In the above scheme, the method further comprises:

acquiring a fund account corresponding to the user account;

when the mapping table for representing the association relationship between the terminal identifier and the user account is established, the method further includes:

and establishing an association relation among the representation fund account, the terminal identification and the user account in the mapping table.

In the above scheme, the user contact data further includes a fund account;

determining whether the fund account number meets a preset fund condition;

and determining the terminal corresponding to the target fund account meeting the preset fund condition as the target terminal.

In the above scheme, the method further comprises:

detecting a first operation event in a cache library to acquire a first occurrence time of the first operation event;

first comparing the first occurrence time with a current watermark time to determine whether the first operational event satisfies a marking condition;

if the first comparison result represents that the first operation event meets the marking condition, marking the state of the first operation event;

and determining whether to send a touch event aiming at the target terminal according to the marking state of the first operation event.

In the above scheme, the user touch data further includes a first occurrence time of the first operation event; before detecting a first operation event in a cache library to obtain a first occurrence time of the first operation event, the method further includes:

comparing the first occurrence time contained in the user touch data with a current watermark time to determine whether the first operation event meets a caching condition;

and if the second comparison result represents that the first operation event meets the cache condition, saving the first operation event to the cache library so as to mark the state of the first operation event.

In the above scheme, a second operation event is stored in the cache library;

acquiring a second occurrence time of the second operation event;

generating a second watermark time of the second operation event based on a time difference between the second occurrence time and a preset delay time;

determining the second watermark time as a current watermark time.

In the foregoing solution, after the saving the first operation event in the cache library, the method further includes:

generating a first watermark time of the first operation event based on a time difference between the first generation time and a preset delay time;

comparing the first watermark time with the current watermark time;

and if the comparison result represents that the first watermark time is greater than the current watermark time, updating the first watermark time to be the current new watermark time.

In a second aspect, an embodiment of the present application provides an event reaching device, including:

the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving user touch data which comprises a terminal identifier and/or a user account;

an obtaining unit, configured to obtain, based on the user contact data, a historical user account corresponding to the terminal identifier and/or a historical terminal identifier corresponding to the user account;

the establishing unit is used for establishing a mapping table representing the association relation between the terminal identification and the user account based on the historical user account corresponding to the terminal identification and/or the historical terminal identification corresponding to the user account;

and the sending unit is used for determining a target terminal identifier and/or a target user account associated with the target terminal by using the mapping table so as to send a reaching event aiming at the target terminal.

In a third aspect, an embodiment of the present application provides an event reach apparatus, where the apparatus includes:

one or more processors;

a memory communicatively coupled to the one or more processors;

one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of the above event-triggered methods.

In a fourth aspect, a computer-readable storage medium stores a computer program, wherein the program is configured to implement the method of any one of the above event reach methods when executed by a processor.

According to the event touch method, the event touch device, the event touch equipment and the storage medium, all user accounts and all terminal identifications of the same user are obtained by receiving user touch data, and a mapping table representing the incidence relation between the user accounts and the terminal identifications is established; and sending a touch event to the target terminal based on the mapping table, so that different accounts of the same user can be found, the marketing dimensionality is improved, and the purpose of joint marketing of a multi-account system is realized.

Drawings

FIG. 1 is a schematic flow chart illustrating an implementation of an event reaching method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating a structure of an event trigger device according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of an event trigger device in the embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In some of the flows described in the specification and claims of the present application and in the above-described figures, a number of operations are included that occur in a particular order, but it should be clearly understood that the flows may include more or less operations, and that the operations may be performed sequentially or in parallel.

Fig. 1 is a schematic flow chart illustrating an implementation process of an event reaching method in an embodiment of the present invention, as shown in fig. 1, the method includes:

step 101, receiving user touch data, wherein the user touch data comprises a terminal identification and/or a user account;

in the Application, the method is mainly applied to a server installed with an Automated Marketing (APP) Application program, and the server can communicate with a plurality of terminals bound with the APP through the Automated Marketing APP. Here, the terminal includes, but is not limited to, a desktop computer, a notebook computer, a mobile phone, a tablet computer, and the like.

Here, the automated marketing APP refers to a piece of software of a cloud for executing, managing, and automatically completing marketing tasks and processes based on big data using computer technology for a large number of repeated human jobs in a conventional marketing campaign. When a user performs an operation in the automated marketing APP through a terminal, the server may receive user contact data sent by the terminal, and the user contact data includes a terminal identifier and/or a user account.

Here, the terminal identifier specifically refers to a unique Identity (ID) number of the terminal, and the user account specifically refers to a user name used when logging in the APP, for example, the user name may be a mobile phone number, a mailbox address, a micro signal, a QQ number, and the like.

In the application, the user touch data received by the server may specifically be behavior data triggered by the user on the terminal by gestures, a mouse, voice, touch and the like. The behavioral data include, but are not limited to: the method comprises the following steps of logging in the APP, registering the APP, browsing the APP, collecting the APP, commenting the APP, and conducting product transaction in the APP.

For example, the automatic marketing APP is an APP for the stock industry, and when a user logs in the automatic marketing APP by using a mobile phone a, the automatic marketing APP can detect the login operation of the user, so that login data of the user is acquired based on the login operation, and the login data is sent to a server of the automatic marketing APP; when the user conducts stock trading in the automatic marketing APP, the automatic marketing APP can also detect the trading operation of the user, so that the trading data of the user are collected based on the trading operation, and the trading data are sent to the server of the automatic marketing APP. When the server of the automated marketing APP receives the login data and/or the transaction data, the terminal identifier of the mobile phone a and/or the user account used when the mobile phone a logs in the automated marketing APP can be obtained from the login data and/or the transaction data.

Here, when receiving the user contact data, the server may specifically receive the user contact data of the network-wide terminal, rather than the contact data of one terminal. And then establishing a mapping table for representing the association relation between the terminal identification and the user account based on the user contact data.

102, acquiring a historical user account corresponding to the terminal identification and/or a historical terminal identification corresponding to the user account based on the user contact data;

here, when the server receives user contact data from a plurality of terminals in the whole network, since the terminal identifier and/or the user account of each terminal are different, the server may identify the user account and/or the terminal identifier of the same user from different sources based on the terminal identifier and/or the user account after receiving the user contact data, so as to obtain different user accounts and/or different terminal identifiers of the same user.

For example, a terminal corresponding to the same terminal identifier may use different user accounts to log in the automated marketing APP at different times, and the same user account may also log in the automated marketing APP on different terminals, so that after the server receives user contact data sent by the terminal, a plurality of different historical user accounts corresponding to the terminal identifier may be obtained from the cloud database based on the terminal identifier carried in the user contact data, and a plurality of different historical terminal identifiers corresponding to the user account may be obtained from the cloud database based on the user account carried in the user contact data, so as to associate the user accounts of the same user from different sources with \ or the terminal identifier in a subsequent process.

103, establishing a mapping table representing an association relation between a terminal identifier and a user account based on the historical user account corresponding to the terminal identifier and/or the historical terminal identifier corresponding to the user account;

here, when the server acquires a plurality of user accounts and/or a plurality of terminal identifications representing different sources of the same user, a mapping table representing the association relationship between different user accounts and different terminal identifications of the same user may be established, so that in a subsequent marketing process, a touch event may be sent to a plurality of terminals corresponding to the plurality of user accounts and/or the plurality of terminal identifications having an association relationship with the user based on the terminal identification and/or the user account of the user through the mapping table, so as to implement joint marketing of the plurality of terminals, thereby expanding a marketing range and improving marketing efficiency.

And 104, determining a target terminal identifier and/or a target user account associated with the target terminal by using the mapping table so as to send a reach event aiming at the target terminal.

Here, a plurality of different marketing strategies configured by background staff through the visual interface of the automated marketing APP may be stored in the server, and different marketing flow branches may be run through different marketing strategies to generate different reach events.

Specifically, background staff can set different attribute information according to different user groups, and the automatic marketing APP can form different marketing strategies based on the different attribute information.

Here, the different attribute information may refer to different ages, different genders, different incomes, different hobbies and interests, different investment amounts, and the like of the users. The type of event may be different for different user populations due to individual differences. Different reach events are generated based on different marketing strategies, so that the pushing precision of the events can be improved, the marketing efficiency can be improved, and the appropriate events can be pushed for users with different differences.

In the application, when the server sends a reach event to a target terminal, all target terminal identifications and/or all target user accounts associated with the target terminal can be determined by using the mapping table, and the reach event is sent to a plurality of target terminals and a plurality of target user accounts corresponding to all target terminal identifications through short messages, mails, system information push, labeling push and the like. Therefore, the marketing efficiency and the marketing range can be effectively improved.

Here, the system information pushing refers to event pushing through the system of the automated marketing APP. The user can receive the system push event through the message window of the automated marketing APP. For example, the system push event includes, but is not limited to, an advertising event for a marketed product, an information check event for a marketed product, a step node reminder event for a marketed product, a problem solving event for a marketed product, and the like.

Wherein, the advertising event of the marketing product is: the user purchases a product A on the automatic marketing APP once, and the automatic marketing APP can send other products of the same type as the product A to the user as touch events; the information check event of the marketing product is as follows: after the user successfully purchases the product A, the automatic marketing APP can acquire step node events of the user for the product A, and when the user is determined to be in a step of successful transaction according to the step node events, order information of the user is sent to the user as a touch event, so that the user can conveniently check the order information of the user. The problem solving event of the marketing product is that: the automatic marketing APP receives a problem consultation event of a user for a product A, and a response result corresponding to the problem consultation event can be sent to the user as a touch event so as to solve the problem that the user proposes the product A and improve the marketing efficiency of the product.

In the application, the tag pushing refers to pushing an event according to the tag attribute marked by the user in the automatic marketing APP.

Here, the tag attributes include, but are not limited to, high net worth users, potential attrition users, potential users, and the like.

Taking the securities industry as an example, a high-net-value user means: social groups with high total value of investable assets such as personal financial assets and investable property. Potentially attrition customers refer to: inactive accounts for more than 7 days; the potential users are: the total assets exceed 50 million RMB, and the investment experience exceeds two years. The automated marketing APP may push different marketing messages to users of different tag attributes based on the tag attributes of the users.

In the application, after the automatic marketing APP sends the reach event to the user, feedback data aiming at the reach event of the user can be collected; and optimizing the marketing strategy based on the feedback data. Therefore, the completeness of the marketing strategy and the satisfaction degree of the user on the marketing strategy can be improved.

By the automatic marketing method, different user accounts and different terminal identifications of the same user can be mapped based on user contact data from different sources, and a mapping table representing the mapping relation between the user accounts and the terminal identifications of the same user is generated; based on the mapping table, the reach event can be sent to the user in different data reach modes, so that the aim of joint marketing of a multi-account system can be fulfilled, and the reach precision of the reach event can be improved.

In the application, before the automatic marketing APP generates the touch event based on the configured marketing strategy, data conversion can be performed on the collected user touch data, so that the format of the collected user touch data is converted into a target format. And generating the format-converted user touch point data into a touch event based on the configured marketing strategy. Here, the target format may be specifically as shown in table one:

watch 1

The form is a binary serialization form, the form of the collected user contact data is converted into a target form, and then the contact event is generated by the format-converted user contact data based on the configured marketing strategy, so that the subsequent process treatment and the process unified management can be facilitated.

In the application, the user contact data received by the server may also carry a fund account corresponding to the user account, where the fund account is a current fund account used for performing product transaction in the automated marketing APP. For example, in the securities industry, the funding account may be the funding account that conducts a stock exchange. The server can determine whether the terminal where the user account is located meets the reaching condition or not based on the fund account. For example, the preset fund amount in the reach policy is 50 thousands, when the server acquires the current fund account corresponding to the user account, whether the fund amount corresponding to the current fund account reaches 50 thousands or not may be determined, if the determination result indicates that the fund amount corresponding to the current fund account reaches 50 thousands, it is determined that the terminal corresponding to the user account satisfies the reach condition, and a reach event may be sent to the terminal corresponding to the user account. Otherwise, if the judgment result indicates that the fund limit corresponding to the current fund account is less than 50 ten thousand, determining that the terminal corresponding to the user account does not meet the reaching condition, and not sending a reaching event to the terminal corresponding to the user account.

In the application, a plurality of different historical fund accounts can be associated with the user account. When the server obtains the user account based on the user contact data, a plurality of different historical fund accounts corresponding to the user account can be obtained from a cloud database based on the user account, and when a mapping table for representing the association relationship between the terminal identification and the user account is established, the association relationship among the represented fund account, the terminal identification and the user account is established in the mapping table so as to further expand the marketing dimensionality. When the server determines a target terminal meeting the touch condition based on the capital accounts, whether a plurality of capital accounts corresponding to the same user account meet a preset capital amount can be judged, if the judgment result represents that the capital amount of at least one of the capital accounts meets the preset capital amount, the terminal where the user account is located is determined to meet the touch condition, a touch event can be sent to the user account, and the touch event can also be sent to the terminal corresponding to the user account.

For example, in the automated marketing APP, the UserID is taken as the primary account ID of the user. DeviceID is the device ID when the user uses the automated marketing App. When the user uses the automatic marketing APP for the first time and does not register the automatic marketing APP, the user can use the APP in the identity of a tourist, at the moment, the automatic marketing APP can allocate a temporary ID to the user, the allocated temporary ID can be used as the user UserID of the current event, and the temporary ID is stored in a cache library in a lasting mode. When the user registers the automatic marketing APP and uses the mobile phone number to log in the automatic marketing APP, the automatic marketing APP can map the mobile phone number of the user and the equipment ID of the user, the mapping relation between the mobile phone number and the equipment ID is stored in a cache library in a lasting mode, and at the moment, the mobile phone number of the user can serve as the user UserID of the current event.

In the application, the account id is usually used as a fund account of the user, and after the user binds the fund account in the automatic marketing APP, the automatic marketing APP can also map the fund account with the mobile phone number and the device account of the user based on the fund account of the user, and persistently store the mapping relationship among the fund account, the mobile phone number of the user and the device account to the cache library.

Here, a case where a plurality of accountids (fund accounts) are bound may occur with one UserID. In the case that one UserID is bound to a plurality of accountids (fund accounts), the automatic marketing APP may also query the AccountID list and the AccountID to which the UserID is newly bound through the UserID. Therefore, unified management of different accounts of the user can be realized.

In the application, the automatic marketing APP saves the user account mapping relation under the condition of generating the user account mapping relation, so that when the user uses the automatic marketing APP next time, the user account mapping relation can be directly obtained from the buffer library, and the system response efficiency can be improved.

Here, the fund account includes, but is not limited to, a cash account opened by the user at a stock dealer or broker, a secured fund account, a credit card account of the user, a bank card account of the user, and the like.

In the application, the automatic marketing APP is realized based on a Flink streaming processing framework, and a related marketing process is driven based on a marketing event. Therefore, the user touch data received by the server further includes the first occurrence time of the first operation event. However, due to the problem of network delay, the time when the first operation event arrives at the server may be later than the first occurrence time of the first operation event, and if the server marks the state of the first operation event based on the arrival time of the first operation event, the problem of out-of-order arrival of events may be caused. For example, the occurrence time of the first operation event is 1: 00: 00, time of arrival at server is 1: 03: 00 min; the occurrence time of the second operation event is 1: 01: 00 cents, the time to server is 1: 02: and 00 minutes. Normally, the server should process the first operation event and then the second operation event, but due to network delay, the server may process the second operation event and then the first operation event, which may cause the problem of out-of-order events.

In order to solve the problem of event out-of-order arrival caused by network delay, a watermark mechanism is introduced in the application, the watermark is a delay timer embedded in a data stream, and a calculation program of a server can judge whether a certain time point arrives or not through watermark time, so that each operation event can be accurately processed.

Specifically, when the server acquires the first operation event and the first occurrence time of the first operation event from the user touch data, the first occurrence time of the first operation event may be compared with the current watermark time of the server to determine whether the first operation event satisfies the caching condition. And when the comparison result shows that the first generation time is greater than the current watermark time, determining that the first operation event meets the caching condition, and storing the first operation event into a caching library. Otherwise, if the comparison result indicates that the first generation time is less than the current watermark time, the first operation event is deleted if the first operation event is determined not to meet the caching condition.

Here, the user contact data includes a plurality of operation events, each of which is different, such as a plurality of operation events including, but not limited to, a login event, a browsing event, a transaction event, and the like. The server calculates the time difference between the occurrence time of each operation event in the user contact point data and the preset delay time to generate the watermark time of each operation event, and then, the maximum watermark time in the watermark time of each operation event is used as the current watermark time of the server. Here, the current watermark time is mainly used to determine whether a certain event needs to be discarded and whether a certain event needs to be processed.

For example, the preset delay time: 1 minute and 30 seconds; the occurrence time of event a is: 1: 00: 00, the first watermark time is: 12: 58: 30, of a nitrogen-containing gas; the occurrence time of event B is: 1: 01: 00, the second watermark time is: 12: 59: 30, of a nitrogen-containing gas; the occurrence time of event C is 1: 02: 00, the third watermark time is: 1: 00: 30. the third watermark time is taken as the current watermark time. And if the occurrence time of the event A is less than the current watermark time, discarding the event A, and if the occurrence time of the event B and the occurrence time of the event C are both greater than the current watermark time, storing the event B and the event C in a cache database.

The operation event here specifically means: the user operates any one of the generated operational behavior events in the automated marketing APP. For example, the first operation event may be a login event generated when the user logs in the automated marketing APP at the terminal, where the login event corresponds to an event occurrence time; the second operation event can be a browsing event generated when the user browses the product in the automatic marketing APP, and the browsing event corresponds to an event occurrence time; the third operation event may be a transaction event generated when the user conducts a product transaction in the automated marketing APP, and the transaction event corresponds to an event occurrence time.

Alternatively, when an operation event (hereinafter, referred to as a second operation event) is first generated in the user touch data, the server may obtain a second occurrence time of the second operation event, and calculate a time difference between the second occurrence time and a preset delay time to generate a second watermark time of the second operation event. Since the second watermark time is the first watermark time, the second watermark time may be determined as the current watermark time for subsequent operations.

In this application, after the server caches the first operation event in the cache library, a time difference between a first occurrence time of the first operation event and a preset delay time may also be calculated to generate a first watermark time of the first operation event. Then, comparing the first watermark time with the current watermark time, and if the comparison result indicates that the first watermark time is greater than the current watermark time, updating the first watermark time to be the current new watermark time; and if the first watermark time is less than the current watermark time, deleting the first watermark time and keeping the current watermark time unchanged.

After the current watermark time is determined, the server can also query the cached operation events in the cache library at preset time intervals and mark the operation events meeting the marking conditions. Taking the first operation event as an example, if the first operation event is queried, comparing the first occurrence time of the first operation event with the current watermark time to determine whether the first operation event satisfies the marking condition. And if the comparison result represents that the first generation time is less than or equal to the current watermark time, and the first operation event is determined to meet the marking condition, marking the state of the first operation event. Otherwise, if the comparison result represents that the first generation time is greater than the current watermark time, and the first operation event is determined not to meet the marking condition, the state of the first operation event is not marked. For example, if the first operation event is a login event, the state of the first operation event is marked as a login state; if the first operational event is a favorites event, the state of the first operational event is marked as a favorites state.

In the application, if the second occurrence time of the second operation event is detected to be greater than the current watermark time in the cache library, continuing to cache the second operation event; and when the second occurrence time of the second operation event meets the marking condition, marking the state of the second operation event, so that the problem that normal marketing cannot be performed due to the fact that the events arrive out of order can be avoided.

In this application, after the server marks the state of the first operation event, it may be further determined whether to send a reach event to a target terminal corresponding to the first operation event according to the marked state of the first operation event.

Specifically, when the touch strategy indicates that event touch is performed on the collection event, the touch event is sent to the target terminal when the mark state of the first operation event is determined to be the collection state; and if the touch strategy indicates that the event touch is carried out on the login event, sending the touch event to the target terminal when the mark state of the first operation event is determined to be the login event.

In the application, the automatic marketing APP associates a plurality of user accounts and/or a plurality of terminal identifications and/or a plurality of fund accounts of the same user from different sources by receiving user contact data, marks the state of each operation event through a watermark mechanism, and performs event contact according to the marked state of each operation event, so that the marketing range can be enlarged, the marketing efficiency is improved, and a higher marketing strategy in complexity can be supported.

An embodiment of the present application further provides a touch device, as shown in fig. 2, the touch device includes:

a receiving unit 201, configured to receive user touch data, where the user touch data includes a terminal identifier and/or a user account;

an obtaining unit 202, configured to obtain, based on the user contact data, a historical user account corresponding to the terminal identifier and/or a historical terminal identifier corresponding to the user account;

the establishing unit 203 is configured to establish a mapping table representing an association relationship between a terminal identifier and a user account based on the historical user account corresponding to the terminal identifier and/or the historical terminal identifier corresponding to the user account;

a sending unit 204, configured to determine, by using the mapping table, a target terminal identifier and/or a target user account associated with a target terminal, so as to send a reach event for the target terminal.

In a preferred embodiment, the obtaining unit 202 is further configured to obtain a fund account corresponding to the user account; the establishing unit 203 is further configured to establish an association relationship between the characteristic fund account, the terminal identifier and the user account in the mapping table.

In a preferred scheme, the user contact data further comprises a fund account number; further, the apparatus further comprises: a determining unit 205, configured to determine whether the fund account number meets a preset fund condition; and determining the terminal corresponding to the target fund account meeting the preset fund condition as the target terminal.

In a preferred embodiment, the apparatus further comprises: a query unit 206, a comparison unit 207 and a marking unit 208;

specifically, the query unit 206 is configured to detect a first operation event in the cache library, and trigger the obtaining unit 202 when the first operation event is detected; acquiring, by the acquiring unit 202, a first occurrence time of the first operation event; and when the first occurrence time of the first operation event is acquired, the comparison unit 207 is triggered.

The comparing unit 207 is configured to perform a first comparison between the first occurrence time and a current watermark time to determine whether the first operation event satisfies a marking condition; if the first comparison result represents that the first operation event meets the marking condition, the trigger marking unit 208 marks the state of the first operation event; then, the determination unit 205 is triggered by the marking unit 208 to determine whether to send a touch event for the target terminal according to the marking state of the first operation event.

In a preferred embodiment, the user touch data further includes a first occurrence time of the first operation event. The device further comprises a memory unit 209;

specifically, the comparing unit 207 is further configured to perform a second comparison between the first occurrence time included in the user touch point data and the current watermark time, so as to determine whether the first operation event meets a buffering condition; if the second comparison result indicates that the first operation event meets the cache condition, the storage unit 209 is triggered to store the first operation event into the cache library, so that the marking unit 208 marks the state of the first operation event.

In a preferred embodiment, the apparatus further comprises: a generating unit 210, configured to generate a first watermark time of the first operation event based on a time difference between the first occurrence time and a preset delay time after the storing unit 209 stores the first operation event in the cache library; then the trigger determining unit 205 determines the current watermark time according to the first watermark time.

In a preferred embodiment, the comparing unit 207 is further configured to compare the first watermark time with a current watermark time; if the comparison result indicates that the first watermark time is greater than the current watermark time, the trigger determining unit 205 updates the first watermark time to the current new watermark time.

In a preferred embodiment, the apparatus further comprises: an event preprocessing unit 211;

specifically, the event preprocessing unit 211 is configured to perform data conversion on the user touch data to convert the format of the received user touch data into a target format. Therefore, subsequent data processing flow and management are facilitated. After the format conversion is executed, the generating unit 210 is triggered, and the generating unit 203 generates a reach event for the format-converted user touch data based on the configured marketing strategy.

In a preferred embodiment, the apparatus further comprises: an optimization unit 212;

specifically, the receiving unit 201 is further configured to receive feedback data for the reach event; and after obtaining the feedback data, triggering the optimization unit 212; the marketing strategy is optimized by the optimization unit 212 based on the feedback data.

In a preferred embodiment, the storage unit 209 is further configured to store the mapping table. So that when the subsequent user accesses the automated marketing application again, the mapping relationship among the user account, the terminal identifier and the fund account is directly acquired from the storage unit 209, thereby improving the response efficiency of the system.

In this application, the device specifically can be the server of installing automatic marketing APP, and this server can communicate with a plurality of terminals that bind this APP through this APP, and for example, this terminal can be cell-phone, desktop computer, panel computer, TV etc..

In the present application, the apparatus further comprises a management platform 213;

the management platform 213 is typically used by back office workers who may configure visual marketing strategies via the management platform 213. And also for evaluating the value of the marketing strategy based on the feedback data received by the receiving unit 201 in order to optimize the marketing strategy.

In the present application, the device may also obtain the marketing task through the external database 214. Such as external database 214 including, but not limited to, third party databases and other data sources. And after the marketing task is acquired through the external database 214, the generation unit 210 is triggered, and the marketing task acquired from the external database 214 is generated into a marketing task event by the generation unit 210.

Here, it should be noted that: the descriptions of the embodiments of the apparatus are similar to the descriptions of the methods, and have the same advantages as the embodiments of the methods, and therefore are not repeated herein. For technical details that are not disclosed in the embodiments of the apparatus of the present invention, those skilled in the art should refer to the description of the embodiments of the method of the present invention to understand, and for brevity, will not be described again here.

An embodiment of the present application further provides an event touch device, including: one or more processors; a memory communicatively coupled to the one or more processors; one or more application programs; wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method described above.

In a specific example, the event trigger device according to the embodiment of the present application may be embodied as a structure as shown in fig. 3, and the event trigger device at least includes a processor 31, a storage medium 32, and at least one external communication interface 33; the processor 31, the storage medium 32, and the external communication interface 33 are all connected by a bus 34. The processor 31 may be a microprocessor, a central processing unit, a digital signal processor, or a programmable logic array, etc. having processing functions. The storage medium has stored therein computer executable code capable of performing the method of any of the above embodiments. In practical applications, each unit module of the event triggering device in fig. 2 can be implemented by the processor 31.

Here, it should be noted that: the above description of the event trigger device embodiment is similar to the above description of the method, and has the same beneficial effects as the method embodiment, and therefore, the description thereof is omitted. For technical details not disclosed in the embodiment of the event trigger apparatus of the present invention, those skilled in the art should refer to the description of the embodiment of the method of the present invention for understanding, and for the sake of brevity, will not be described again here.

Embodiments of the present application also provide a computer-readable storage medium, which stores a computer program, and when the program is executed by a processor, the computer program implements the method described above.

A computer-readable storage medium can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM). Additionally, the computer-readable storage medium may even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that all or part of the steps carried by the method for implementing the above embodiments can be implemented by hardware related to instructions of a program, which can be stored in a computer readable storage medium, and the program includes one or a combination of the steps of the method embodiments when the program is executed.

In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.

The embodiments described above are only a part of the embodiments of the present invention, and not all of them. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Claims

1. An event reach method applied to a server, the method comprising:

2. The method of claim 1, further comprising:

acquiring a fund account corresponding to the user account;

3. The method of claim 2, wherein the user contact data further includes a funding account number;

determining whether the fund account number meets a preset fund condition;

4. The method of claim 1, further comprising:

5. The method of claim 4, wherein the user contact data further comprises a first occurrence time of the first operational event; before detecting a first operation event in a cache library to obtain a first occurrence time of the first operation event, the method further includes:

6. The method of claim 4, wherein the cache library stores a second operational event;

acquiring a second occurrence time of the second operation event;

determining the second watermark time as a current watermark time.

7. The method of claim 5, wherein after saving the first operational event to the cache bank, further comprising:

comparing the first watermark time with the current watermark time;

8. An event reach apparatus, the apparatus comprising:

9. An event reach device, the device comprising:

one or more processors;

a memory communicatively coupled to the one or more processors;

one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-7.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.