Sign-in task view configuration method, electronic equipment, storage medium and program product

Abstract

The embodiment of the invention provides a sign-in task view configuration method, electronic equipment, a storage medium and a program product. Relates to the technical field of financial science. Multi-dimensional attribute information such as a user identity identifier, a target system identifier and a service label is accurately collected, specific service requirements are anchored in combination with the target system identifier and the service label, personalized sign-in periods, task strategies and incentive strategies are matched based on a preset configuration database, and finally an exclusive sign-in task view is generated. The method has the core beneficial effects that the problem that a traditional bank APP sign-in function is cut at a time is thoroughly solved, and the sign-in willingness of a user and the use stickiness of the APP are remarkably improved by matching the incentive and task forms meeting the financial requirements of the user through the service labels of the user; and meanwhile, deep binding of a sign-in function and a bank operation target can be realized, and subdivision business requirements are associated through a target system identifier, so that sign-in becomes an effective carrier for pushing key business conversion.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of financial technology, and in particular to a check-in task view configuration method, an electronic device, a storage medium and a program product. BACKGROUND

[0002] Nowadays, a bank APP has been upgraded from a traditional account tool to a comprehensive financial service platform, and user activity is directly related to core indicators such as financial sales and credit conversion. As a key module for activating users at low cost, the view configuration of check-in needs to be consistent with the characteristics of banks, that is, "compliance first, customer stratification", which not only guides high-frequency use, but also conveys a safe and professional brand image.

[0003] The current mainstream check-in task view configuration technology of the bank APP is a "standardized fixed rule mode", that is, a unified check-in logic is preset in the development stage, such as "fixed points for daily check-in, small amount of rights and interests for continuous 7-day check-in", and all users use the same view interface and incentive standard.

[0004] However, in the above method, the user can only check in according to the fixed rule mode, resulting in low flexibility of the check-in task. SUMMARY

[0005] The check-in task view configuration method, the electronic device, the storage medium and the program product provided by the embodiments of the present application are used to improve the check-in willingness and stickiness of different users.

[0006] In a first aspect, the embodiments of the present application provide a check-in task view configuration method, comprising:

[0007] obtaining user attribute information of a target user, the user attribute information including an identity of the user, an identity of a target system registered by the user, and a business label corresponding to the user in the target system;

[0008] determining business requirement information of the target system according to the identity of the target system and the business label;

[0009] determining a check-in period configuration corresponding to the user attribute information, a strategy of a check-in task, and a strategy of obtaining an incentive after completing the check-in, based on a preset configuration database and the business requirement information;

[0010] determining a check-in task view of the target user based on the check-in period configuration, the strategy of the check-in task, and the strategy of obtaining the incentive, the check-in task view being used to display a check-in task associated with the user and incentive information corresponding to the check-in task.

[0011] In a second aspect, the embodiments of the present application provide a check-in task view configuration device, comprising:

[0012] The acquisition module is configured to acquire user attribute information of the target user, the user attribute information comprising an identity of the user, an identity of a target system registered by the user, and a service label corresponding to the user in the target system.

[0013] The determination module is configured to determine service requirement information of the target system according to the identity of the target system and the service label.

[0014] The determination module is further configured to determine, based on a preset configuration database and the service requirement information, a check-in period configuration corresponding to the user attribute information, a strategy of a check-in task, and a strategy of obtaining an incentive after completing the check-in.

[0015] The configuration module is configured to determine, based on the check-in period configuration, the strategy of the check-in task, and the strategy of obtaining the incentive, a check-in task view of the target user, the check-in task view being used to display a check-in task associated with the user and incentive information corresponding to the check-in task.

[0016] In a third aspect, an electronic device is provided, comprising a memory and a processor.

[0017] The memory stores computer-executable instructions.

[0018] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect.

[0019] In a fourth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the first aspect and / or various possible implementation manners of the first aspect.

[0020] In a fifth aspect, a computer program product is provided, and the computer program product comprises a computer program. When the computer program is executed by a processor, the computer program implements the first aspect and / or various possible implementation manners of the first aspect.

[0021] The check-in task view configuration method, the electronic device, the storage medium and the program product provided by the embodiment of the application, through accurately collecting multi-dimensional attribute information such as user identity, target system identifier and business label, combining the target system identifier and the business label to anchor specific business requirements, and matching personalized check-in periods, task strategies and incentive strategies based on a preset configuration database, finally generating a dedicated check-in task view, the core beneficial effect of which is to completely solve the problem of the traditional bank APP check-in function "one size fits all", through matching the incentive and task form of the financial needs of the user by the business label, significantly improving the user check-in willingness and APP use stickiness; at the same time, the check-in function and the bank operation target can be deeply bound, through the target system identifier to associate the subdivided business requirements, so that the check-in becomes an effective carrier to promote the conversion of key businesses. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0023] Figure 1 The flowchart of the check-in task view configuration method provided by the embodiment of the application Figure One ;

[0024] Figure 2 The flowchart of the check-in task view configuration method provided by the embodiment of the application Figure Two ;

[0025] Figure 3 The structure diagram of the check-in task view configuration device provided by the embodiment of the application

[0026] Figure 4 The structure diagram of the electronic device provided by the embodiment of the application.

[0027] Through the above drawings, the specific embodiments of the present application have been shown, and there will be more detailed descriptions in the following. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, the same numbers are used to indicate the same or similar components. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of devices and methods consistent with some aspects of the present application, as detailed in the appended claims.

[0029] In view of the pain point that the standardization configuration of the bank APP sign-in function is inconsistent with business requirements and user requirements, a closed-loop configuration logic of "user attribute collection - business requirement anchoring - rule matching - view generation" is constructed. First, the data basis of personalized configuration is consolidated by collecting three types of core attribute information of user identity, target system identity and business label. Then, the basic operation requirements of bank sub-business fields are locked based on the target system identity, and the demand granularity is further refined by combining the user business label to form accurate business requirement information. Subsequently, the sign-in period, task strategy and incentive strategy corresponding to the user attributes and business requirements are matched based on the association mapping relationship of "system - label - rule" in the preset configuration database. Finally, the personalized sign-in task view is generated by integrating the three types of strategies, the accurate matching of the sign-in function and the bank operation target and the user financial requirement is realized, the problem of "one-size-fits-all" of the traditional sign-in configuration is solved, and the user participation and business conversion efficiency are improved.

[0030] In the technical solution of the present application, the collection, storage, use, processing, transmission, provision and disclosure of financial data or user data and other information comply with relevant laws and regulations and do not violate public order and good customs.

[0031] It should be noted that in the embodiments of the present application, some existing industry solutions, components, models and the like may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0032] The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0033] Figure 1 Flowchart of the sign-in task view configuration method provided by the embodiments of the present application Figure One The above method provided by the embodiments of the present application is applied to any electronic device. As shown in Figure 1 The method comprises the following steps.

[0034] S101, obtaining user attribute information of a target user, the user attribute information comprising an identity of the user, an identity of a target system registered by the user, and a business label corresponding to the user in the target system.

[0035] The user attribute information is used for uniquely identifying the user identity, associating the user with a business system, and defining a comprehensive information set of specific business scenarios, is the core data basis for subsequent personalized check-in view configuration, and specifically includes three types of key information: identity identification, i.e., the unique identification credential of the user in the digital service system, such as an account ID, a real-name authentication mobile phone number, an ID card number, etc., for ensuring accurate positioning of the user identity; target system identification, i.e., the specific bank APP exclusive identification of the user registered and used, for distinguishing the business carriers and supporting service systems of different banks; and business label, i.e., the scenario-based identification generated by the bank APP according to user identity information, asset size, transaction behavior, and service preferences, for accurately matching the business promotion goals of the bank with the customer service needs.

[0036] Specifically, the data collection range is defined as the three types of core information of “identity identification + target system identification + business label”. Among them, the identity identification is automatically extracted through the user login state (such as after the user logs in to the bank APP, the system associates and extracts the customer number according to the real-name authentication information); the target system identification is directly determined by the bank APP environment currently operated by the user; and the business label is directly called from the bank customer label library, which is dynamically updated by the system according to the user historical behavior data (such as credit card transaction records, financial product purchase amounts, and monthly repayment frequencies) and registration information (such as age, occupation, and asset level). For example, the system marks a user with “monthly average financial asset of 500,000 yuan or more and large amount transfer record in the last 3 months” as a “financial gold customer”, and marks a user with “newly opened credit card without binding” as a “credit card new customer”. Through the integration and verification of the three types of information, a complete user attribute information set is formed, providing a reliable data basis for subsequent accurate matching of bank business needs.

[0037] S102, determining the business demand information of the target system according to the identification and business label of the target system.

[0038] Among them, the business demand information is determined by the bank APP identification and the user business label, and reflects the core information of the bank operation target and customer service demand. For example, the core demand of the bank APP for “credit card new customers” is “guiding card binding and consumption, and activating user card usage habits”; the demand for “financial gold customers” is “improving financial business interaction frequency and accurately pushing exclusive financial products”; and the demand for “old-age savings customers” is “optimizing operation process convenience and strengthening savings business safety prompts”.

[0039] Specifically, a "bank APP identifier-business label-business demand" association rule library is constructed in advance. Different bank APPs correspond to different demand orientations due to differences in core business positioning. Within the same bank APP, users with different business labels correspond to different demand focuses: when the system identifier is "China Merchants Bank APP" and the business label is "new user of wealth management", the business demand is determined to be "guide the user to complete the first check-in, synchronously push the entry-level wealth management product, and cultivate the habit of wealth management operation"; when the system identifier is "a bank APP" and the business label is "high-frequency repayment user", the business demand is "bind the repayment scene through check-in incentive to improve the use rate of APP repayment service". This step realizes the accurate conversion from user attributes to bank business demand, and ensures that the subsequent configuration scheme is consistent with the financial scene operation goal.

[0040] S103, based on the preset configuration database and the business demand information, determining the check-in period configuration, the check-in task strategy, and the strategy for obtaining incentives after completing the check-in corresponding to the user attribute information.

[0041] The check-in period configuration is a check-in time rule system formulated for bank APP users, which determines the time range, frequency requirement, and period type of check-in in combination with the characteristics of financial business scenes. For example, "7-day wealth management knowledge promotion continuous check-in", "credit card repayment reminder check-in from the 1st to the 10th of each month", and "check-in time period from 7:00 to 23:00 every day" (covering the main operation time period of salaried people).

[0042] The check-in task strategy is a standardized rule system for guiding the design and execution of bank APP check-in tasks, which determines core elements such as task form (such as click check-in, check-in after completing credit card repayment, check-in after watching financial knowledge propaganda video, check-in after browsing exclusive wealth management product details, etc.), task trigger condition (such as unlocking check-in permission after first binding card, opening advanced check-in channel after asset reaching standard), and check-in validity determination standard (such as excluding non-personal operation through positioning verification, confirming task completion status through transaction record matching).

[0043] The strategy for obtaining incentives after completing the check-in is a financial attribute reward rule system directly bound with the bank APP check-in task, which determines the incentive type (such as bank points, payment discount, credit card repayment deduction coupon, wealth management fee discount, exclusive gift redemption right, senior wealth management consultant consulting service, etc.), reward amount standard (such as 2 yuan payment discount for 7 consecutive days of check-in, 50 yuan wealth management coupon for 30 days of cumulative check-in), delivery method (instantly credited to APP account, manually collected after cumulative standard is reached), and usage restriction (such as 10 yuan or more for payment discount, wealth management discount limited to specified products).

[0044] Specifically, the preset configuration database stores multiple sets of standardized configuration templates corresponding to the bank business needs, while reserving flexible adjustment space to adapt to special scenarios. First, according to the "time attribute" of the business needs, the sign-in period configuration is determined: for example, the "credit card new user acquisition" demand corresponds to a "7-day continuous period" (which matches the key period for cultivating new user habits), and the "financial customer long-term retention" demand corresponds to a "30-day cumulative period" (which matches the decision-making period of financial business). Second, the sign-in task strategy is determined in combination with the "behavior guidance target" of the business needs: for example, the bank APP "promote credit card consumption" demand corresponds to the task form of "bind card consumption 1 times can sign in", the "popularize financial knowledge" demand corresponds to the task form of "watch 3 minutes of propaganda video can sign in", and the "improve financial interaction frequency" demand corresponds to the task form of "browse exclusive financial product details for 10 seconds can sign in". Finally, the incentive strategy is determined according to the "incentive orientation" of the business needs: for example, the "financial new user conversion" demand corresponds to "10 yuan of financial service fee deduction coupon", the "credit card old user retention" demand corresponds to "points accumulation + monthly payment deduction lottery" mechanism, and the "high net worth customer maintenance" demand corresponds to "points exchange for exclusive physical examination service + consultation by experienced financial consultant". With the support of the configuration database, the precise matching of the three types of configurations and the bank business needs is realized, while ensuring compliance with the requirements of financial services.

[0045] S104, based on the sign-in period configuration, the strategy of the sign-in task, and the strategy of obtaining the incentive, determine a sign-in task view of the target user, the sign-in task view being used to display the sign-in task associated with the user and the incentive information corresponding to the sign-in task.

[0046] The sign-in task view is a professional visual interaction interface component for bank APP users, and its core function is to centrally display the sign-in tasks matched with the user's identity level, asset status, and bank service needs, and clearly present the incentive rules and reward contents (such as bank points, payment deduction, financial preferential benefits, etc.) corresponding to each task, providing intuitive sign-in operation guidance and clear value expectations for users, and is usually deployed in the "personal center" or exclusive activity module of the bank APP.

[0047] Specifically, first, the three types of configurations are interface decomposed and converted: the check-in period configuration is converted into a "period progress bar + make-up check-in function entrance" (such as "7-day continuous check-in, 3 days have been completed, and 1 time can be made up", which is adapted to the fragmentation operation characteristics of bank users); the check-in task strategy is converted into "task guide text + safety prompt description" (such as "credit card repayment 1 time over 10 yuan can check in, and the fund safety is guaranteed by the bank throughout the process") and "task state identification button" (such as "unpaid / go to repayment / can check in"); the incentive strategy is converted into "reward preview icon" (such as exclusive icons of discount coupons and cash discounts) and "reward description text" (such as "check-in can get 500 bank points, and the points can be directly deducted from the credit card annual fee"). Secondly, according to the operation habits of bank users and the display specifications of financial information, the interface elements are integrated, the safety prompt and the risk description are placed in a prominent position, the period progress is ensured to be intuitive and clear, the task guide is ensured to be accurate and clear, and the reward information is ensured to be prominent and in compliance. Finally, the visual adaptation is performed in combination with the brand visual style of the bank APP, the operation path of the old customer group is optimized, and finally a standardized check-in task view is formed. The view accurately presents the check-in information related to the bank users, reduces the understanding cost of financial services, strengthens the check-in motivation of the users through practical incentives, and realizes the organic unification of the bank business demand and the customer experience.

[0048] The check-in task view configuration method provided in the embodiments of the present application accurately collects multi-dimensional attribute information such as the user identity, the target system identifier and the business tag, anchors specific business demands in combination with the target system identifier and the business tag, matches personalized check-in periods, task strategies and incentive strategies based on a preset configuration database, and finally generates a dedicated check-in task view. The core beneficial effect lies in that the problem of "one-size-fits-all" of the traditional bank APP check-in function is completely solved, the incentives and task forms that meet the financial demands of the users are matched through the business tag of the users, the check-in willingness of the users and the APP use stickiness are significantly improved, the check-in function and the bank operation target can be deeply bound, the check-in becomes an effective carrier for promoting the conversion of key businesses through the association of the target system identifier with the subdivided business demands.

[0049] Figure 2 The flowchart of the check-in task view configuration method provided in the embodiments of the present application Figure Two As shown in Figure 2 , the method comprises the following steps.

[0050] S201, acquiring user attribute information of a target user, the user attribute information comprising an identity of the user, an identifier of a target system registered by the user, and a business tag corresponding to the user in the target system.

[0051] In a possible implementation, when it is detected that a target user triggers a check-in function entrance, a user information acquisition request is generated, the user information acquisition request including token information of a current login state of the target user; the user information acquisition request is sent to a user center database to acquire an identity bound to the token information; based on the identity, an identity of a target system registered by the target user is extracted from a business system database; based on the identity, business behavior data of the target user within a preset period is acquired; the business behavior data is input into a preset algorithm to obtain a business label of the target user; and based on the identity, the identity of the target system and the business label, user attribute information of the target user is determined.

[0052] The check-in function entrance is an interactive node in the bank APP for triggering the check-in function, and common forms include a check-in icon of a "my" page, a homepage pop-up prompt, an activity center entrance, etc., which is a starting point for the user to enter the check-in process. The token information of the login state is an encrypted string generated by the system to identify the user login state after the user successfully logs in the bank APP, which contains user identity digest information and login validity period, and is the core credential for ensuring the security of user information acquisition. The user center database is a database built by the bank to centrally store core user identity information, which contains user identity, real-name authentication information, login state and other data, has high security and authority, and provides unified user identity verification services for various business systems. The business system database is a database storing related data of various business line systems of the bank, which contains system information registered by the user, business handling records, etc., such as a credit card system database, a financial system database, etc., supporting extraction of business labels and improvement of user attributes. The business behavior data is operation data generated by the user in the bank APP and various business systems within a preset period (such as the last 30 days), including transaction records (such as credit card consumption, financial purchase), browsing records (such as product viewing, information reading), function use records (such as card binding, repayment), etc., which is the core data source for generating business labels.

[0053] Specifically, the operation state of the check-in function entrance is monitored in real time through an event listening function, and when it is detected that the user clicks the "check-in" icon, the current login token information of the user (the token is generated by the system when the user logs in, and contains a 60-minute validity period) is immediately acquired. Based on the token information, a standardized user information acquisition request including "request type: user information acquisition; operation terminal: mobile phone model + address; request time: timestamp" is generated to ensure the uniqueness and traceability of the request.

[0054] The user information acquisition request is sent to the user center database, the database receives the request first, parses the token information, checks its validity (such as whether it is within the validity period, whether the signature matches), after the check, according to the binding relationship between the token and the identity, extracts the unique identity of the user (such as the customer number associated with the identity card number after real name authentication), and returns the identification to the request initiation end, ensures the safety of the transmission of the identity information.

[0055] The acquired user identity is used as a retrieval condition, and a query interface of a business system database is called to retrieve the registration record of the user in each business system of the bank. For example, if the user only registers and uses the credit card APP, the "credit card APP exclusive identification" is extracted; if the user registers the financial APP and the savings APP at the same time, the "financial APP identification" is extracted in combination with the current operation scene (such as triggering the check-in from the financial APP), to ensure that the target system identification is consistent with the current operation scene of the user.

[0056] The user's business behavior data is extracted according to a preset period (such as the last 30 days) by calling the interfaces of the credit card system, the financial system, the payment system and other business databases with the user identity as the associated field. The extraction range includes "3 credit card consumption records with consumption amount ≥1000 yuan, 5 times of browsing financial product details, 2 times of completing credit card repayment, 1 time of binding WeChat payment" and other structured data. The extracted data is de-duplicated and cleaned to ensure the integrity and accuracy of the data.

[0057] The cleaned business behavior data is converted into a feature vector (such as "consumption frequency: 3 times / month; financial attention: high; repayment timeliness: 100%") that can be recognized by an algorithm, and is input into a preset decision tree classification algorithm model. The model compares the feature vector with a label rule library (such as "consumption frequency ≥2 times / month and financial attention high → credit card active user") and outputs the business label corresponding to the user. If there are multiple matching labels, the final label is determined according to the "weight priority", such as "credit card active user + financial potential customer", and each label is assigned a confidence score.

[0058] The "identity: customer number XXX; target system identification: credit card APP identification; business label: credit card active user + financial potential customer" three types of information are associated and integrated, and consistency check (such as checking whether the binding relationship between the identity and the system identification is valid) is performed. After the check, a structured user attribute information set is generated according to the bank's preset data specification format, and is stored in the temporary data cache of the check-in function, providing direct data support for subsequent check-in configuration matching.

[0059] S202, according to the identification and business label of the target system, determine the business demand information of the target system.

[0060] S203, based on the preset configuration database and the business demand information, determine the check-in period configuration corresponding to the user attribute information, the strategy of the check-in task, and the strategy of obtaining the incentive after completing the check-in.

[0061] In a possible implementation, multi-dimensional configuration demand information is collected, the multi-dimensional configuration demand information including a check-in scene demand in a business line dimension, a benefit configuration demand in a user level dimension, and an activity rule demand in a region dimension; the multi-dimensional configuration demand information is structurally analyzed to extract core configuration items; a hierarchical structure of the configuration database is constructed, the hierarchical structure including a basic configuration layer, a user grouping configuration layer, and a business-specific configuration layer, wherein the basic configuration layer stores general check-in rules, the user grouping configuration layer associates business tags with differentiated configurations, and the business-specific configuration layer binds the identification of a target system and regionalization strategies; the core configuration items are stored in the database according to the hierarchical structure, and a mapping relationship index between user attribute information and each configuration item is established, to obtain the configuration database.

[0062] The multi-dimensional configuration demand information is check-in configuration demand data covering multiple aspects collected from a bank APP operation scene, and specifically includes a check-in scene demand in a business line dimension (such as a credit card business, a financial business, and a savings business), a benefit configuration demand in a user level dimension (such as an ordinary customer, a special customer, and a high net worth customer), and an activity rule demand in a region dimension (such as a first-tier city and a third- or fourth-tier city), and is a core basis for constructing the configuration database.

[0063] The structural analysis is a process of converting unstructured or semi-structured configuration demand information into structured data conforming to a preset data specification, and the demand information has the characteristics of being storable and searchable by extracting key information, determining data types, and establishing association relationships.

[0064] The core configuration item is a key data item extracted from the multi-dimensional configuration demand information, which determines the core logic of the check-in configuration, such as a check-in period type, a task trigger condition, an incentive benefit level, and a regional activity time range, and is a core storage content of the configuration database.

[0065] The hierarchical structure of the configuration database is a database architecture designed for precise matching and flexible expansion of the check-in configuration, and is divided into three levels of a basic configuration layer, a user grouping configuration layer, and a business-specific configuration layer, each level has clear responsibilities and is associated with each other, and supports the landing of multi-dimensional configuration demand.

[0066] The mapping relationship index is an index structure of the association relationship between user attribute information (an identity, a system identification, and a business tag) and each core configuration item in the configuration database, and is used to improve the retrieval efficiency of the configuration matching and ensure that the check-in configuration can be quickly and accurately positioned.

[0067] Specifically, the combination of "business line interview + data statistics + regional feedback" is adopted. For the business line dimension, the credit card, financial management, and savings departments are connected to collect the "credit card business needs to guide the sign-in scene demand of card consumption" and "financial management business needs to improve product browsing sign-in scene demand"; for the user level dimension, the rights and interests preferences of users at different levels are counted through the customer management system to clarify the "special customers need special high-value incentive configuration demand"; for the regional dimension, the activity planning of each branch is collected to obtain the "first-tier city focuses on payment reduction activity rule demand" and "third and fourth-tier cities focus on savings points activity rule demand", and finally a multi-dimensional demand information library is formed.

[0068] Taking the demand of "credit card business line, for new customers, first-tier city, needs 7-day continuous sign-in, complete card consumption sign-in, and incentive is 10 yuan payment reduction" as an example, through structured analysis, data types (such as period type: continuous period; period length: 7 days), association conditions (such as business line: credit card; user label: new customer; region: first-tier city), core rules (such as task trigger: card consumption; incentive type: payment reduction; incentive amount: 10 yuan) and other elements are extracted, and finally a core configuration item set of "business line-user label-region-period configuration-task strategy-incentive strategy" is formed, and is stored in a preset format.

[0069] A three-level architecture is constructed and the responsibilities of each level are clarified: the basic configuration layer stores the general sign-in rules of the whole system, such as "the daily sign-in valid period is 7:00-23:00" and "sign-in status is synchronized in real time"; the user grouping configuration layer establishes the association between business labels and differentiated configurations, such as associating the "credit card new customer" label with the "7-day continuous period" and "card consumption task"; the business-specific configuration layer binds the target system identifier and regional strategy, such as associating the "credit card APP identifier" with the "10 yuan reduction in first-tier cities" and "8 yuan reduction in third and fourth-tier cities". Each level realizes data interconnection through the association field of "user attribute-configuration item".

[0070] The general rule type core configuration item is stored in the basic configuration layer, the differentiated configuration associated with the user label is stored in the user grouping configuration layer, and the strategy associated with the system identifier and region is stored in the business-specific configuration layer. After storage is completed, a mapping relationship index is established with "user attribute information (business label associated with identity identifier, target system identifier)" as the retrieval key and "configuration items matched by each level" as the value, for example, "identity identifier A-business label: credit card new customer-target system identifier: credit card APP" corresponds to the index value "basic configuration: 7:00-23:00 sign-in; user grouping configuration: 7-day continuous period + card consumption task; business-specific configuration: 10 yuan reduction in first-tier cities", and finally a complete configuration database is formed.

[0071] In a possible implementation, the differentiated configuration of the target user is obtained based on the matching of the business label and the user grouping configuration layer; the regionalization strategy of the target user is obtained based on the matching of the identification of the target system and the business exclusive configuration layer; and the differentiated configuration and the regionalization strategy are matched with the basic configuration layer to obtain the check-in period configuration, the strategy of the check-in task, and the strategy of obtaining the incentive of the target user.

[0072] The differentiated configuration is the check-in configuration content generated based on the user business label and different from the ordinary user, and embodies the configuration concept of “thousand faces for a thousand people”. For example, the “7-day continuous period” for a new credit card user and the “monthly cumulative check-in” for an ordinary user are differentiated configurations. The regionalization strategy is the check-in configuration strategy customized for a specific regional user in combination with the business demand and operation focus of the region to which the target user belongs. For example, the difference between the “payment reduction gold” in a first-tier city and the “savings points” in a third- or fourth-tier city is a regionalization strategy. The basic configuration is the general check-in rule in the configuration database covering all user groups, and is the basic guarantee of the personalized configuration, which ensures the unity and standardization of the check-in function, such as the check-in time range and the state verification rule.

[0073] Specifically, the business label (such as “financial gold customer”) of the target user is extracted, and a retrieval interface of the configuration database is called to match in the user grouping configuration layer with the label as the retrieval key. In the matching process, the configuration items directly corresponding to the associated label are preferentially associated, such as the “30-day cumulative check-in period” and the “task of browsing exclusive financial products” associated with the “financial gold customer” label. If there are multiple associated configurations, the optimal result is selected according to the “configuration priority”, and finally the differentiated configuration content of the user is obtained.

[0074] The identification of the bank APP currently operated by the user (such as “financial APP identification”) is obtained, and the matching operation is performed in the business exclusive configuration layer in combination with the regional information (determined by the user registration location or the frequently used login location) associated with the APP. For example, the “financial APP identification + a region” matches the regionalization strategy of “continuous check-in for 10 days to obtain a financial service fee 8-fold coupon”, and the “financial APP identification + a region” matches the strategy of “continuous check-in for 10 days to obtain a financial service fee 7-fold coupon”, and finally the regionalization strategy suitable for the region to which the user belongs is obtained.

[0075] Extract the general rules of the basic configuration layer (such as "Sign in every day from 9:00 to 21:00"), then integrate the differentiated configuration ("30-day cumulative sign-in period" "Browse exclusive financial product tasks") and regionalized strategy ("Financial service fee 8-fold coupon") into the general rules, perform configuration conflict verification (such as checking whether the period and time range are compatible), and if there is a conflict, adjust according to the priority of "business exclusive configuration layer > user grouping configuration layer > basic configuration layer". Finally, obtain the complete sign-in configuration containing "sign-in period, task form, incentive content, and effective time", ensuring the unity of the generality and individuality of the configuration.

[0076] S204, a preset bitmap marker is obtained, and the bitmap marker is used to represent a sign-in state of a target user.

[0077] The bitmap marker is used to visually present a graphical identification of the sign-in state of the target user, is a standardized marker composed of pixel points or vector graphics, and can distinguish "signed in", "not signed in", "can be signed in" and other sign-in results through different colors, shapes or states (such as filled / empty, lit / dim). It has intuitiveness and easy identification, and is suitable for the multi-terminal display requirements of the bank APP. The sign-in state reflects the sign-in completion of the target user in a specific sign-in period, including but not limited to "signed in today", "not signed in today", "historical missed sign-in", "successful sign-in", "invalid sign-in" and other specific states, and is one of the core display information of the sign-in task view.

[0078] Specifically, the preset bitmap marker set is called through a resource interface. The set has been classified according to the sign-in state completion, such as a red solid dot corresponding to "signed in", a gray hollow dot corresponding to "not signed in", and a yellow translucent dot corresponding to "can be signed in". The marker size and style have been adapted to the visual specifications of the bank APP. After calling, the marker resource is verified for effectiveness to ensure that it can be normally rendered and displayed.

[0079] S205, the sign-in period configuration, the sign-in task strategy and the strategy for obtaining incentives are combined with the bitmap marker to obtain a sign-in task view of the target user.

[0080] Specifically, an association rule between the configuration information and the bitmap marker is established. For example, in a "7-day continuous sign-in period", the period information of "the first day signed in" is bound to a "red solid dot", and the period information of "the second day not signed in" is bound to a "gray hollow dot". At the same time, the incentive strategy "complete the third day sign-in to get 5 yuan of repayment discount" is associated to the bitmap marker beside the third day in the form of a text label. Through the interface rendering engine, the markers and associated information are arranged in chronological order, and the brand visual elements (such as background color and font) of the bank APP are superimposed. Finally, a clear structure and clear state sign-in task view is generated and pushed to the user interface for display.

[0081] By combining the check-in period configuration, check-in task strategy and incentive strategy with the preset bitmap mark to generate a check-in task view, first, the different check-in states such as "checked in" and "not checked in" are intuitively distinguished by means of the bitmap mark, solving the problem of low user recognition efficiency when traditional check-in information is described in words, especially adapting to the fragmented operation scene of bank APP users, so that users can quickly obtain core check-in information and significantly improve the interactive experience.

[0082] In a possible implementation, a check-in request of a target user is received; based on the check-in request, a check-in timestamp is determined; and according to the check-in timestamp, a bitmap mark in the check-in task view is updated.

[0083] The check-in request is an operation application submitted by the target user to the system to make up for the missing check-in record, which is a structured request containing user identity information, missing check-in date and other key data, and can be triggered by clicking a "check-in" button or the like, and needs to meet the preset check-in rules of the bank APP (such as redeeming check-in with points or completing a specified task to check in).

[0084] The check-in timestamp is a time identifier for accurately recording the execution time of the check-in operation, in the format of a standard timestamp, containing the check-in application submission time and the check-in success confirmation time, and is the core basis for updating the check-in state and tracing the operation record, guaranteeing the traceability of data in the financial scene.

[0085] Specifically, when the user clicks the "make up" button in the check-in task view, the system automatically generates a make-up request containing "user identity, date of applying for make-up, and current operation terminal information". After the interface receives the request, it first verifies the validity of the user login state (such as whether the token is expired), and then verifies whether the make-up date is within the allowed make-up range (such as only supporting make-up for the last 7 days of missing check-in). After the preliminary verification is passed, the subsequent process is entered. The system extracts the "date of user's application for make-up" from the verified make-up request, records the system time (accurate to seconds) of the make-up request submission, and generates a "make-up date-submission time-confirmation time" composite timestamp. For example, the user applies for make-up on December 7, 2025 at 15:30 on December 9, 2025, and the system generates a timestamp of "20251207-20251209153000-20251209153001" (the last segment is the make-up confirmation time), and binds and stores the timestamp with the user identity. The system locates the bitmap mark of the corresponding date in the check-in task view according to the "make-up date" in the make-up timestamp, replaces the original "gray hollow dot (not checked in)" with a "yellow solid dot (make-up success)", and adds a "make-up" small character mark next to the mark. After the update operation is completed, the new view state is synchronized to the bank APP interface currently operated by the user through the push mechanism, ensuring that the user can perceive the make-up result in real time; at the same time, the make-up timestamp and the updated check-in state are synchronized to the background database, completing the data loop.

[0086] The check-in task view configuration method provided by the embodiments of the present application can accurately collect multi-dimensional attribute information such as user identity, target system identifier and business label, anchor specific business requirements in combination with the target system identifier and business label, and match personalized check-in periods, task strategies and incentive strategies based on a preset configuration database, and finally generate a dedicated check-in task view. The core beneficial effect is that it completely solves the "one-size-fits-all" problem of the traditional bank APP check-in function, matches the incentive and task form that meets the financial needs of the user through the user business label, significantly improves the user's check-in willingness and APP use stickiness; at the same time, it can realize the deep binding of the check-in function and the bank operation target, associate the subdivided business requirements through the target system identifier, and make the check-in an effective carrier to promote key business conversion.

[0087] Figure 3 The structure diagram of the check-in task view configuration device provided by the embodiments of the present application is shown in Figure 3 The check-in task view configuration device 30 provided by the embodiments of the present application includes an acquisition module 301, a determination module 302 and a configuration module 303.

[0088] The acquisition module 301 is configured to acquire user attribute information of a target user, the user attribute information including an identity of the user, an identity of a target system registered by the user, and a service label corresponding to the user in the target system.

[0089] The determination module 302 is configured to determine service requirement information of the target system according to the identity of the target system and the service label.

[0090] The determination module 302 is further configured to determine, based on a preset configuration database and the service requirement information, a check-in period configuration corresponding to the user attribute information, a policy of a check-in task, and a policy of obtaining an incentive after completing the check-in.

[0091] The configuration module 303 is configured to determine a check-in task view of the target user based on the check-in period configuration, the policy of the check-in task, and the policy of obtaining the incentive, the check-in task view being used to display a check-in task associated with the user and incentive information corresponding to the check-in task.

[0092] In a possible implementation, the configuration module 303 is specifically configured to:

[0093] acquire a preset bitmap mark, the bitmap mark being used to represent a check-in state of the target user;

[0094] combine the check-in period configuration, the policy of the check-in task, and the policy of obtaining the incentive with the bitmap mark respectively to obtain the check-in task view of the target user.

[0095] In a possible implementation, the configuration module 303 is specifically configured to:

[0096] receive a make-up check-in request of the target user;

[0097] determine a make-up check-in timestamp based on the make-up check-in request;

[0098] update the bitmap mark in the check-in task view according to the make-up check-in timestamp.

[0099] In a possible implementation, the configuration module 303 is specifically configured to:

[0100] collect multi-dimensional configuration requirement information, the multi-dimensional configuration requirement information including a check-in scene requirement in a business line dimension, a benefit configuration requirement in a user level dimension, and an activity rule requirement in a region dimension;

[0101] structurally analyze the multi-dimensional configuration requirement information to extract a core configuration item;

[0102] A hierarchy of the configuration database is constructed, and the hierarchy includes a basic configuration layer, a user group configuration layer, and a service-specific configuration layer, wherein the basic configuration layer stores general check-in rules, the user group configuration layer associates service tags with differentiated configurations, and the service-specific configuration layer binds the identification of a target system and regionalization strategies;

[0103] The core configuration items are stored in the database according to the hierarchy, and a mapping relationship index of user attribute information and each configuration item is established, to obtain the configuration database.

[0104] In a possible implementation, the determining module 302 is specifically configured to:

[0105] Based on the matching between the service tag and the user group configuration layer, the differentiated configuration of the target user is obtained;

[0106] Based on the matching between the identification of the target system and the service-specific configuration layer, the regionalization strategy of the target user is obtained;

[0107] The differentiated configuration and the regionalization strategy are matched with the basic configuration layer, to obtain the check-in period configuration, the strategy of the check-in task, and the strategy of obtaining incentives of the target user.

[0108] In a possible implementation, the obtaining module 301 is specifically configured to:

[0109] When it is detected that the target user triggers the check-in function entry, a user information obtaining request is generated, and the user information obtaining request includes token information of a current login state of the target user;

[0110] The user information obtaining request is sent to a user center database, and an identity bound with the token information is obtained;

[0111] Based on the identity, the identification of the target system registered by the target user is extracted from a service system database;

[0112] Based on the identity, the service behavior data of the target user in a preset period is obtained;

[0113] The service behavior data is input into a preset algorithm, to obtain the service tag of the target user;

[0114] Based on the identity, the identification of the target system, and the service tag, the user attribute information of the target user is determined.

[0115] The check-in task view configuration apparatus provided in this embodiment can execute the method provided in the method embodiments, and has similar implementation principles and technical effects, which will not be described here in detail.

[0116] Figure 4 A structural schematic diagram of an electronic device provided in this embodiment is shown in FIG. 1. Figure 4As shown, the electronic device 40 provided by the embodiment includes at least one processor 401 and a memory 402. Optionally, the device 40 further includes a communication component 403. Wherein, the processor 401, the memory 402 and the communication component 403 are connected through a bus.

[0117] In the process of implementation, the at least one processor 401 executes the computer execution instructions stored in the memory 402, so that the at least one processor 401 executes the above-mentioned method.

[0118] The specific implementation process of the processor 401 can refer to the above-mentioned method embodiment, which has similar implementation principles and technical effects, and will not be described here in detail.

[0119] In the above-mentioned embodiment, it should be understood that the processor can be a central processing unit (English: Central Processing Unit, for short: CPU), and can also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, for short: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, for short: ASIC) and the like. The general-purpose processor can be a microprocessor, or the processor can be any conventional processor, etc. The steps of the method disclosed in combination with the application can be directly embodied as the execution of the hardware processor, or executed by the combination of hardware and software modules in the processor.

[0120] The memory can contain a random access memory (Random Access Memory, RAM), and can also include a non-volatile memory (Non-volatile Memory, NVM), for example, at least one disk memory.

[0121] The bus can be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect (Peripheral Component, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, the bus in the drawings of the present application does not limit only one bus or one type of bus.

[0122] The present application also provides a computer program product, including a computer program, which is executed by the processor to realize the above-mentioned method.

[0123] The application further provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions.

[0124] The readable storage medium can be implemented by any type of volatile or nonvolatile storage devices or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0125] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0126] The division of units is only a logical function division, and in actual implementation, there can be another division mode, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0127] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on multiple network units. According to actual needs, some or all of the units can be selected to achieve the purpose of the embodiment.

[0128] In addition, the functional units in each embodiment of the application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0129] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the method of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0130] It can be understood by those skilled in the art that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0131] Finally, it should be noted that: those skilled in the art will easily think of other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application that follow the general principles of the present application and include common knowledge or conventional technical means in the art that are not disclosed in the present application, and is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the present application is only limited by the appended claims.

Claims

1. A method for configuring a check-in task view, characterized in that, include: Obtain user attribute information of the target user, the user attribute information including the user's identity identifier, the identifier of the target system registered by the user, and the business tag corresponding to the user in the target system; Based on the identifier of the target system and the business tag, determine the business requirement information of the target system; Based on the preset configuration database and the business requirement information, determine the check-in period configuration, check-in task strategy, and incentive strategy for obtaining rewards after completing the check-in corresponding to the user attribute information. Based on the check-in cycle configuration, the check-in task strategy, and the incentive acquisition strategy, a check-in task view for the target user is determined. The check-in task view is used to display the check-in tasks associated with the user and the incentive information corresponding to the check-in tasks.

2. The method according to claim 1, characterized in that, The step of determining the check-in task view for the target user based on the check-in period configuration, the check-in task strategy, and the incentive acquisition strategy includes: Obtain a preset bitmap marker, which is used to represent the check-in status of the target user; The check-in period configuration, the check-in task strategy, and the incentive acquisition strategy are combined with the bitmap markers to obtain the check-in task view of the target user.

3. The method according to claim 2, characterized in that, Also includes: Receive the signature replacement request from the target user; Based on the aforementioned request for supplementary signature, determine the supplementary signature timestamp; Update the bitmap marker in the sign-in task view based on the sign-in timestamp.

4. The method according to claim 1, characterized in that, Also includes: Collect multi-dimensional configuration requirement information, including check-in scenario requirements at the business line level, rights and benefits configuration requirements at the user level, and activity rule requirements at the regional level. The multi-dimensional configuration requirement information is structured and parsed to extract the core configuration items; Construct a hierarchical structure for the configuration database, which includes a basic configuration layer, a user group configuration layer, and a business-specific configuration layer. The basic configuration layer stores general check-in rules, the user group configuration layer associates business tags with differentiated configurations, and the business-specific configuration layer binds the identifier and regionalization strategy of the target system. The core configuration items are stored in the database according to the hierarchical structure, and an index is established to map user attribute information to each configuration item, thus obtaining the configuration database.

5. The method according to claim 4, characterized in that, The process of determining the check-in period configuration, check-in task strategy, and incentive acquisition strategy corresponding to the user attribute information based on a preset configuration database includes: Based on the matching of the business tags with the user grouping configuration layer, the differentiated configuration of the target user is obtained; Based on the matching of the target system's identifier with the business-specific configuration layer, the regionalization strategy for the target user is obtained. By matching the differentiated configuration and the regionalization strategy with the basic configuration layer, the target user's check-in cycle configuration, check-in task strategy, and incentive acquisition strategy are obtained.

6. The method according to claim 1, characterized in that, The process of obtaining the target user's user attribute information includes: When the system detects that a target user has triggered the check-in function entry, a user information retrieval request is generated. The user information retrieval request includes the token information of the target user's current login state. The user information retrieval request is sent to the user center database to obtain the identity identifier bound to the token information; Based on the identity identifier, extract the identifier of the target system registered by the target user from the business system database; Based on the identity identifier, obtain the target user's business behavior data within a preset period; The business behavior data is input into a preset algorithm to obtain the business tags of the target user; Based on the identity identifier, the identifier of the target system, and the business tag, the user attribute information of the target user is determined.

7. A check-in task view configuration device, characterized in that, include: The acquisition module is used to acquire user attribute information of the target user, including the user's identity identifier, the identifier of the target system to which the user is registered, and the business tag corresponding to the user in the target system. The determination module is used to determine the business requirement information of the target system based on the identifier of the target system and the business tag; The determining module is also used to determine, based on a preset configuration database and the business requirement information, the check-in period configuration, the check-in task strategy, and the incentive strategy for completing the check-in. The configuration module is used to determine the check-in task view of the target user based on the check-in cycle configuration, the check-in task strategy, and the incentive acquisition strategy. The check-in task view is used to display the check-in tasks associated with the user and the incentive information corresponding to the check-in tasks.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images