CN111105270A - Method and device for managing push data - Google Patents
Method and device for managing push data Download PDFInfo
- Publication number
- CN111105270A CN111105270A CN201911232206.6A CN201911232206A CN111105270A CN 111105270 A CN111105270 A CN 111105270A CN 201911232206 A CN201911232206 A CN 201911232206A CN 111105270 A CN111105270 A CN 111105270A
- Authority
- CN
- China
- Prior art keywords
- information
- data
- target data
- preset
- dimension
- 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Computational Linguistics (AREA)
- Game Theory and Decision Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application is applicable to the technical field of computers, and provides a method for managing push data, which comprises the following steps: in the embodiment of the application, historical pushing information is obtained; performing dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information; and generating target sending data based on the data corresponding to the preset dimension information and a preset statistical strategy. According to the method, the sending data can be counted and summarized in real time according to the preset dimension information, the target sending data is generated, the business personnel do not need to spend a large amount of time for summarizing the pushing information every day, resources are saved, and the processing efficiency is improved.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a method and a device for managing push data.
Background
In the process of telemarketing promotion, the telemarketing system distributes the obtained promotion list to the seat, and seat personnel promote commodities by making a call and can obtain historical push information. Business staff can analyze the requirements of users, product popularization conditions and the like according to historical push information. However, in the existing electricity marketing system, it takes a lot of time for business personnel to gather the pushed information every day, which consumes resources and is not beneficial to improving the processing efficiency.
Disclosure of Invention
The embodiment of the application provides a method and a device for managing push data, and the method and the device can solve the problems that in an existing electricity marketing system, business personnel need to spend a large amount of time to gather push information every day, resources are consumed, and the promotion efficiency is not improved.
In a first aspect, an embodiment of the present application provides a method for managing push data, including:
acquiring historical pushing information; the historical push information comprises client list information and a push record corresponding to the client list information;
performing dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information;
and generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
Further, the generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy includes:
generating a data table based on the data corresponding to each piece of preset dimension information;
screening a target data table from the data tables based on a preset statistical strategy, and establishing an association relation between the target data tables;
and obtaining target data based on the incidence relation between the target data table and the target data table.
Further, after the generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy, the method further includes:
when a query request is detected, a query result is obtained from the target data based on the query request.
Further, the query request includes a query condition;
when the query request is detected, obtaining a query result from the target data based on the query request, including:
when a query request is detected, analyzing the query request to obtain query dimension information;
acquiring a target data table corresponding to the query dimension information from the target data based on the query dimension information, and establishing an association relation between the target data tables;
and obtaining a query result based on the query condition, the target data table and the incidence relation among the target data tables.
Further, after the obtaining a query result from the target data based on the query request when the query request is detected, the method further includes:
when a query result export request is detected, an export file in a preset format is generated based on the query result, and the export file is exported.
Further, the target data comprises a client list and client information corresponding to the client list;
after the target data is generated based on the data corresponding to the preset dimension information and a preset statistical strategy, the method further includes:
and obtaining screening information of a client list, and screening the client list and the client information corresponding to the client list based on the screening information to obtain a target client list meeting the screening information and the client information corresponding to the target client list.
Further, the preset dimension information comprises one or more of a data batch dimension, a customer grade dimension, a customer warehousing time dimension, a telephone dialing condition dimension and a list condition dimension.
In a second aspect, an embodiment of the present application provides an apparatus for managing push data, including:
the first acquisition unit is used for acquiring historical push information; the historical push information comprises client list information and a push record corresponding to the client list information;
the first processing unit is used for carrying out dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information;
and the first generating unit is used for generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
Further, the first generating unit is specifically configured to:
generating a data table based on the data corresponding to each piece of preset dimension information;
screening a target data table from the data tables based on a preset statistical strategy, and establishing an association relation between the target data tables;
and obtaining target data based on the incidence relation between the target data table and the target data table.
Further, the apparatus for managing push data further includes:
and the second acquisition unit is used for acquiring an inquiry result from the target data based on the inquiry request when the inquiry request is detected.
Further, the query request includes a query condition;
the second obtaining unit is specifically configured to:
when a query request is detected, analyzing the query request to obtain query dimension information;
acquiring a target data table corresponding to the query dimension information from the target data based on the query dimension information, and establishing an association relation between the target data tables;
and obtaining a query result based on the query condition, the target data table and the incidence relation among the target data tables.
Further, the apparatus for managing push data further includes:
and the second generation unit is used for generating an export file in a preset format based on the query result when the query result export request is detected, and the export file is exported.
Further, the target data comprises a client list and client information corresponding to the client list;
the apparatus for managing push data further comprises:
and the second processing unit is used for acquiring screening information of the client list, screening the client list and the client information corresponding to the client list based on the screening information, and obtaining a target client list meeting the screening information and the client information corresponding to the target client list.
Further, the preset dimension information comprises one or more of a data batch dimension, a customer grade dimension, a customer warehousing time dimension, a telephone dialing condition dimension and a list condition dimension.
In a third aspect, an embodiment of the present application provides an apparatus for managing push data, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor, when executing the computer program, implements the method for managing push data according to the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the method for managing push data according to the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product, which, when running on a device for managing push data, causes a terminal device to execute the method for managing push data according to the first aspect.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
In the embodiment of the application, historical pushing information is obtained; performing dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information; and generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy. According to the method, the sent data can be counted and summarized in real time according to the preset dimension information, the target data is generated, the business personnel do not need to spend a large amount of time for summarizing the pushed information every day, resources are saved, and the processing efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flow chart of a method for managing push data according to a first embodiment of the present application;
fig. 2 is a schematic flowchart of a refinement of S103 in a method for managing push data according to a first embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of another method for managing push data provided in a second embodiment of the present application;
fig. 4 is a schematic flowchart of a refinement of S203 in another method for managing push data provided in the second embodiment of the present application;
fig. 5 is a schematic diagram of an apparatus for managing push data according to a third embodiment of the present application;
fig. 6 is a schematic diagram of an apparatus for managing push data according to a fourth embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
Referring to fig. 1, fig. 1 is a schematic flow chart of a method for managing push data according to a first embodiment of the present application. The execution main body of the method for managing push data in this embodiment is a device having a function of managing push data, and specifically may be a device such as a mobile phone, a computer, a super mobile personal computer, a netbook, a server, and the like. The method of managing push data as shown in fig. 1 may include:
s101: acquiring historical pushing information; the historical push information comprises client list information and a push record corresponding to the client list information.
The device acquires historical push information, wherein the historical push information comprises client list information and a push record corresponding to the client list information. Specifically, the client list information and the corresponding push records thereof may be pre-stored in the device, and the device acquires the client list information and the corresponding push records thereof from the database; the device can also receive the client list information and the corresponding push records sent by other devices through the network.
The customer list information includes the name of the customer and customer information, which may include the customer's profile and contact details, for example, the customer information may include the customer's gender, occupation, phone, mailbox address, and the like. The push records may include time of historical promotion, historical promotion times, historical promotion singleton status, promotion client evaluation, and so on corresponding to each client.
S102: and carrying out dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information.
The dimension information is preset in the equipment and used for carrying out data statistics on the client list information and the corresponding push records, the preset dimension information comprises dimensions required when data are counted, and further the preset dimension information comprises data batch dimensions, client grade dimensions, client warehousing time dimensions, telephone dialing condition dimensions and single condition dimensions. When the client list information and the corresponding push records are obtained, the client list information and the corresponding push records are obtained in batches when the obtained quantity is too large, so that the management is convenient, different data batches corresponding to different client list information and the corresponding push records are obtained, and the data batch dimension is the data batch to which the client list information and the corresponding push records belong; different customers can be classified into different grades according to the customer information, for example, the customers can be graded according to the amount consumed by the customers, so that the customer grade dimensionality is the customer grade corresponding to the different customers; the dimension of the call dialing condition can correspond to the number of times of call dialing, the time length of each pass of the call, the information of the call condition and the like; the customer warehousing time dimension is the time when the relevant data of the customer enters the database of the client.
The device performs dimension splitting on the client list information and the corresponding push records based on the preset dimension information to obtain data corresponding to the preset dimension information. For example, the device performs dimension splitting on the client list information and the corresponding push records thereof based on the data batch dimension and the client grade dimension, extracts data corresponding to the data batch dimension as a first batch from the client list information and the corresponding push records thereof, and extracts data corresponding to the client grade dimension as 3 levels.
S103: and generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
The device is preset with a statistical strategy, and the preset statistical strategy is used for counting data corresponding to the preset dimension information to obtain target data. The preset statistical policy may include a data dimension included in the target data. The device acquires the target data dimension in the target data based on a preset statistical strategy, acquires data corresponding to the target data dimension from the data corresponding to the preset dimension information, and generates a target sending number. The target data can be sent to a system of business personnel, and the business personnel can perform operations such as inquiry, screening and the like based on the target data. In this embodiment, data management may be performed at intervals, that is, data is acquired at intervals and data statistics is performed to generate target data.
Further, in order to accurately generate the target data, S103 may include S1031 to S1033, as shown in fig. 2, where S1031 to S1033 are specifically as follows:
s1031: and generating a data table based on the data corresponding to each preset dimension information.
The device generates a data table based on the data corresponding to each piece of preset dimension information, wherein the data table is a table in a memory for temporarily storing the data. The device generates a data table based on the data corresponding to each piece of preset dimension information, that is, each piece of preset dimension information corresponds to one data table, and the data corresponding to the preset dimension information is stored.
S1032: and screening a target data table from the data tables based on a preset statistical strategy, and establishing an association relation between the target data tables.
The device screens out a target data table from the data table based on a preset statistical strategy, specifically, the preset statistical strategy comprises a target data dimension included in the target data, and the data table corresponding to the target data dimension is obtained from the data table and is the target data table. And after the target data tables are obtained, establishing an association relation between the target data tables according to the data corresponding to the preset dimension information. For example, the data corresponding to the preset dimension information includes an association relationship between each preset dimension, and the association relationship between the preset dimensions is an association relationship between the target data tables corresponding to the preset dimension information. When the preset dimension information comprises a client name dimension and a client consumption amount dimension, the incidence relation between the client name dimension and the client consumption amount dimension is the client consumption amount of the client corresponding to the client by the client name dimension, and the corresponding relation between the client name data table and the client consumption amount data table is established based on the incidence relation between the client name dimension and the client consumption amount dimension.
S1033: and obtaining target data based on the incidence relation between the target data table and the target data table.
The device obtains target data based on the incidence relation between the target data table and the target data table, wherein the target data comprises data corresponding to target data dimensions and the incidence relation between the data corresponding to the target data dimensions.
Further, the target data includes a client list and client information corresponding to the client list, and in order to improve the promotion efficiency, after S103, the method may further include: and obtaining screening information of a client list, and screening the client list and the client information corresponding to the client list based on the screening information to obtain a target client list meeting the screening information and the client information corresponding to the target client list. In this embodiment, the target data includes a client list and client information corresponding to the client list, the device obtains screening information of the client list, the screening information may be set by a service worker in the electric sales system according to a requirement, and the screening information may include a plurality of screening conditions. The device screens the client list and the client information corresponding to the client list based on the screening information to obtain a target client list meeting the screening information and the client information corresponding to the target client list.
In the embodiment of the application, historical pushing information is obtained; performing dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information; and generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy. According to the method, the sent data can be counted and summarized in real time according to the preset dimension information, the target data is generated, and business personnel do not need to spend a large amount of time for summarizing the pushed information every day, so that resources are saved, and the popularization efficiency is improved.
Referring to fig. 3, fig. 3 is a schematic flow chart of another method for managing push data according to a second embodiment of the present application. The execution main body of the method for managing push data in this embodiment is a device having a function of managing push data, and specifically may be a device such as a mobile phone, a computer, a super mobile personal computer, a netbook, a server, and the like. In order to improve the promotion efficiency, the required promotion data can be inquired, and the difference between the present embodiment and the first embodiment is S204, in the present embodiment, S201 to S203 are the same as S101 to S103 in the first embodiment, and S204 is executed after S203. As shown in fig. 3, S204 is specifically as follows:
s204: when a query request is detected, a query result is obtained from the target data based on the query request.
The method comprises the steps that whether a query request exists or not is detected in real time by equipment, wherein the query request is used for acquiring data corresponding to the query request from target data, the query request comprises query condition information, and when the equipment detects the query request, the equipment screens out the data meeting the query condition information from the target data based on the query condition information to acquire a query result.
Further, the query request includes query conditions and query dimension information corresponding thereto, and in order to accurately obtain a query result, S204 may include S2041 to S2043, where as shown in fig. 4, S2041 to S2043 specifically include the following:
s2041: when the query request is detected, the query request is analyzed to obtain query dimension information.
In this embodiment, the query request includes query dimension information, that is, a dimension to which information that needs to be acquired by a service person belongs. And the equipment analyzes the query request to obtain query dimension information.
S2042: and acquiring a target data table corresponding to the query dimension information from the target data based on the query dimension information, and establishing an association relation between the target data tables.
Since the target data includes the data table corresponding to the target data, the device may obtain the target data table corresponding to the query dimension information from the target data based on the query dimension information. And establishing an association relation between the target data tables based on the relation between the query dimension information.
S2043: and obtaining a query result based on the query condition, the target data table and the incidence relation among the target data tables.
The device obtains a query result based on the query condition, the target data table and the association relationship between the target data tables, wherein the query result comprises the association relationship between the target data table and the target data table.
Further, in order to improve the efficiency of popularization, the query result can be derived, after S204, the method may further include: when a query result export request is detected, an export file in a preset format is generated based on the query result, and the export file is exported. When the business personnel inquire the inquiry result, the inquiry result can be exported to obtain the file with the specified format. When business personnel click export in the electricity marketing system, an inquiry result export request is triggered and generated, and when equipment detects the inquiry result export request, an export file in a preset format is generated based on the inquiry result, and the export file is exported. The preset format may be preset for a user, or may be included in the query result export request, and the preset format may be a plurality of formats, for example, a table Excel format, a document word format, and the like.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Referring to fig. 5, fig. 5 is a schematic diagram of an apparatus for managing push data according to a third embodiment of the present application. The units included are used to perform the steps in the embodiments corresponding to fig. 1-4. Please refer to the related description of the embodiments corresponding to fig. 1 to 4. For convenience of explanation, only the portions related to the present embodiment are shown. Referring to fig. 5, the apparatus 5 for managing push data includes:
a first obtaining unit 510, configured to obtain history push information; the historical push information comprises client list information and a push record corresponding to the client list information;
the first processing unit 520 is configured to perform dimension splitting on the client list information and a corresponding push record based on preset dimension information, so as to obtain data corresponding to the preset dimension information;
a first generating unit 530, configured to generate target data based on the data corresponding to the preset dimension information and a preset statistical policy.
Further, the first generating unit 530 is specifically configured to:
generating a data table based on the data corresponding to each piece of preset dimension information;
screening a target data table from the data tables based on a preset statistical strategy, and establishing an association relation between the target data tables;
and obtaining target data based on the incidence relation between the target data table and the target data table.
Further, the apparatus 5 for managing push data further includes:
and the second acquisition unit is used for acquiring an inquiry result from the target data based on the inquiry request when the inquiry request is detected.
Further, the query request comprises query conditions and query dimension information corresponding to the query conditions;
the second obtaining unit is specifically configured to:
when a query request is detected, analyzing the query request to obtain query dimension information;
acquiring a target data table corresponding to the query dimension information from the target data based on the query dimension information, and establishing an association relation between the target data tables;
and obtaining a query result based on the query condition, the target data table and the incidence relation among the target data tables.
Further, the apparatus 5 for managing push data further includes:
and the second generation unit is used for generating an export file in a preset format based on the query result when the query result export request is detected, and the export file is exported.
Further, the target data comprises a client list and client information corresponding to the client list;
the device 5 for managing push data further comprises:
and the second processing unit is used for acquiring screening information of the client list, screening the client list and the client information corresponding to the client list based on the screening information, and obtaining a target client list meeting the screening information and the client information corresponding to the target client list.
Further, the preset dimension information comprises a data batch dimension, a customer grade dimension, a customer warehousing time dimension, a telephone dialing condition dimension and a list forming condition dimension.
Fig. 6 is a schematic diagram of an apparatus for managing push data according to a fourth embodiment of the present application. As shown in fig. 6, the apparatus 6 for managing push data of this embodiment includes: a processor 60, a memory 61 and a computer program 62 stored in said memory 61 and executable on said processor 60, such as a program managing push data. The processor 60, when executing the computer program 62, implements the steps in the various above-described embodiments of the method of an apparatus for managing push data, such as the steps 101 to 103 shown in fig. 1. Alternatively, the processor 60, when executing the computer program 62, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the modules 510 to 530 shown in fig. 5.
Illustratively, the computer program 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 62 in the device for managing push data 6. For example, the computer program 62 may be divided into a first acquisition unit, a first processing unit, and a first generation unit, and each unit specifically functions as follows:
the first acquisition unit is used for acquiring historical push information; the historical push information comprises client list information and a push record corresponding to the client list information;
the first processing unit is used for carrying out dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information;
and the first generating unit is used for generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
The device for determining the promotion list may include, but is not limited to, the processor 60 and the memory 61. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the device 6 for managing push data and does not constitute a limitation of the device 6 for managing push data and may comprise more or less components than those shown, or some components may be combined, or different components, e.g. the device for managing push data may also comprise an input output device, a network access device, a bus, etc.
The Processor 60 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 61 may be an internal storage unit of the device 6 for managing push data, such as a hard disk or a memory of the device 6 for managing push data. The memory 61 may also be an external storage device of the device 6 for managing push data, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), and the like, which are provided on the device 6 for managing push data. Further, the memory 61 may also comprise both an internal storage unit and an external storage device of the device 6 for managing push data. The memory 61 is used for storing the computer program and other programs and data needed by the device for managing push data. The memory 61 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. . Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A method of managing push data, comprising:
acquiring historical pushing information; the historical push information comprises client list information and a push record corresponding to the client list information;
performing dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information;
and generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
2. The method for managing push data according to claim 1, wherein the generating target data based on the data corresponding to the preset dimension information and a preset statistical policy includes:
generating a data table based on the data corresponding to each piece of preset dimension information;
screening a target data table from the data tables based on a preset statistical strategy, and establishing an association relation between the target data tables;
and obtaining target data based on the incidence relation between the target data table and the target data table.
3. The method for managing push data according to claim 1, wherein after generating the target data based on the data corresponding to the preset dimension information and a preset statistical policy, the method further comprises:
when a query request is detected, a query result is obtained from the target data based on the query request.
4. The method of managing push data of claim 3, wherein the query request includes a query condition;
when the query request is detected, obtaining a query result from the target data based on the query request, including:
when a query request is detected, analyzing the query request to obtain query dimension information;
acquiring a target data table corresponding to the query dimension information from the target data based on the query dimension information, and establishing an association relation between the target data tables;
and obtaining a query result based on the query condition, the target data table and the incidence relation among the target data tables.
5. The method for managing push data of any of claims 3-4, further comprising, after the obtaining query results from the target data based on the query request when the query request is detected:
when a query result export request is detected, an export file in a preset format is generated based on the query result, and the export file is exported.
6. The method of managing push data of claim 1, wherein the target data includes a list of customers and their corresponding customer information;
after the target data is generated based on the data corresponding to the preset dimension information and a preset statistical strategy, the method further includes:
and obtaining screening information of a client list, and screening the client list and the client information corresponding to the client list based on the screening information to obtain a target client list meeting the screening information and the client information corresponding to the target client list.
7. The method of managing push data of claim 1, wherein the preset dimension information includes one or more of a data batch dimension, a customer rating dimension, a customer warehousing time dimension, a phone dialing case dimension, and a singleton case dimension.
8. An apparatus for managing push data, comprising:
the first acquisition unit is used for acquiring historical push information; the historical push information comprises client list information and a push record corresponding to the client list information;
the first processing unit is used for carrying out dimension splitting on the client list information and the corresponding push records based on preset dimension information to obtain data corresponding to the preset dimension information;
and the generating unit is used for generating target data based on the data corresponding to the preset dimension information and a preset statistical strategy.
9. An apparatus for managing push data, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911232206.6A CN111105270A (en) | 2019-12-05 | 2019-12-05 | Method and device for managing push data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911232206.6A CN111105270A (en) | 2019-12-05 | 2019-12-05 | Method and device for managing push data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111105270A true CN111105270A (en) | 2020-05-05 |
Family
ID=70421927
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911232206.6A Pending CN111105270A (en) | 2019-12-05 | 2019-12-05 | Method and device for managing push data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111105270A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312176A (en) * | 2021-04-30 | 2021-08-27 | 浙江大搜车软件技术有限公司 | Resource information management method, device, electronic device and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109254966A (en) * | 2018-08-23 | 2019-01-22 | 平安科技（深圳）有限公司 | Tables of data querying method, device, computer equipment and storage medium |
| CN109831592A (en) * | 2018-12-14 | 2019-05-31 | 深圳市佰仟金融服务有限公司 | A kind of list management method and list management equipment |
-
2019
- 2019-12-05 CN CN201911232206.6A patent/CN111105270A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109254966A (en) * | 2018-08-23 | 2019-01-22 | 平安科技（深圳）有限公司 | Tables of data querying method, device, computer equipment and storage medium |
| CN109831592A (en) * | 2018-12-14 | 2019-05-31 | 深圳市佰仟金融服务有限公司 | A kind of list management method and list management equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312176A (en) * | 2021-04-30 | 2021-08-27 | 浙江大搜车软件技术有限公司 | Resource information management method, device, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105657003B (en) | Information processing method and server | |
| CN108492188B (en) | Client recommendation method, device, equipment and storage medium | |
| CN112364004B (en) | Data warehouse-based policy data processing method, device and storage medium | |
| CN110300084A (en) | A kind of IP address-based portrait method and apparatus | |
| CN109657998B (en) | Resource allocation method, device, equipment and storage medium | |
| CN110020149A (en) | Labeling processing method, device, terminal device and the medium of user information | |
| WO2019205324A1 (en) | Task allocation method and system, and terminal device | |
| CN111459961A (en) | Method, device and equipment for updating service data and storage medium | |
| CN109450963B (en) | Message pushing method and terminal equipment | |
| CN111598360A (en) | Service policy determination method and device and electronic equipment | |
| CN108694609B (en) | Advertisement network alliance platform | |
| CN114143402A (en) | AI outbound method, device, computer equipment and storage medium | |
| CN113609409A (en) | Method and system for recommending browsing information, electronic device and storage medium | |
| CN111105270A (en) | Method and device for managing push data | |
| CN112950359A (en) | User identification method and device | |
| CN111311310A (en) | Advertisement order pushing method and device, storage medium and electronic device | |
| CN111695077A (en) | Asset information pushing method, terminal equipment and readable storage medium | |
| CN101770626A (en) | Method, device and system for identifying agents with card-laundering behavior | |
| CN110751510A (en) | Method and device for determining promotion list | |
| CN114817347A (en) | Business approval method and device, electronic equipment and storage medium | |
| CN114285896A (en) | Information pushing method, device, equipment, storage medium and program product | |
| CN112131219A (en) | Customer maintenance management method and system | |
| CN113434754A (en) | Method and device for determining recommended API (application program interface) service, electronic equipment and storage medium | |
| CN107368597B (en) | Information output method and device | |
| CN111127077A (en) | Recommendation method and device based on stream computing |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200505 |
|
| WD01 | Invention patent application deemed withdrawn after publication |