An information pushing method, device and electronic equipment

Abstract

The specification provides an information pushing method, device and electronic equipment, the method obtains information pushing instruction including content identifier of to-be-pushed content and customer group identifier of target audience; according to the customer group identifier, a set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform is determined; a target component corresponding to a target platform identifier associated with the target user identifier is called, and the content identifier of the to-be-pushed content is taken as a calling parameter; when the target component is called, the target platform is connected and the target platform is triggered to send content corresponding to the content identifier to the target user. The information pushing method is simple, convenient, and efficient. The method breaks through the limitation of different user systems of each channel, uses a unified customer group for operation and promotion, reduces the operation cost, and improves the user conversion rate. Through the customer group identifier, the target user can be determined, and personalized content operation can be performed on each customer group, thereby improving the user activity, stickiness and retention rate.

Description

Technical Field

[0001] This application relates to the field of computer technology and can be used in the financial field, and in particular to an information push method, device and electronic device. Background Technology

[0002] With the development of the internet and new media social platforms, platforms for information dissemination are constantly emerging. A merchant can register on multiple platforms as a merchant customer, and a platform can serve as a merchant customer for another platform. For example, in addition to its own portal website and mobile banking, XX Bank has also applied for accounts on third-party platforms (such as a certain social media platform and Douyin) and registered as a merchant.

[0003] Currently, different platforms acquire different user data and use different customer segmentation algorithms. Merchants typically need to operate each platform separately when pushing information to users on different platforms. For example, when XX Bank places marketing advertisements on its own marketing and promotion platform, bank employees need to operate the bank's marketing and promotion platform. However, when XX Bank needs to place marketing advertisements on a third-party platform, bank employees need to operate the third-party platform separately.

[0004] Therefore, when platform A acts as a merchant customer on platform B, if platform A needs to push information to users, it needs to perform repeated operations on both platform A and platform B, making the information push process cumbersome and labor-intensive. Summary of the Invention

[0005] This manual provides an information push method, device, and electronic device to solve the problem that when merchants are on multiple platforms, pushing information to users requires separate operations on each platform, which is cumbersome and labor-intensive.

[0006] To address the aforementioned technical problems, this specification provides a first aspect of an information push method, comprising: acquiring an information push instruction, the information push instruction including a content identifier of the content to be pushed and a customer group identifier of the target audience; determining, based on the customer group identifier, a set of target user identifiers corresponding to the customer group identifier in a set of user identifiers of each platform; and sending the content to be pushed to each target user in the following manner: invoking a target component corresponding to a target platform identifier associated with the target user identifier, and using the content identifier of the content to be pushed as a calling parameter; when the target component is invoked, connecting to the target platform and triggering the target platform to send the content corresponding to the content identifier to the target user, wherein the content corresponding to the content identifier is pre-stored in the target platform.

[0007] In some embodiments, before determining the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform based on the customer group identifier, the method further includes: obtaining user identifiers from multiple platforms and establishing a correspondence between the user identifiers of the same user on different platforms.

[0008] In some embodiments, obtaining user identifiers from multiple platforms and establishing a correspondence between user identifiers of the same user on different platforms includes: when a user logs into a third-party platform to use a service embedded in the target platform, invoking a first interaction component that interacts with the third-party platform to obtain the user's first user identifier on the third-party platform and account interaction information entered when using the service embedded in the target platform, wherein the account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform; obtaining the account interaction information entered when using the service of the target platform on the third-party platform, and determining the user's second user identifier on the target platform based on the account interaction information; storing the first user identifier and the second user identifier in association, wherein the first user identifier is associated with the identifier of the third-party platform, and the second user identifier is associated with the identifier of the target platform.

[0009] In some embodiments, user identifiers are obtained from multiple platforms, and a correspondence is established between user identifiers of the same user on different platforms. This includes: when a user logs into a target platform and initiates authorization on a third-party platform, obtaining the user's second user identifier on the target platform and the user's first user identifier on the third-party platform entered when initiating authorization through a second interactive component that interacts with the target platform; storing the first user identifier and the second user identifier together, wherein the first user identifier is associated with the identifier of the third-party platform, and the second user identifier is associated with the identifier of the target platform.

[0010] In some embodiments, the method further includes: pre-storing customer group identifiers corresponding to each user identifier, wherein the customer group identifiers are determined by the platform corresponding to the user identifier based on the platform's built-in algorithm.

[0011] In some embodiments, the information push instruction may further include a target push strategy, which is selected by the user from a plurality of push strategies.

[0012] In some embodiments, the target push strategy is selected from at least two of the following: a first strategy, a second strategy, and a third strategy; wherein the first strategy represents pushing information to all accounts of the same user on different platforms, the second strategy represents pushing information to accounts of the same user on predetermined platforms among their accounts on different platforms, and the third strategy represents pushing information to accounts of the same user on their most preferred platform among their accounts on different platforms.

[0013] In some embodiments, where the user can select a third strategy, the method further includes: periodically acquiring user access data statistically collected from each platform; determining the user's preference characteristics for each platform based on the user access data statistically collected from each platform; and determining the user's most preferred platform based on the user's preference characteristics for each platform.

[0014] In some embodiments, the method further includes: obtaining user identifiers, user data, and user identifiers from multiple platforms; mapping user data from each platform to user data of a target platform; and classifying the user data using a classification algorithm of the target platform to determine the customer group identifier corresponding to each user identifier.

[0015] In some embodiments, when determining the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform based on the customer group identifier: if the first user identifier of the first platform has a corresponding stored second user identifier of the second platform, then one of the first user identifier and the second user identifier is determined as the target user identifier.

[0016] A second aspect of this specification provides an information push device, comprising: a first acquisition unit, configured to acquire an information push instruction, the information push instruction including a content identifier of the content to be pushed and a customer group identifier of the target audience; a first determination unit, configured to determine, based on the customer group identifier, a set of target user identifiers corresponding to the customer group identifier in a set of user identifiers of each platform; and a calling unit, configured to send the content to be pushed to each target user in the following manner: calling a target component corresponding to a target platform identifier associated with the target user identifier, and using the content identifier of the content to be pushed as a calling parameter; when the target component is called, it connects to the target platform and triggers the target platform to send the content corresponding to the content identifier to the target user, the content corresponding to the content identifier being pre-stored in the target platform.

[0017] In some embodiments, the apparatus further includes: an establishment unit, configured to obtain user identifiers from multiple platforms and establish a correspondence between user identifiers of the same user on different platforms.

[0018] In some embodiments, the establishment unit includes: a calling subunit, configured to, when a user logs into a third-party platform and uses a service embedded in the target platform, call a first interaction component that interacts with the third-party platform to obtain a first user identifier of the user on the third-party platform and account interaction information entered when using the service embedded in the target platform, wherein the account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform; a first obtaining subunit, configured to obtain the account interaction information entered when using the service of the target platform on the third-party platform, and determine a second user identifier of the user on the target platform based on the account interaction information; and a first storage unit, configured to store the first user identifier and the second user identifier in association, wherein the first user identifier is associated with the identifier of the third-party platform, and the second user identifier is associated with the identifier of the target platform.

[0019] In some embodiments, the establishment unit includes: a second acquisition subunit, configured to acquire, through a second interaction component that interacts with the target platform, a second user identifier of the user on the target platform and a first user identifier of the user on the third-party platform entered when initiating authorization, when the user logs into the target platform and initiates authorization on the third-party platform; and a second storage unit, configured to store the first user identifier and the second user identifier together, wherein the first user identifier is associated with the identifier of the third-party platform and the second user identifier is associated with the identifier of the target platform.

[0020] In some embodiments, the information push instruction may further include a target push strategy, which is selected by the user from a plurality of push strategies.

[0021] In some embodiments, the target push strategy is selected from at least two of the following: a first strategy, a second strategy, and a third strategy; wherein the first strategy represents pushing information to all accounts of the same user on different platforms, the second strategy represents pushing information to accounts of the same user on predetermined platforms among their accounts on different platforms, and the third strategy represents pushing information to accounts of the same user on their most preferred platform among their accounts on different platforms.

[0022] In some embodiments, where the user can select a third strategy, the apparatus further includes: a second acquisition unit, configured to periodically acquire user access data statistically collected by each platform; a second determination unit, configured to determine the user's preference characteristics for each platform based on the user access data statistically collected by each platform; and a third determination unit, configured to determine the user's most preferred platform based on the user's preference characteristics for each platform.

[0023] In some embodiments, the apparatus further includes: a third acquisition unit, configured to acquire user identifiers, user data, and user identifiers from multiple platforms; a mapping unit, configured to map user data from each platform to user data of a target platform; and a classification unit, configured to classify the user data using a classification algorithm of the target platform, thereby determining the customer group identifier corresponding to each user identifier.

[0024] The information push method, apparatus, and electronic device provided in this manual acquire an information push instruction containing a content identifier of the content to be pushed and a customer group identifier of the target audience. Then, based on the customer group identifier, the target user identifier is determined. The target component corresponding to the target platform identifier associated with the target user identifier is invoked. When the target component is invoked, it connects to the target platform and triggers the target platform to send the content corresponding to the content identifier to the target user. With this solution, when a user needs to push content, they only need to pre-store the content to be pushed on the target platform, and then create an information push task to generate an information push instruction. This enables the push of content to target users on multiple platforms, making the process simple, convenient, and highly efficient. This solution overcomes the limitations of different user systems across various channels, using a unified customer group for operation and promotion, reducing operational costs while improving user conversion rates. Since customer groups are usually segmented based on user needs and usage habits, this solution allows for personalized content operation for each customer group by identifying target users through customer group identifiers, improving user activity, stickiness, and retention rates. Attached Figure Description

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

[0026] Figure 1 This diagram illustrates the interaction methods between information exchange tools and various platforms.

[0027] Figure 2 A schematic diagram of an information push method provided in the embodiments of this specification;

[0028] Figure 3 A user interface diagram for creating an information push task;

[0029] Figure 4 A schematic diagram of a method for obtaining user identifiers from multiple platforms and establishing a correspondence between user identifiers of the same user on different platforms to form a preset database;

[0030] Figure 5A schematic diagram illustrating another method for obtaining user identifiers from multiple platforms and establishing corresponding relationships between the user identifiers of the same user on different platforms to form a pre-defined database;

[0031] Figure 6 This is a schematic diagram of an information push device provided in this specification;

[0032] Figure 7 A schematic diagram of the electronic device provided in this specification is shown. Detailed Implementation

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

[0034] Typically, each social media platform is independently developed and operated, and there is no sharing of user information or operations between different social media platforms. Therefore, if a merchant on platform A joins platform B and needs to push information to users, the operation needs to be repeated on both platform A and platform B.

[0035] To address this technical problem, this specification provides an information push method that allows information to be pushed to users on multiple platforms with only a single operation. This method can be used for, for example... Figure 1 The information push tool shown allows users to push information to two or more platforms by operating the tool. The information push tool interacts with these platforms through interactive components.

[0036] like Figure 2 As shown, the information push method provided in this specification includes the following S10 to S30.

[0037] S10: Obtain information push instruction, wherein the information push instruction includes the content identifier of the content to be pushed and the customer group identifier of the target audience.

[0038] In some embodiments, such as Figure 3 As shown, users can create push notification tasks using the push notification tool and input the content identifier of the content to be pushed and the target audience's demographic identifier. After the user confirms the completion of the push notification task, the push notification tool automatically generates a push notification instruction based on the content identifier of the content to be pushed and the target audience's demographic identifier.

[0039] In other embodiments, the information push tool may also accept information push instructions sent by other program modules or other devices.

[0040] Customer segment identifiers are tags set by the platform to identify users, indicating the type of user the corresponding user data belongs to. These types are usually set according to marketing and promotional purposes. For example, customer segment identifiers may include age-based groups such as those born in the 1970s, 1980s and 1990s, and 2000s, or groups such as toddlers, students, office workers, and retired seniors.

[0041] The customer group identifiers corresponding to each user identifier are pre-stored in a preset database. In some embodiments, these customer group identifiers may be determined by the platform corresponding to the user identifier according to the platform's built-in algorithm. That is, after collecting user data, each platform will determine the customer group identifier corresponding to the user identifier according to its built-in algorithm. In other words, while obtaining user identifiers from multiple platforms, the customer group identifiers determined by the platform for the user identifier are also obtained at the same time.

[0042] Different platforms may have different built-in algorithms, and the transaction data of the same user may also be different on different platforms. Therefore, the customer group identifiers identified by different platforms for the same user are often different.

[0043] Furthermore, the push notification includes a target push strategy, which indicates how to push information to the same user's accounts on different platforms. The target push strategy is selected by the user from multiple push strategies, allowing for flexible selection based on the content to be pushed.

[0044] For example, a targeted push strategy can be selected from at least two of a first strategy, a second strategy, and a third strategy. The first strategy involves pushing information to all accounts of the same user across different platforms. The second strategy involves pushing information to accounts on a predetermined platform within each of the same user's accounts across different platforms. Here, the "predetermined platform" can be a pre-set mainstream social media platform. The third strategy involves pushing information to accounts on the user's most preferred platform across different platforms. Here, the "most preferred platform" can be pre-set by the user or determined based on user access frequency, access duration, and transaction volume statistics from each platform.

[0045] When users can select a third strategy, the push notification tool can periodically obtain user access data from various platforms, including but not limited to access functions, access channels, access times, and access devices. Based on the user access data from each platform, it can determine the user's preference characteristics for each platform; and based on the user's preference characteristics for each platform, it can determine the user's most preferred platform. In other words, the push notification tool can periodically update the user's most preferred platform, thus consistently pushing information to the user on the user's most preferred platform.

[0046] Push notification tools can store user identifiers along with their preferred platforms. In some cases, they can also determine a user's preferred platform based on the type of content, thus storing the user identifier, the type of content to be pushed, and the user's preferred platform. For example, for sports information, users prefer to browse on platform A; for entertainment information, users prefer to browse on platform B.

[0047] In other embodiments, the customer group identifier may be determined by the following S51 to S53.

[0048] S51: Obtain user identifiers and user data from multiple platforms.

[0049] S52: Map user data from various platforms to user data on the target platform.

[0050] S53: Use the target platform's classification algorithm to classify user data, thereby determining the customer group identifier corresponding to each user identifier.

[0051] User data collected from different platforms is different. In order to unify the user data obtained from different platforms so as to use a classification algorithm to determine the customer group identifier corresponding to each user identifier, the user data of each platform can be mapped to the user data of the target platform, and then the classification algorithm of the target platform can be used to classify the user data. Through the above steps S51 to S53, a unique customer group identifier can be determined for the same user.

[0052] The “target platform” in S51 to S53 can be one of the various platforms that need to push information.

[0053] S20: Based on the customer group identifier, determine the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform.

[0054] The information push tool can connect to a preset database, which stores a set of user identifiers from multiple platforms. Each user identifier is associated with at least one customer group identifier, thus allowing the determination of a set of multiple target user identifiers based on the customer group identifiers.

[0055] In some embodiments, the user identifier sets of each platform are stored in a preset database. For example, assuming there are three platforms A, B, and C, and platform A has registered as a merchant customer on platforms B and C, then the user identifiers of all customers of platforms A, B, and C, as well as at least one associated customer group identifier, can be stored in the preset database.

[0056] In other embodiments, the preset database may store user data groups, which include multiple user identifiers on different platforms that have corresponding relationships. Typically, the multiple user identifiers in a user data group are the same user's user identifiers on different platforms.

[0057] Prior to S20, user identifiers could be obtained from multiple platforms, and a correspondence could be established between the user identifiers of the same user on different platforms.

[0058] Specifically, in some cases, such as Figure 4 As shown, user identifiers can be obtained from multiple platforms through steps S41 to S43, and a corresponding relationship can be established between the user identifiers of the same user on different platforms, thereby forming a preset database.

[0059] S41: When a user logs into a third-party platform to use the service embedded in the target platform, the first interaction component that interacts with the third-party platform is invoked to obtain the user's first user identifier on the third-party platform and the account interaction information entered when using the service embedded in the target platform. The account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform.

[0060] The information push tool may include a first interactive component, which is used to interact with a third party and obtain data from the third party platform.

[0061] Specifically, when a user logs into a third-party platform and uses the services embedded in the target platform, the first interaction component is invoked. This first interaction component can first allow the user to confirm whether to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform. If the user confirms the authorization, the first interaction component displays an account interaction information filling interface on the third-party platform. This interface is used to fill in the user's account and password on the target platform, which is the account interaction information.

[0062] "Services embedded in the target platform" refers to the services set up on the third-party platform after the target platform, as a merchant customer, has joined the third-party platform.

[0063] S42: Determine the user's second user identifier on the target platform based on the account interaction information.

[0064] The information exchange platform determines a user's secondary user identifier on the target platform based on account interaction information. Specifically, the database can store the user's identifier, account, and password on the target platform. The information exchange platform can determine the user's secondary user identifier on the target platform from the database based on the account and password. Furthermore, the information exchange platform can also send a query request to the target platform's server to retrieve the secondary user identifier corresponding to the account and password.

[0065] S43: Store the first user identifier and the second user identifier in correspondence, wherein the first user identifier is associated with the identifier of the third-party platform, and the second user identifier is associated with the identifier of the target platform.

[0066] Through S43, a user data group is formed, as shown in "First User Identifier (Third-Party Platform Identifier), Second User Identifier (Target Platform Identifier)".

[0067] It is important to note that S41 to S43 above only provide an example of storing user identifiers from a third-party platform and the target platform to form user data groups. In reality, S41 to S43 can also be used to store user identifiers from multiple platforms in pairs to form user data groups. In this case, these user data can be combined into one. For example, if user identifiers from platform A and B are stored in pairs (AB), user identifiers from platform B and C are stored in pairs (BC), and user identifiers from platform C and A are stored in pairs (CA), then the user identifiers from platforms A, B, and C can be stored as a single record (ABC).

[0068] In some cases, if user identifiers from multiple third-party platforms are stored separately and corresponding to user identifiers from the target platform to form user data groups, these user data can be combined into one. For example, if third-party platforms X, Y, and Z are stored separately and corresponding to user identifiers from target platform A (XA, YA, ZA), then the user data from third-party platforms X, Y, and Z can be stored as a single record (AXYZ).

[0069] Specifically, S41 to S43 can be as follows: The user logs into a third-party platform and applies for an account on the third-party platform using their bank account, and interacts with banking business functions within the third-party platform through this account; the information push tool obtains the user's identity ID on the third-party platform, denoted as opencust_id, and the user's account interaction information on the third-party platform through the first interaction component, and verifies the user's identity ID within the bank, denoted as bankcust_id, based on the interaction information; the identity IDs "opencust_id" and "bankcust_id" are stored in a preset database, establishing a mapping relationship between the user's identity ID within the banking application and the user's identity ID within the third-party platform.

[0070] In other cases, such as Figure 5 As shown, user identifiers can be obtained from multiple platforms through S44 and S45, and a corresponding relationship can be established between the user identifiers of the same user on different platforms, thereby forming a preset database.

[0071] S44: When a user logs into the target platform and initiates authorization on a third-party platform, the second user identifier of the user on the target platform and the first user identifier assigned to the user by the third-party platform are obtained through the second interactive component that interacts with the target platform.

[0072] Users can initiate authorization from the target platform to a third-party platform, authorizing the use of the target platform's login information to log in. During authorization, users do not need to enter any login information or user identifier; they only need to select the third-party platform to authorize. After authorization, the third-party platform will log in using the user's account and password from the target platform and automatically assign a first user identifier to the user, which it then returns to the target platform. Thus, the second interactive component interacting with the target platform can obtain the user's second user identifier from the target platform and the first user identifier assigned to the user by the third-party platform.

[0073] S45: The first user identifier and the second user identifier are associated and stored together, wherein the first user identifier is associated with the identifier of the third-party platform and the second user identifier is associated with the identifier of the target platform.

[0074] Please refer to S43 for understanding S45; it will not be elaborated upon further.

[0075] Specifically, S44 to S45 can be as follows: When a user logs into the bank application platform, the user's identity ID is obtained and recorded as bankcust_id; when the user uses the embedded function of the bank application, the function guides the user to use the SDK provided by the third-party platform to initiate authorization on the third-party platform; when the user agrees to the authorization, the user's identity ID on the third-party platform is obtained and recorded as opencust_id; the identity ID "bankcust_id" and the identity ID "opencust_id" are stored in a preset database to establish a mapping relationship between the user's identity ID in the bank application and the user's identity ID on the third-party platform.

[0076] In addition to S41 to S45 mentioned above, the information interaction tool can periodically obtain user identifier lists from each platform and add user identifiers that are not present in the preset database to the preset database. In other words, S41 to S45 specify that when a user initiates authorization, the user identifiers of the two platforms are stored in the preset database accordingly. For user identifiers on platforms where the user has not initiated authorization, they can be added in batches periodically, ensuring that the preset database contains user identifiers from each platform. This facilitates more accurate information delivery to users based on subsequent push strategies.

[0077] S30: Send the content to be pushed to each target user in the following way: call the target component corresponding to the target platform identifier associated with the target user identifier, and use the content identifier of the content to be pushed as the call parameter; when the target component is called, it connects to the target platform and triggers the target platform to send the content corresponding to the content identifier to the target user, and the content corresponding to the content identifier is pre-stored in the target platform.

[0078] In S30, "target users" refers to user accounts on various social platforms that have customer group identifiers in the information push instructions.

[0079] In some embodiments, a preset database stores customer group identifiers corresponding to user identifiers. In this case, the information push tool can determine the identifier of the target user based on the data stored in the preset database. When invoking the target component, the target user's identifier can also be used as a calling parameter. The target component is used to instruct the target platform to send content corresponding to the content identifier to the target user identifier.

[0080] With user identifiers, platform identifiers, customer group identifiers, and preferred push strategies stored in a pre-defined database, the push notification tool can filter target user identifiers based on push notification instructions and create a list of target user identifiers categorized by platform identifier. The push notification tool then calls the target component corresponding to each platform identifier one by one. When calling a target component corresponding to a platform identifier, it pushes information in batches to the target user identifiers in the list corresponding to that platform identifier.

[0081] If a first user identifier on the first platform has a corresponding second user identifier stored on the second platform, one of the first user identifier and the second user identifier can be determined as the target user identifier according to the rules of the push strategy. The first user identifier and the second user identifier with a corresponding relationship are usually from the same user. That is, for a single user, information is pushed to the user through only one platform.

[0082] In some other embodiments, the preset database does not store the customer group identifier corresponding to the user identifier. In this case, the information push tool can call the target component corresponding to each platform and use the content identifier to be pushed and the customer group identifier of the target audience as calling parameters. The target component triggers each platform to first determine the target user based on the customer group identifier, and then send the content corresponding to the content identifier to the target user.

[0083] The aforementioned "content corresponding to the content identifier" can be pre-stored on various platforms. The identifiers of the content stored on each platform may be named according to the platform's rules, and therefore differ from the content identifier in the information push instruction. To address this, when storing the content to be pushed on each platform, the content identifier on the platform and the pre-determined content identifier can be recorded, thus establishing a mapping relationship between the content identifiers on the platform and the pre-determined content identifiers. The content identifier of the content to be pushed in the information push instruction can be determined based on the content to be pushed itself and the pre-determined content identifier.

[0084] The following example illustrates the information push method provided in this manual by using an information push tool to push information to a bank platform and a third-party platform (which can be a social platform).

[0085] Banks typically possess rich customer profile data, segmenting users into multiple groups for more effective operations. However, the bank's user system is not interconnected with the user systems of third-party social media channels. User identities defined by the bank cannot be directly used on third-party platforms; that is, marketing methods tailored to the bank's segmented customer groups cannot be directly applied to third-party platforms. Due to this limitation, banks often adopt a broad-based approach on third-party platforms. While this broad-based approach can reach more customers and increase exposure and traffic, it suffers from a lack of focused promotion, distraction of customer attention, increased operational costs in terms of manpower and resources, increased operational complexity and cost, and reduced conversion rates.

[0086] When banks use the information push method provided in this manual, they can specifically perform the following steps 1-9.

[0087] Step 1: Operators can segment users into different customer groups based on user profiles within the banking application, such as region, gender, age, and usage habits. Each customer group is associated with the user's identity identifier, bankcust_id.

[0088] Step 2: Based on the customer segmentation in Step 1, use the association table formed by the "User Identity Mapping Relationship Establishment Module" to synchronously associate the customer segments with the user's user identity identifier opencust_id on the third-party platform;

[0089] Step 3: Operators can segment users into different customer groups based on user profiles on third-party platforms, such as usage habits and preferred content. Each customer group is associated with the user's identity identifier, opencust_id.

[0090] Step 4: Based on the customer segmentation in Step 3, use the association table formed by the "User Identity Mapping Relationship Establishment Module" to synchronously associate the customer segments with the user's user identity identifier bankcust_id within the bank application;

[0091] Step 5: The operator selects the placement and format based on the promotional content of the activity;

[0092] Step 6: The operator selects the target customer groups. At this point, the customer groups are associated with the user's identity identifier bankcust_id within the bank application and the user's identity identifier opencust_id on the third-party platform.

[0093] Step 7: Based on the results of the selections in Steps 5 and 6, and the customer preference channels identified in the "Joint Operation Channel Selection Module", select and publish the activity content to the bank's application and third-party platforms.

[0094] Step 8: The target customer group can view the promotional content through any channel, either within the bank's app or on a third-party platform, and the system records the user's access information;

[0095] Step 9: Operators can view the promotion status of activities on various channels based on the user access data recorded by the system, and then adjust the channels and intensity of the promotion.

[0096] The joint operation channel selection module executes the following steps 1-4.

[0097] Step 1: Customers access business functions provided by bank applications and third-party platform accounts;

[0098] Step 2: Record customer access records, including but not limited to access functions, access channels, access times, access terminals, etc.;

[0099] Step 3: Based on the customer's access records, analyze the channels and frequency of customer access, and use the statistical data to indicate the customer's preference for each channel.

[0100] Step 4: Set the update cycle and update the customer's preference for accessing each channel according to the most recent statistical period.

[0101] The implementation of the above embodiments relies on the following two modules: the first part is to establish a mapping relationship between users on third-party platforms and bank user identity identifiers, breaking down the restrictions of user systems across different channels; the second part is a multi-channel joint operation module, which divides customer groups based on bank user identity identifiers to establish marketing strategies, and conducts joint operation and promotion on third-party platforms simultaneously through identity mapping relationships.

[0102] The user identifier in the above embodiments is the same as the user identifier in this solution, and the bank application and the third-party platform are both platforms in this solution.

[0103] It should be noted that the information and data related to users involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by the relevant parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with relevant laws, regulations, and standards, and necessary confidentiality measures have been taken. They do not violate public order and good morals, and corresponding operation entry points are provided for users or relevant parties to choose to authorize or refuse.

[0104] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0105] This specification provides an information push device that can be used to achieve... Figure 2 The information push method is shown below. For example... Figure 6 As shown, the device includes a first acquisition unit 10, a first determination unit 20, and a calling unit 30.

[0106] The first acquisition unit 10 is used to acquire information push instructions, which include the content identifier of the content to be pushed and the customer group identifier of the target audience.

[0107] The first determining unit 20 is used to determine, based on the customer group identifier, the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform.

[0108] The calling unit 30 is used to send content to be pushed to each target user in the following way: calling the target component corresponding to the target platform identifier associated with the target user identifier, and using the content identifier of the content to be pushed as the calling parameter; when the target component is called, it connects to the target platform and triggers the target platform to send the content corresponding to the content identifier to the target user, and the content corresponding to the content identifier is pre-stored in the target platform.

[0109] In some embodiments, the apparatus further includes: an establishment unit, configured to obtain user identifiers from multiple platforms and establish a correspondence between user identifiers of the same user on different platforms.

[0110] In some embodiments, the establishment unit includes: a calling subunit, configured to, when a user logs into a third-party platform and uses a service embedded in the target platform, call a first interaction component that interacts with the third-party platform to obtain a first user identifier of the user on the third-party platform and account interaction information entered when using the service embedded in the target platform, wherein the account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform; a first obtaining subunit, configured to obtain the account interaction information entered when using the service of the target platform on the third-party platform, and determine a second user identifier of the user on the target platform based on the account interaction information; and a first storage unit, configured to store the first user identifier and the second user identifier in association, wherein the first user identifier is associated with the identifier of the third-party platform, and the second user identifier is associated with the identifier of the target platform.

[0111] In some embodiments, the establishment unit includes: a second acquisition subunit, configured to acquire, through a second interaction component that interacts with the target platform, a second user identifier of the user on the target platform and a first user identifier of the user on the third-party platform entered when initiating authorization, when the user logs into the target platform and initiates authorization on the third-party platform; and a second storage unit, configured to store the first user identifier and the second user identifier together, wherein the first user identifier is associated with the identifier of the third-party platform and the second user identifier is associated with the identifier of the target platform.

[0112] In some embodiments, the information push instruction may further include a target push strategy, which is selected by the user from a plurality of push strategies.

[0113] In some embodiments, the target push strategy is selected from at least two of the following: a first strategy, a second strategy, and a third strategy; wherein the first strategy represents pushing information to all accounts of the same user on different platforms, the second strategy represents pushing information to accounts of the same user on predetermined platforms among their accounts on different platforms, and the third strategy represents pushing information to accounts of the same user on their most preferred platform among their accounts on different platforms.

[0114] In some embodiments, where the user can select a third strategy, the apparatus further includes: a second acquisition unit, configured to periodically acquire user access data statistically collected by each platform; a second determination unit, configured to determine the user's preference characteristics for each platform based on the user access data statistically collected by each platform; and a third determination unit, configured to determine the user's most preferred platform based on the user's preference characteristics for each platform.

[0115] In some embodiments, the apparatus further includes: a third acquisition unit, configured to acquire user identifiers, user data, and user identifiers from multiple platforms; a mapping unit, configured to map user data from each platform to user data of a target platform; and a classification unit, configured to classify the user data using a classification algorithm of the target platform, thereby determining the customer group identifier corresponding to each user identifier.

[0116] The descriptions and functions of the above devices can be found in the section on information push methods, and will not be repeated here.

[0117] This invention also provides an electronic device, such as... Figure 7 As shown, the electronic device may include a processor 701 and a memory 702, wherein the processor 701 and the memory 702 may be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

[0118] Processor 701 can be a central processing unit (CPU). Processor 701 can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations of the above types of chips.

[0119] The memory 702, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the information push method in the embodiments of the present invention. The processor 701 executes various functional applications and data processing of the processor by running the non-transitory software programs, instructions, and modules stored in the memory 702, thereby realizing the information push method in the above method embodiments.

[0120] The memory 702 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created by the processor 701, etc. Furthermore, the memory 702 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 702 may optionally include memory remotely located relative to the processor 701, and these remote memories may be connected to the processor 701 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0121] The one or more modules are stored in the memory 702, and when executed by the processor 701, they perform actions such as... Figure 1 The information push method in the illustrated embodiment.

[0122] The specific details of the above-mentioned electronic device can be understood by referring to the relevant descriptions and effects in the method embodiments, and will not be repeated here.

[0123] This specification also provides a computer storage medium storing computer program instructions, which, when executed by a processor, implement the steps of the above-described information push method.

[0124] This specification also provides a computer program product comprising a computer program that, when executed by a processor, implements the steps of the above-described information push method.

[0125] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0126] The various embodiments in this specification are described in a progressive manner. For the same or similar parts between the various embodiments, please refer to each other. The focus of each embodiment is to describe the differences from other embodiments.

[0127] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions.

[0128] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0129] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute certain parts of the methods of various embodiments of this application.

[0130] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0131] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0132] Although this application has been described through embodiments, those skilled in the art will know that this application has many modifications and variations without departing from the spirit of this application, and it is intended that the appended claims cover such modifications and variations without departing from the spirit of this application.

Claims

1. An information push method, characterized in that, include: Obtain an information push instruction, wherein the information push instruction includes the content identifier of the content to be pushed and the customer group identifier of the target audience; Based on the customer group identifier, determine the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform; The content to be pushed is sent to each target user in the following way: the target component corresponding to the platform identifier associated with the target user identifier is called, and the content identifier of the content to be pushed is used as the calling parameter; when the target component is called, it connects to the corresponding platform and triggers the corresponding platform to send the content corresponding to the content identifier to the target user, and the content corresponding to the content identifier is pre-stored in each platform; The method further includes: Obtain user identifiers and user data from multiple platforms; User data from each platform is mapped to user data from a second platform; the second platform can be any one of the multiple platforms. The user data is classified using the classification algorithm of the second platform to determine the customer group identifier corresponding to each user identifier. The customer group identifier is used to indicate the type of user reflected in the user data corresponding to the user identifier. Before determining the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform based on the customer group identifier, the method further includes: Obtain user identifiers from multiple platforms and establish corresponding relationships between user identifiers of the same user on different platforms, including: When a user logs into a third-party platform to use the services embedded in the target platform, the first interaction component that interacts with the third-party platform is invoked to obtain the user's first user identifier on the third-party platform and the account interaction information entered when using the services embedded in the target platform. The account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform. Determine the user's second user identifier on the target platform based on the account interaction information; The first user identifier and the second user identifier are stored together, with the first user identifier associated with the identifier of the third-party platform and the second user identifier associated with the identifier of the target platform.

2. The method according to claim 1, characterized in that, Obtain user identifiers from multiple platforms and establish corresponding relationships between user identifiers of the same user on different platforms, including: When a user logs into the target platform and initiates authorization on a third-party platform, the second user identifier of the user on the target platform and the first user identifier of the user on the third-party platform entered when initiating authorization are obtained through the second interactive component that interacts with the target platform. The first user identifier and the second user identifier are stored together, with the first user identifier associated with the identifier of the third-party platform and the second user identifier associated with the identifier of the target platform.

3. The method according to claim 1, characterized in that, The information push instruction also includes a target push strategy, which is selected by the user from multiple push strategies.

4. The method according to claim 3, characterized in that, The target push strategy is selected from at least two of the following: a first strategy, a second strategy, and a third strategy; The first strategy involves pushing information to all accounts of the same user on different platforms; the second strategy involves pushing information to the accounts of the same user on the preferred platform among all accounts on different platforms; and the third strategy involves pushing information to the accounts of the same user on the most preferred platform among all accounts on different platforms.

5. The method according to claim 3, characterized in that, When the user can select a third strategy, the method further includes: Regularly obtain user access data from various platforms; Determine user preferences for each platform based on user access data collected from each platform. The user's most preferred platform is determined based on their preferences for each platform.

6. The method according to claim 1, characterized in that, When determining the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform based on the customer group identifier: If the first user identifier of the first platform has a corresponding stored second user identifier of the second platform, then one of the first user identifier and the second user identifier is determined as the target user identifier.

7. An information push device, characterized in that, include: The first acquisition unit is used to acquire information push instructions, wherein the information push instructions include the content identifier of the content to be pushed and the customer group identifier of the target audience. The first determining unit is used to determine, based on the customer group identifier, the set of target user identifiers corresponding to the customer group identifier in the user identifier set of each platform; The calling unit is used to send content to be pushed to each target user in the following way: calling the target component corresponding to the platform identifier associated with the target user identifier, and using the content identifier of the content to be pushed as the calling parameter; when the target component is called, it connects to the corresponding platform and triggers the corresponding platform to send the content corresponding to the content identifier to the target user, and the content corresponding to the content identifier is pre-stored in each platform; The third acquisition unit is used to acquire user identifiers and user data from multiple platforms; The mapping unit is used to map user data from one platform to user data from a second platform. The second platform can be any one of multiple platforms; The classification unit is used to classify the user data using the classification algorithm of the second platform and determine the customer group identifier corresponding to each user identifier. The customer group identifier is used to indicate the type of user reflected by the user data corresponding to the user identifier. The unit is used to call the first interaction component that interacts with the third-party platform when a user logs into the third-party platform to use the service embedded in the target platform, to obtain the user's first user identifier on the third-party platform and the account interaction information entered when using the service embedded in the target platform. The account interaction information is used to authorize the association between the user identifier of the third-party platform and the user identifier of the target platform. Determine the user's second user identifier on the target platform based on the account interaction information; The first user identifier is associated with and stored together with the second user identifier, wherein the first user identifier is associated with the identifier of the third-party platform and the second user identifier is associated with the identifier of the target platform; or, when a user logs into the target platform and initiates authorization on the third-party platform, the user's second user identifier on the target platform and the user's first user identifier on the third-party platform entered when initiating authorization are obtained through a second interactive component that interacts with the target platform; the first user identifier is associated with and stored together with the second user identifier, wherein the first user identifier is associated with the identifier of the third-party platform and the second user identifier is associated with the identifier of the target platform.

8. An electronic device, characterized in that, include: The system includes a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to implement the information push method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by a processor, implement the information push method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, implements the information push method according to any one of claims 1 to 6.

Images