CN112508658A - Data processing method and device - Google Patents
Data processing method and device Download PDFInfo
- Publication number
- CN112508658A CN112508658A CN202110139157.2A CN202110139157A CN112508658A CN 112508658 A CN112508658 A CN 112508658A CN 202110139157 A CN202110139157 A CN 202110139157A CN 112508658 A CN112508658 A CN 112508658A
- Authority
- CN
- China
- Prior art keywords
- customer data
- user
- data component
- client
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0641—Shopping interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9537—Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0623—Item investigation
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a data processing method and equipment, comprising the following steps: in response to a trigger instruction of a target entrance, loading a target live broadcast room page associated with the target entrance, wherein the target live broadcast room page displays a client data component associated with the target live broadcast room, and the client data component is used for triggering and displaying a reservation page for receiving client data; detecting and triggering the customer data component, displaying the reservation page, receiving user behavior information, and associating the customer data corresponding to the user behavior information with the customer data component; providing customer data associated with the customer data component to an entity object associated with the customer data component. By adopting the method, the problem of long client data acquisition link of the live broadcast room is solved.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a data processing method and device.
Background
With the development of the internet live broadcast industry, the client data conversion rate of the live broadcast room is higher and higher. Therefore, obtaining customer data through a live broadcast room has become an important commodity promotion mode.
The existing live broadcast room client data acquisition link is generally: selling commodities at low price in a live broadcast room, placing an order for the commodities sold at low price in the live broadcast process when a user enters the live broadcast room, adding customer data collection in an order placing link of the user to obtain customer data, and guiding to a commodity detail page to fill in a mobile phone number. Thus, the live room customer data acquisition link is long and the user is charged for purchase, potentially losing a portion of the potential users.
Therefore, how to provide a shorter live room client data acquisition link is a problem to be solved.
Disclosure of Invention
The data processing method provided by the embodiment of the application solves the problem that a client data acquisition link of a live broadcast room is long.
An embodiment of the present application provides a data processing method, including: in response to a trigger instruction of a target entrance, loading a target live broadcast room page associated with the target entrance, wherein the target live broadcast room page displays a client data component associated with the target live broadcast room, and the client data component is used for triggering and displaying a reservation page for receiving client data; detecting and triggering the customer data component, displaying the reservation page, receiving user behavior information, and associating the customer data corresponding to the user behavior information with the customer data component; providing customer data associated with the customer data component to an entity object associated with the customer data component.
Optionally, the client data component is associated with a virtual resource available to a user; the method further comprises the following steps: associating the virtual resource with a user that triggered the customer data component based on the user behavior information; and checking and selling the virtual resource in an object transaction link of the entity object.
Optionally, before associating the customer data corresponding to the user behavior information with the customer data component, the method includes: detecting whether a user triggering the customer data component has picked up a virtual resource associated with the customer data component; if yes, prompting that the virtual resource is acquired; otherwise, the virtual resource is associated with the user that triggered the customer data component.
Optionally, the client data component is one of customized live broadcast components generated based on configuration information provided by the entity object; the configuration information comprises any of the following information corresponding to the customer data component: the method comprises the steps of reserving activity identification information, reserving activity rules, display information of a client data component on a target live broadcast room page, display information of a reserving page and a distribution mode of client data.
Optionally, the receiving the user behavior information and associating the customer data corresponding to the user behavior information with the customer data component include: if the user triggering the client data assembly is a logged-in user, client data corresponding to the user is obtained according to the login information of the user, and the client data is associated with the client data assembly; otherwise, receiving customer data input by the user, and associating the customer data with the customer data component.
Optionally, the client data component is selected from a plurality of client data components associated with the entity object for the anchor of the target live broadcast room and is added to the component of the target live broadcast room.
Optionally, the providing the customer data associated with the customer data component to the entity object associated with the customer data component includes: providing the customer data to the store selected by the entity object for the customer data component; or, providing the customer data to stores that match the geographic location of the user that triggered the customer data component, wherein the providing the customer data to stores that match the geographic location of the user that triggered the customer data component comprises: acquiring the geographical position of the user, and inquiring a store which is associated with the entity object and has a distance between the entity object and the geographical position of the user meeting a preset distance condition according to the geographical position of the user; providing the customer data to the queried store.
Optionally, the method further includes: acquiring client information corresponding to the target entry; storing the client information as auxiliary information in association with the client data; after the customer data and the auxiliary information thereof are provided for the selected store or the inquired store, sending a user notification message to a user corresponding to the customer data; sending store customer data notification messages to customer data processing resources of the selected stores or the inquired stores in a preset time period; and updating the processing state of the client data according to the processing behavior of the client data processing resource.
An embodiment of the present application further provides an electronic device, including: a memory, and a processor; the memory is used for storing a computer program, and the computer program is executed by the processor to execute the method provided by the embodiment of the application.
The embodiment of the present application further provides a storage device, in which a computer program is stored, and the computer program is executed by the processor to perform the method provided in the embodiment of the present application.
Compared with the prior art, the method has the following advantages:
according to the resource processing method and the resource processing equipment provided by the embodiment of the application, a target live broadcast room page associated with a target entrance is loaded, the target live broadcast room page displays a client data component associated with the target live broadcast room, and the client data component is used for triggering and displaying a reservation page for receiving client data; detecting and triggering the client data component, and displaying the reservation page; receiving user behavior information, and associating client data corresponding to the user behavior information with the client data component; providing customer data associated with the customer data component to an entity object associated with the customer data component. Direct guide to the reservation page through customer data subassembly, the link guide user that can be shorter provides customer data, make the operation that the user kept customer data more convenient, thereby avoid the part to have the user who keeps customer data intention to give up the information of keeping because complex operation, can improve the acquisition efficiency and the quantity of the customer data who acquires through the live broadcast room, furthermore, the customer data distribution that acquires through the live broadcast room reaches the store, the store can turn into actual user with the user who provides customer data, enlarge the user scope that the trade company can touch and promote user conversion rate.
Drawings
Fig. 1 is a schematic diagram of a system environment of a client data providing function in a live broadcast room according to an embodiment of the present application.
Fig. 2 is a flowchart of a data processing method according to a first embodiment of the present application.
Fig. 3 is an interaction diagram of a live broadcast associated client data component provided in the first embodiment of the present application.
Fig. 4 is a flowchart of live-room user retention of client data according to the first embodiment of the present application.
Fig. 5 is a schematic diagram of a data processing apparatus according to a second embodiment of the present application.
Fig. 6 is a schematic diagram of an electronic device provided herein.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The embodiment of the application provides a resource processing method and device, electronic equipment and storage equipment. The following examples are individually set forth.
For ease of understanding, a system environment in which the method provided by the embodiments of the present application is applied is first presented. Referring to FIG. 1, a system environment is shown that includes: entity object client 101, client data system 102, anchor background 103, anchor client 104 and live broadcast room 105.
The entity object is an entity that provides the object, and may be a merchant. A physical object may have associated with it a plurality of stores, such as a chain of stores. The entity object client 101 is a client loaded on the entity object electronic device and used for editing and managing store information in the customer data system by the entity object. The entity object can configure a live room client data component (hereinafter referred to as a client data component) in the client data system through the entity object client. The method comprises the following steps: the name of the subscription activity of the client data component, the rules of the subscription activity, description information of the subscription activity, the distribution mode of the client data associated with the client data component, etc. are configured.
The client data system 102 generates a client data component according to configuration information provided by the entity object client, and/or the object client data component is edited, provides the client data component which can be selected by the anchor (or the live anchor) to the anchor background, and acquires the client data collected by the anchor background through the client data component; and displaying the client data on the entity object client, and receiving the processing and state updating of the client data by the entity object. For example, a component identification for the customer data component is generated, and the customer data component is populated with configuration information provided by the entity object. As another example, customer data associated with the customer data component is obtained and the data volume of the customer data is counted; the processing state of the customer data associated with the customer data component is updated based on the user visit information. For another example, a piece of customer data is set to be in the store-reached state when the corresponding user visits the store of the entity object according to the reservation information. For another example, the entity object client may expose the amount of data of customer data that the customer data component has associated with, as well as the amount of data that has arrived at the store.
The anchor background 103 acquires a client data component which can be selected by the anchor from a client data system, outputs the information of the client data component and displays the information on the anchor client, and associates a target client data component selected by the anchor with a live broadcast room; displaying a live broadcast room page associated with a target client data assembly on a live broadcast client, wherein the file information and/or the bullet layer information of the target client data assembly can be displayed on the live broadcast client; customer data corresponding to the user and provided by the target customer data component in the live broadcast room are received, and the customer data are provided to a customer data system and/or a store distributed to entity objects.
The anchor client 104 refers to a client that is loaded on the anchor electronic device and is used by the anchor to interactively configure the live information. The anchor can be a merchant self-broadcasting or a landlord agent broadcasting, and a target customer data component is selected from the displayed information of the customer data components through an anchor client and added to a live broadcasting room. Specifically, the anchor binds the target client data component to the live broadcast room at the anchor client via the component identifier.
The live broadcast room 105 refers to a client that is loaded on the electronic device of the user and is used for the user to watch live broadcasts and perform information interaction with the anchor and/or anchor background. The live broadcast room page is displayed on the user electronic equipment, and the target client data component added by the anchor is displayed on the live broadcast room page. When a user checks a target client component in a live broadcast room, the live broadcast room detects that the user triggers the target client data component and displays an appointment page corresponding to the target client data component; and detecting the reservation information of the user confirmation reservation page, acquiring client data corresponding to the user, providing the client data to a client data system, and finally precipitating the client data to the entity object through the client data system.
In the system environment, the linkage pull-through is carried out on a merchant end (an entity object client and a customer data system), an anchor end (an anchor client and an anchor background) and a live broadcast room (a user end), so that a guide link for providing customer data by a user is shortened. A merchant adds a live broadcast room customer data component at a merchant end; the anchor binds the client data component to the live broadcast room through the component identification at the anchor end; the user views the customer data component in the live broadcast room and provides customer data, and the customer data is finally deposited at the merchant end.
According to the data processing method provided by the embodiment of the application, a target live broadcast room page is loaded, and a client data component associated with the target live broadcast room is displayed; detecting and triggering the client data component, and displaying the reservation page; associating customer data with the customer data component based on user behavior information; providing customer data associated with the customer data component to an entity object associated with the customer data component. The client data component is directly guided to the reservation page, so that a guide link for providing client data by a user is shortened, and the reachable user range of the entity object is expanded.
The data processing method provided in the first embodiment of the present application is described below with reference to fig. 2 to 4. The data processing method shown in fig. 1 includes: step S201 to step S203.
Step S201, responding to a trigger instruction of a target entrance, loading a target live broadcast room page related to the target entrance, wherein the target live broadcast room page displays a client data component related to the target live broadcast room, and the client data component is used for triggering and displaying a reservation page used for receiving client data.
In this embodiment, a user checks a client data component bound with a target live broadcast room in the target live broadcast room, and retains client data of the user in subsequent steps. Wherein the client data component initiates a created component for the entity object, and the anchor can bind the selected client data component to the live broadcast room through the component identification, thereby enabling a user to view the client data component in the live broadcast room. The reservation page is a popup layer page displayed after the user triggers the client data component in the target live broadcast room. Specifically, the second-level page of the live broadcast room page may be the reserved page corresponding to the address associated with the jump-to client data component.
In this embodiment, the client data component is one of customized live broadcast components generated based on configuration information provided by an entity object; the configuration information comprises any of the following information corresponding to the customer data component: the method comprises the steps of reserving activity identification information, reserving activity rule information, display information of a client data component on a target live broadcast room page, display information of a reserving page and a distribution mode of client data. For example, the reservation campaign identification information may be a campaign name of the user-to-store reservation campaign. The reservation activity rules may include information such as a limit on the number of times the user engages in the activity, the value of the reservation activity coupon, and coupon use restrictions or coupons to use by text message. The display information of the client data component on the target live broadcast room page can be the title content of the client data component and the like. The display information of the reservation page can comprise reservation activity rules, reservation activity description information and other contents. The distribution mode of the client data includes but is not limited to: and distributing the customer data to a store designated by the entity object, or automatically distributing the customer data to a store of the entity object, such as a store which is close to the store meeting the preset condition at the geographical position of the user, for example. In configuring the customer data component, further comprising generating a user retrievable virtual resource associated with the customer data component. For example, the user saves the customer data and then automatically issues the redemption ticket associated with the customer data component to the user account, and the user can use the redemption ticket after arriving at a store according to the reservation information corresponding to the reservation page.
In this embodiment, the client data component is a component selected from a plurality of client data components associated with the entity object for the anchor of the target live broadcast room and added to the target live broadcast room. In practice, the entity object initiates generation of one or more customer data components, each having a component identification. The anchor may select a customer data component from the one or more customer data components to add to the target live room. Specifically, the anchor initiates live broadcast, a plurality of displayed customer data assemblies are checked through the interactive panel, the customer data assemblies are selected from the customer data assemblies, information corresponding to the selected customer data assemblies is previewed, the adding button is triggered to associate the selected customer data assemblies with a live broadcast room where the anchor currently carries out live broadcast, and the customer data assemblies are displayed on a live broadcast room page after the adding is successful.
Referring to fig. 3, the interactive process of the live room associated client data component shown in the figure includes: s301, adding a customer data component which can be used in a live broadcast room at a merchant end by a merchant. And the merchant terminal is a client terminal for managing customer data for the entity object. And displaying and setting a client data component entrance of the live broadcast room in a reservation management page of the client, and triggering and displaying a client data component list for the live broadcast room through the entrance. The list of client data components may be presented in particular in the order of creation or modification. S301-1 presents information for one or more customer data components in a customer data component list page, including but not limited to the following: the method comprises the following steps of marking a client data component title, a name of a reserved activity corresponding to the client data component, a component identification of a generated client data component, description information of the reserved activity, data volume of current client data associated with the client data component, and data volume of client data processed to be arrived at a store by a merchant. An example of a customer data component list page is shown. S301-2, configuring a client data component displayed in the live broadcast room in the newly-built client data component page, and using the client data component as the information of the reservation page displayed in the popup layer after being triggered. For example, a component title and an event name of a customer data component displayed on a configuration reservation page, description information of a reservation event, document information of a button related to the reservation page, value information corresponding to the reservation event, a customer data distribution method, and the like. Wherein, the distribution mode includes: to a merchant designated store or automatically to a store closer to the user. An example of a new customer data component is shown. And the customer data system generates a redemption ticket corresponding to the customer data component according to the value information corresponding to the reservation activity configured by the merchant. The redemption ticket may be issued to the user account after the user retains the customer data. For example: and if the user selects to distribute to the shop appointed by the merchant, jumping to the selectable shop list page, and displaying the shops with the opened reservation to the shop. The merchant may perform the off-shelf processing on the configured and generated customer data components, and the off-shelf customer data components are grayed out in the displayed customer data component list and display the "off-shelf" status for the customer data components. The pages in the figures are schematic illustrations only and are not intended to limit the specific implementations. S302, the anchor binds the selected data component with the live broadcast room through the component identification at the anchor end. And after the anchor initiates the live broadcast, the optional client data component list is obtained through a component entrance provided by the anchor background, and the client data component is selected from the optional client data component list and added to the live broadcast room. And the anchor background realizes access in a mode of embedding an iframe into a component. The anchor can also set the activity reservation information associated with the client data assembly through the background, thereby realizing the self-setting of the activity reservation page and embedding the page into the anchor background after deployment. The embedded client data component can be used as a user reservation entrance, can be developed and realized according to the development specification of the interactive component of the live broadcast room rax during realization, and realizes the linkage of the reservation entrance and the anchor background by utilizing the message pushing mechanism of the component.
Step S202, detecting and triggering the customer data assembly, displaying the reservation page, receiving user behavior information, and associating the customer data corresponding to the user behavior information with the customer data assembly.
In this embodiment, the user views the components and retains the client data in the live broadcast room. The customer data may be a contact means such as a telephone number. The receiving user behavior information and associating customer data corresponding to the user behavior information with the customer data component includes: if the user triggering the client data assembly is a logged-in user, client data corresponding to the user is obtained according to the login information of the user, and the client data is associated with the client data assembly; otherwise, receiving customer data input by the user, and associating the customer data with the customer data component. The opportunity for a user to authorize the acquisition of his customer data triggered by the customer data component is not constrained. In actual implementation, the client data component can be triggered to prompt the user whether the user authorization can retain the client data of the user, and the user authorization can be confirmed to retain the client data of the user after the client data component associated with the target live broadcast room is triggered when the user logs in the page of the target live broadcast room. Further, the customer data component associates virtual resources available to a user; the method further comprises the following steps: associating the virtual resource with a user that triggered the customer data component based on the user behavior information; and checking and selling the virtual resource in an object transaction link of the entity object. In implementation, before associating the customer data corresponding to the user behavior information with the customer data component, the method includes: detecting whether a user triggering the customer data component has picked up a virtual resource associated with the customer data component; if yes, prompting that the virtual resource is acquired; otherwise, the virtual resource is associated with the user that triggered the customer data component. Thereby limiting the number of times the user draws virtual resources.
In this embodiment, the method further includes: acquiring client information corresponding to the target entry; and storing the client information as auxiliary information in association with the client data. That is, the source of the customer data is stored as auxiliary information. For example, a user enters a live broadcast room through an application a, the live broadcast room is associated with a client data component B, the user triggers the client data component B to enter a reservation page, client data corresponding to the user can be saved through the reservation page under the permission of the user, and information of the application a is recorded in the client data. If the user is a logged-in user, backfilling user information through a form of a live broadcast room page; and if the user is a non-login user, the user inputs user information on the reservation page. And taking the backfilled user information or the input user information as basic customer data, adding the information of the application A as auxiliary information to obtain customer data retained by the user, and associating the retained customer data with a customer data component B.
Referring to fig. 4, the flow of live-room user retention of client data shown in the figure includes: s401, the user triggers the client data component. S402, judging whether the user draws the virtual resource, if yes, prompting repeated drawing, and returning to the live broadcast page. And S403, automatically backfilling the corresponding customer data of the user or customer data input by the user, such as contact information, in the form page. S404, judging whether the geographical area where the user is located has stores of merchants, and if yes, prompting store information; otherwise, no store is prompted. The process proceeds to S405. S405, the user draws the virtual resource associated with the customer data component. S406, judging whether the picking is successful or not, and carrying out corresponding prompt according to the picking result. For example, each UID (user ID) account number participates in a reservation event through a certain customer data component within a preset time (such as within one day), picks up a redemption ticket associated with the certain customer data component, and retains a piece of customer data.
Step S203, providing the customer data associated with the customer data component to the entity object associated with the customer data component.
In this embodiment, the providing the customer data associated with the customer data component to the entity object associated with the customer data component includes: providing the customer data to the store selected by the entity object for the customer data component; or, providing the customer data to stores that match the geographic location of the user that triggered the customer data component, wherein the providing the customer data to stores that match the geographic location of the user that triggered the customer data component comprises: acquiring the geographical position of the user, and inquiring a store which is associated with the entity object and has a distance between the entity object and the geographical position of the user meeting a preset distance condition according to the geographical position of the user; providing the customer data to the queried store. In implementation, data distribution is performed according to a client data distribution mode configured by the entity object for the client data component. If the distribution mode is to distribute the customer data to the appointed stores, lossless distribution is carried out according to the appointed stores, and the appointed stores need to be verified to open the reservation to the stores before distribution. If the distribution mode is near automatic distribution, the geographical position, such as longitude and latitude, of the user is obtained from the live broadcast information under the condition that the user allows, stores which are close to the user and reserved to the store are screened out, and the customer data are distributed to the screened stores. After the customer data is distributed to the stores, the stores further perform customer relationship maintenance and management work according to the customer data, for example, contact the corresponding users according to the contact ways included in the customer data, confirm the time when the users can arrive at the stores or exchange goods or services by using the received virtual resources, time and the like, and thus convert potential users retaining the customer data into actual users.
In this embodiment, after the user retains the client data, notification messages are respectively sent to the entity object and the user. The method specifically comprises the following steps: acquiring client information corresponding to the target entry; storing the client information as auxiliary information in association with the client data; after the customer data and the auxiliary information thereof are provided for the selected store or the inquired store, sending a user notification message to a user corresponding to the customer data; sending store customer data notification messages to customer data processing resources of the selected stores or the inquired stores in a preset time period; and updating the processing state of the client data according to the processing behavior of the client data processing resource. For example, the merchant sends a short message to the store manager to notify, and sends a notification within a preset time period according to the customer data generated within a certain time period. For another example, the user side sends a short message to the user after the customer data retained by the user is successfully distributed to the store. Wherein the customer data includes, but is not limited to, the following: the time of the customer data being distributed to the store, the contact information retained by the user, and the client information of the customer data being watched and retained by the user. The client data obtained by the entity object includes but is not limited to the following: the method comprises the steps that a user reserves client information used by client data, the client data reserved by the user and appointment activity name information corresponding to a client data component for triggering and acquiring the client data.
The scheme that this embodiment provided leaves customer data to live broadcasting room with leading, and does not need the user to pay the transaction, has simplified customer data's the link of reserving for user's operation is more convenient, can attract the user to fill in customer data and go to the shop according to the reservation information line, thereby improves the efficiency of reserving customer data and the user quantity of reserving the information, has enlarged the user scope that the trade company can reach.
It should be noted that, in the case of no conflict, the features given in this embodiment and other embodiments of the present application may be combined with each other, and the steps S201 and S202 or similar terms do not limit the steps to be executed sequentially.
The method provided by the embodiment is explained so far, and the method includes loading a target live broadcast room page associated with a target entrance, wherein the target live broadcast room page displays a client data component associated with the target live broadcast room, and the client data component is used for triggering and displaying a reservation page for receiving client data; detecting and triggering the client data component, and displaying the reservation page; receiving user behavior information, and associating client data corresponding to the user behavior information with the client data component; providing customer data associated with the customer data component to an entity object associated with the customer data component. The customer data component is directly guided to the reservation page, and the user can be guided to provide customer data through a short link, so that the user providing the customer data can be further converted into an actual user, the user range reachable by a merchant is expanded, and the user conversion rate is improved.
A second embodiment corresponds to the first embodiment, and a second embodiment of the present application provides a data processing apparatus. The device is described below with reference to fig. 5. The data processing apparatus shown in fig. 5 includes:
a loading unit 501, configured to, in response to a trigger instruction for a target entry, load a target live broadcast room page associated with the target entry, where the target live broadcast room page shows a client data component associated with the target live broadcast room, and the client data component is used to trigger and show a reservation page for receiving client data;
a data retention unit 502, configured to detect that the client data component is triggered, display the reservation page, receive user behavior information, and associate client data corresponding to the user behavior information with the client data component;
a data distribution unit 503, configured to provide the customer data associated with the customer data component to the entity object associated with the customer data component.
Optionally, the client data component is associated with a virtual resource available to a user; the apparatus further comprises a virtual resource unit to: associating the virtual resource with a user that triggered the customer data component based on the user behavior information; and checking and selling the virtual resource in an object transaction link of the entity object.
Optionally, the virtual resource unit is specifically configured to: detecting whether a user triggering the customer data component has picked up a virtual resource associated with the customer data component before associating customer data corresponding to the user behavior information with the customer data component; if yes, prompting that the virtual resource is acquired; otherwise, the virtual resource is associated with the user that triggered the customer data component.
Optionally, the client data component is one of customized live broadcast components generated based on configuration information provided by the entity object; the configuration information comprises any of the following information corresponding to the customer data component: the method comprises the steps of reserving activity identification information, reserving activity rules, display information of a client data component on a target live broadcast room page, display information of a reserving page and a distribution mode of client data.
Optionally, the data retention unit 502 is specifically configured to: if the user triggering the client data assembly is a logged-in user, client data corresponding to the user is obtained according to the login information of the user, and the client data is associated with the client data assembly; otherwise, receiving customer data input by the user, and associating the customer data with the customer data component.
Optionally, the client data component is selected from a plurality of client data components associated with the entity object for the anchor of the target live broadcast room and is added to the component of the target live broadcast room.
Optionally, the data distribution unit 503 is specifically configured to: providing the customer data to the store selected by the entity object for the customer data component; or, providing the customer data to stores that match the geographic location of the user that triggered the customer data component, wherein the providing the customer data to stores that match the geographic location of the user that triggered the customer data component comprises: acquiring the geographical position of the user, and inquiring a store which is associated with the entity object and has a distance between the entity object and the geographical position of the user meeting a preset distance condition according to the geographical position of the user; providing the customer data to the queried store.
Optionally, the data retention unit 502 is specifically configured to: acquiring client information corresponding to the target entry; storing the client information as auxiliary information in association with the client data; after the customer data and the auxiliary information thereof are provided for the selected store or the inquired store, sending a user notification message to a user corresponding to the customer data; the data distribution unit 503 is specifically configured to: sending store customer data notification messages to customer data processing resources of the selected stores or the inquired stores in a preset time period; and updating the processing state of the client data according to the processing behavior of the client data processing resource.
Based on the above embodiments, a third embodiment of the present application provides an electronic device, and please refer to the corresponding description of the above embodiments for related parts. Referring to fig. 6, the electronic device shown in fig. 6 includes a memory 601 and a processor 602. The memory stores a computer program, and the computer program is executed by the processor to execute the method provided by the embodiment of the application.
Based on the foregoing embodiments, a fourth embodiment of the present application provides a storage device, and please refer to the corresponding description of the foregoing embodiments for related parts. The schematic diagram of the storage device is similar to fig. 6. The storage device stores a computer program, and the computer program is executed by the processor to execute the method provided by the embodiment of the application.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
Claims (10)
1. A data processing method, comprising:
in response to a trigger instruction of a target entrance, loading a target live broadcast room page associated with the target entrance, wherein the target live broadcast room page displays a client data component associated with the target live broadcast room, and the client data component is used for triggering and displaying a reservation page for receiving client data;
detecting and triggering the customer data component, displaying the reservation page, receiving user behavior information, and associating the customer data corresponding to the user behavior information with the customer data component;
providing customer data associated with the customer data component to an entity object associated with the customer data component.
2. The method of claim 1, wherein the customer data component is associated with a virtual resource retrievable by a user;
the method further comprises the following steps:
associating the virtual resource with a user that triggered the customer data component based on the user behavior information;
and checking and selling the virtual resource in an object transaction link of the entity object.
3. The method of claim 2, prior to associating customer data corresponding to the user behavior information with the customer data component, comprising:
detecting whether a user triggering the customer data component has picked up a virtual resource associated with the customer data component;
if yes, prompting that the virtual resource is acquired;
otherwise, the virtual resource is associated with the user that triggered the customer data component.
4. The method of claim 1, wherein the customer data component is one of customized live components generated based on configuration information provided by an entity object;
the configuration information comprises any of the following information corresponding to the customer data component: the method comprises the steps of reserving activity identification information, reserving activity rules, display information of a client data component on a target live broadcast room page, display information of a reserving page and a distribution mode of client data.
5. The method of claim 1, wherein receiving user behavior information, associating customer data corresponding to the user behavior information with the customer data component, comprises:
if the user triggering the client data assembly is a logged-in user, client data corresponding to the user is obtained according to the login information of the user, and the client data is associated with the client data assembly;
otherwise, receiving customer data input by the user, and associating the customer data with the customer data component.
6. The method of claim 1, wherein the customer data component is selected from a plurality of customer data components associated with the entity object for the anchor of the target live broadcast and added to a component of the target live broadcast.
7. The method of claim 1, wherein providing customer data associated with the customer data component to an entity object associated with the customer data component comprises:
providing the customer data to the store selected by the entity object for the customer data component; or the like, or, alternatively,
providing the customer data to stores that match the geographic location of the user that triggered the customer data component, wherein the providing the customer data to stores that match the geographic location of the user that triggered the customer data component comprises:
acquiring the geographical position of the user, and inquiring a store which is associated with the entity object and has a distance between the entity object and the geographical position of the user meeting a preset distance condition according to the geographical position of the user;
providing the customer data to the queried store.
8. The method of claim 7, further comprising:
acquiring client information corresponding to the target entry;
storing the client information as auxiliary information in association with the client data;
after the customer data and the auxiliary information thereof are provided for the selected store or the inquired store, sending a user notification message to a user corresponding to the customer data;
sending store customer data notification messages to customer data processing resources of the selected stores or the inquired stores in a preset time period;
and updating the processing state of the client data according to the processing behavior of the client data processing resource.
9. An electronic device, comprising:
a memory, and a processor; the memory is adapted to store a computer program which, when executed by the processor, performs the method of any one of claims 1 to 8.
10. A storage device, characterized in that a computer program is stored which, when being executed by a processor, performs the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110139157.2A CN112508658A (en) | 2021-02-02 | 2021-02-02 | Data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110139157.2A CN112508658A (en) | 2021-02-02 | 2021-02-02 | Data processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112508658A true CN112508658A (en) | 2021-03-16 |
Family
ID=74952868
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110139157.2A Pending CN112508658A (en) | 2021-02-02 | 2021-02-02 | Data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112508658A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112767100A (en) * | 2021-04-07 | 2021-05-07 | 浙江口碑网络技术有限公司 | Page display method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106604048A (en) * | 2016-12-15 | 2017-04-26 | 深圳市智联宝生态科技有限公司 | Direct broadcasting method and system with shopping module embedded in direct broadcasting room |
| CN106791904A (en) * | 2016-12-29 | 2017-05-31 | 广州华多网络科技有限公司 | Live purchase method and device |
| CN111192102A (en) * | 2018-11-14 | 2020-05-22 | 阿里巴巴集团控股有限公司 | Commodity object information processing method and device and electronic equipment |
| CN112153402A (en) * | 2020-09-22 | 2020-12-29 | 北京达佳互联信息技术有限公司 | Electronic resource allocation method, device, electronic equipment and storage medium |
-
2021
- 2021-02-02 CN CN202110139157.2A patent/CN112508658A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106604048A (en) * | 2016-12-15 | 2017-04-26 | 深圳市智联宝生态科技有限公司 | Direct broadcasting method and system with shopping module embedded in direct broadcasting room |
| CN106791904A (en) * | 2016-12-29 | 2017-05-31 | 广州华多网络科技有限公司 | Live purchase method and device |
| CN111192102A (en) * | 2018-11-14 | 2020-05-22 | 阿里巴巴集团控股有限公司 | Commodity object information processing method and device and electronic equipment |
| CN112153402A (en) * | 2020-09-22 | 2020-12-29 | 北京达佳互联信息技术有限公司 | Electronic resource allocation method, device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112767100A (en) * | 2021-04-07 | 2021-05-07 | 浙江口碑网络技术有限公司 | Page display method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11361047B2 (en) | Website creation system for creating websites having at least one series of directional webpages and related methods | |
| US10198764B2 (en) | System and method for message-based purchasing | |
| US20210303654A1 (en) | Website creation system for creating websites having at least one series of directional webpages and related methods | |
| CN104717342B (en) | A kind of method and device waking up client application based on short message | |
| JP5161300B2 (en) | Web-based automated invoice analysis method | |
| US20090259562A1 (en) | Method and apparatus for providing gift by using communication network and system including the apparatus | |
| KR102198932B1 (en) | Membership benefit service method using electronic receipt, membership benefit service apparatus and system therefor | |
| US20180210964A1 (en) | Third-party database interaction to provision users | |
| CN111898780B (en) | Commission returning method and device, electronic equipment and storage medium | |
| CN112948521A (en) | Object handling method and device | |
| CN112508658A (en) | Data processing method and device | |
| WO2008072818A1 (en) | Method of providing mobile advertisement information and apparatus for providing mobile advertisement information using the same | |
| US20120278182A1 (en) | Generating an advertisement message | |
| US20150302373A1 (en) | Method and apparatus for providing a gift using a mobile communication network and system including the apparatus | |
| KR20190021811A (en) | Method, apparatus and system for issuing an electronic receipt | |
| CN113379523A (en) | Bill generation method, device, medium and electronic equipment | |
| CN117455236A (en) | Method, device, equipment and medium for updating wind measurement grade | |
| US8364146B1 (en) | Initiation of wireless service | |
| CN112711722A (en) | Data processing and assisting method, device and storage medium | |
| RU2699059C1 (en) | Method for attracting customers to sales offices of goods and services | |
| CN114897559A (en) | Data interaction method and device based on exclusive service application | |
| CN114971808A (en) | Order fulfillment task customizing method, system, electronic equipment and storage medium | |
| KR20150056680A (en) | mobile marketing system and apparatus for business | |
| CN111324612A (en) | Storage method, system, device, equipment and storage medium of order information | |
| US20150294365A1 (en) | Systems and Methods for Creation and Transmission of Emails with Integral Advertisements via an Email Marketing System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210316 |
|
| RJ01 | Rejection of invention patent application after publication |