CN112435071A - Promotion data creating method and system - Google Patents

Promotion data creating method and system Download PDF

Info

Publication number
CN112435071A
CN112435071A CN202011398613.7A CN202011398613A CN112435071A CN 112435071 A CN112435071 A CN 112435071A CN 202011398613 A CN202011398613 A CN 202011398613A CN 112435071 A CN112435071 A CN 112435071A
Authority
CN
China
Prior art keywords
data
creating
creation
interface
creating step
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.)
Granted
Application number
CN202011398613.7A
Other languages
Chinese (zh)
Other versions
CN112435071B (en
Inventor
田星星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Bilibili Technology Co Ltd
Original Assignee
Shanghai Bilibili Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Bilibili Technology Co Ltd filed Critical Shanghai Bilibili Technology Co Ltd
Priority to CN202011398613.7A priority Critical patent/CN112435071B/en
Publication of CN112435071A publication Critical patent/CN112435071A/en
Application granted granted Critical
Publication of CN112435071B publication Critical patent/CN112435071B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/0241—Advertisements
    • G06Q30/0273—Determination of fees for advertising
    • 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/0241—Advertisements
    • G06Q30/0272—Period of advertisement exposure
    • 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/0241—Advertisements
    • G06Q30/0277—Online advertisement
    • 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/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders
    • 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
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services; Handling legal documents
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application discloses a promotion data creating method, which comprises the following steps: configuring interface request data corresponding to each creating step in the creating step sequence corresponding to the promotion data; traversing the creating step sequence to obtain the current creating step; acquiring interface request data corresponding to the current creation step; generating an HTTP request corresponding to the current creating step according to the interface request data; sending an HTTP request to a server and receiving feedback data of the server; and executing the current creating step according to the feedback data, and then acquiring the next creating step from the creating step sequence until all creating steps are completed so as to create the promotion data. The application also discloses a promotion data creation system, an electronic device and a computer readable storage medium. Therefore, HTTP interface request data corresponding to each creating step can be extracted, different HTTP requests are automatically generated and are connected in series according to the creating step sequence, and automatic creating of the promotion data is achieved.

Description

Promotion data creating method and system
Technical Field
The present application relates to the field of data creation technologies, and in particular, to a method, a system, an electronic device, and a computer-readable storage medium for creating promotional data.
Background
Developers or testers need to create different types of creative promotion data when testing a promotion data (e.g., advertisement) engine. However, it is time-consuming and labor-consuming to manually create a piece of popularization data, it takes time to become familiar with the business system, configure the delivery policy, and prepare the popularization data creative material to be delivered before delivery, and after delivery of the popularization data is completed, the user needs to log in a popularization data auditing platform to audit the popularization data creative, and the popularization data can be normally displayed after the audit is passed. Generally, the magnitude of promotion data required in testing is large, and a plurality of promotion data of different types are required. In addition, different types of promotion data need to be released in different promotion data releasing systems, creating steps are different, and links and time for creating the promotion data are very long.
It should be noted that the above-mentioned contents are not intended to limit the scope of protection of the application.
Disclosure of Invention
The present application mainly aims to provide a method, a system, an electronic device and a computer-readable storage medium for creating promotional data, and aims to solve the problem of how to automatically and quickly create a large amount of promotional data of a desired type.
In order to achieve the above object, an embodiment of the present application provides a method for creating promotional data, where the method includes:
configuring interface request data corresponding to each creating step in the creating step sequence corresponding to the promotion data;
traversing the creating step sequence to obtain the current creating step;
acquiring the interface request data corresponding to the current creation step from the configuration;
generating an HTTP request corresponding to the current creating step according to the interface request data;
sending the HTTP request to a server and receiving feedback data of the server; and
and executing the current creating step according to the feedback data, and then acquiring the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed so as to create the promotion data.
Optionally, before configuring interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data, the method further includes:
receiving a type of the promotional data;
and acquiring a creating step sequence corresponding to the promotion data of the type from a preset template.
Optionally, the configuring interface request data respectively corresponding to each creation step in the creation step sequence corresponding to the promotion data includes:
defining the corresponding relation between each creating step and each interface request data in a file with a preset format, wherein the interface request data comprises an interface address, an interface request mode and an interface request parameter.
Optionally, the generating an HTTP request corresponding to the current creating step according to the interface request data includes:
extracting the interface request mode and the interface request parameter from the interface request data;
and generating the HTTP request according to the interface request mode and the interface request parameters.
Optionally, the sending the HTTP request to the server includes:
extracting the interface address from the interface request data;
and sending the HTTP request to a server according to the interface address.
Optionally, the generating the HTTP request corresponding to the current creating step according to the interface request data further includes:
judging whether the HTTP request corresponding to the current creating step needs upstream data or not;
when the upstream data is needed, acquiring the upstream data;
and generating the HTTP request according to the interface request data and the upstream data.
Optionally, the determining whether the HTTP request corresponding to the current creating step requires upstream data includes:
and judging whether the HTTP request corresponding to the current creating step needs upstream data according to the definition in the file with the preset format, wherein the upstream data comprises the feedback data saved in the previous step of the current creating step or data input by a user on a front end page.
Optionally, the acquiring the upstream data includes:
and acquiring the upstream data from the feedback data saved in the previous step of the current creating step or the received data input by the user on the front end page.
Optionally, the generating the HTTP request corresponding to the current creating step according to the interface request data further includes:
and generating login information and adding the login information into the HTTP request, wherein the login information comprises a login account and a login key, the login account is obtained from the previous step of the current establishing step, and the login key is generated according to a login mode corresponding to the type of the promotion data.
In addition, to achieve the above object, an embodiment of the present application further provides a system for creating promotion data, where the system includes:
the configuration module is used for configuring interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data;
the acquisition module is used for traversing the creation step sequence, acquiring the current creation step and acquiring the interface request data corresponding to the current creation step from the configuration;
a generating module, configured to generate, according to the interface request data, an HTTP request corresponding to the current creating step;
the receiving and sending module is used for sending the HTTP request to a server and receiving feedback data of the server;
and the creating module is used for executing the current creating step according to the feedback data, and then the obtaining module obtains the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed so as to create the promotion data.
In order to achieve the above object, an embodiment of the present application further provides an electronic device, including: the promotion data creation program is stored on the memory and can run on the processor, and when being executed by the processor, the promotion data creation program realizes the promotion data creation method.
In order to achieve the above object, an embodiment of the present application further provides a computer-readable storage medium, where a promotion data creation program is stored, and when executed by a processor, the promotion data creation program implements the promotion data creation method as described above.
The promotion data creation method, the promotion data creation system, the electronic device and the computer-readable storage medium can extract HTTP interface request data corresponding to each creation step of different types of promotion data, automatically generate different HTTP requests and connect in series according to the creation step sequence, achieve automatic creation of the promotion data, are high in creation efficiency and reliable in data, and are widely applicable to various different data types.
Drawings
FIG. 1 is a diagram of an application environment architecture in which various embodiments of the present application may be implemented;
fig. 2 is a flowchart of a method for creating promotional data according to a first embodiment of the present application;
FIG. 3 is a detailed flowchart of step S206 in FIG. 2;
fig. 4 is a flowchart of a method for creating promotional data according to a second embodiment of the present application;
fig. 5 is a flowchart of a method for creating promotional data according to a specific embodiment of the present application;
fig. 6 is a schematic hardware architecture diagram of an electronic device according to a third embodiment of the present application;
fig. 7 is a schematic block diagram of a promotion data creation system according to a fourth embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the descriptions relating to "first", "second", etc. in the embodiments of the present application are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a diagram illustrating an application environment architecture for implementing various embodiments of the present application. The present application is applicable in application environments including, but not limited to, client 2, server 4, network 6.
The client 2 is configured to receive a promotion data type, obtain a corresponding creation step sequence according to the type, configure interface request data corresponding to each creation step, send an HTTP request to an interface corresponding to the server 4, create the promotion data according to feedback data of the server 4, and the like. The client 2 may be a terminal device such as a PC (Personal Computer), a mobile phone, a tablet Computer, and a portable Computer.
The server 4 is configured to receive an HTTP (hypertext transfer protocol) request sent by the client 2 and feed back corresponding data. The server 4 may be a rack server, a blade server, a tower server, a cabinet server, or other computing devices, may be an independent server, or may be a server cluster formed by a plurality of servers.
The network 6 may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like. The server 4 and one or more clients 2 are connected through the network 6 for data transmission and interaction.
Example one
As shown in fig. 2, a flowchart of a method for creating promotional data according to a first embodiment of the present application is provided. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. Some steps in the flowchart may be added or deleted as desired. In this embodiment, the client 2 is taken as a main execution subject to be exemplarily described.
The method comprises the following steps:
s200, configuring interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data.
Different promotion data respectively have different a series of creation steps, constitute a kind of creation step sequence. Each creation step of the promotion data requires a corresponding HTTP interface to be invoked to send an HTTP request to the server 4. Different creating steps correspond to different HTTP interfaces, HTTP interface request data of each creating step in the creating step sequence are configured, and the HTTP interface requests of each creating step are connected in series, so that automatic creating of the popularization data can be achieved.
In this embodiment, in order to simplify the HTTP request calling process, the interface request data of the HTTP interface corresponding to each of the creating steps is defined in a YAML (a data format) file. The YAML file comprises the corresponding relation between each creating step and each interface request data. The interface request data includes, but is not limited to, an interface address, an interface request mode, and an interface request parameter. The subsequent client 2 may obtain the corresponding interface request data from the YAML file according to each of the creation steps.
In addition, some data in the interface request parameters may be defined as variables, and the values of the variables are dynamically set each time an HTTP request is made.
S202, traversing the creating step sequence and acquiring the current creating step.
And when the promotion data is created, acquiring the creation step sequence corresponding to the promotion data. The creating step sequence generally includes a plurality of creating steps, and the client 2 traverses the creating step sequence, sequentially acquires and executes each creating step according to the sequence in the creating step sequence. Each creation step that is acquired and being performed is referred to as a current creation step.
S204, the interface request data corresponding to the current creating step is obtained from the configuration.
In the above step S200, interface request data corresponding to each of the creating steps in the creating step sequence has been configured. After the current creation step is obtained, the interface request data corresponding to the current creation step is further obtained from the configuration (YAML file), wherein the interface request data comprises an interface address, an interface request mode and an interface request parameter.
S206, generating the HTTP request corresponding to the current creating step according to the interface request data.
Specifically, the interface request mode and the interface request parameter are extracted from the interface request data, and the HTTP request is generated according to the interface request mode and the interface request parameter.
The client 2 automatically packages the HTTP request according to the interface request data and sends the HTTP request to the server 4, and the request call of the HTTP interface is completed, so that the corresponding creating step can be realized.
Notably, the HTTP request also typically includes login information and upstream data. The login information comprises a login account and a login key. The login account can be transmitted from an upstream link (a creating step before a current creating step), and the login key is generated according to a predetermined rule (different login modes corresponding to different types of promotion data are different, and different login key generation modes are required). When the HTTP request is sent each time, the login information is sent to the server together, the server verifies whether the account is logged in or not according to the login information, and the server receives the HTTP request only after the login information is verified.
The upstream data is divided into two cases, which may be server feedback data stored in an HTTP request corresponding to an upstream link, or data input by a user on a front-end page. Whether the upstream data is used in the HTTP request calling process needs to be defined in the YAML file in advance, the format is $ { variable name } or $ variable name, and the variable name identifies the name of the data stored in the upstream link.
Specifically, further refer to fig. 3, which is a schematic view of the detailed flow of step S206. It is to be understood that the flow chart is not intended to limit the order in which the steps are performed. Some steps in the flowchart may be added or deleted as desired. In this embodiment, the step S206 specifically includes:
s2062, determining whether the HTTP request corresponding to the current creating step needs upstream data. When upstream data is required, steps S2064-S2066 are executed. When the upstream data is not required, step S2066 is directly performed.
Whether the HTTP request corresponding to each creation step requires upstream data may be preset in the interface request data (e.g., in the interface request parameter part), and it may also be set from where which upstream data is required to be obtained. After the interface request data corresponding to the current creation step is obtained, whether the HTTP request corresponding to the current creation step needs upstream data or not is judged according to the interface request data.
S2064, acquiring the upstream data.
When the HTTP request needs upstream data, the upstream data is obtained from the feedback data stored in the previous step or the received data input by the user on the front-end page according to the preset condition.
S2066, an HTTP request is generated.
And when the HTTP request does not need upstream data, generating a corresponding HTTP request directly according to the interface request mode and the interface request parameters in the interface request data. And when the HTTP request needs upstream data, generating a corresponding HTTP request according to the interface request data and the acquired upstream data. In addition, login information needs to be generated and added to the HTTP request.
Returning to fig. 2, S208, the HTTP request is sent to the server and feedback data of the server is received.
Specifically, the interface address is extracted from the interface request data, and the HTTP request is sent to the server 4 according to the interface address in the interface request data.
After receiving the HTTP request, the server 4 first verifies the login information, receives the HTTP request after the verification is passed, and obtains corresponding feedback data according to the parameters requested in the HTTP request and sends the feedback data to the client 2. The client 2 receives the feedback data sent by the server 4.
S210, executing the current creating step according to the feedback data, then returning to the step S202, and obtaining the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed to create the promotion data.
After receiving the feedback data sent by the server 4, the corresponding creating step may be performed according to the feedback data. And then continuing to generate a corresponding HTTP request according to the next creation step in the creation step sequence, sending the HTTP request to the server and receiving feedback data of the server, and executing to finish the next creation step according to the feedback data. And repeating the steps until all the creating steps in the creating step sequence are completed, and then creating the corresponding promotion data.
The promotion data creation method provided by this embodiment can extract HTTP interface request data corresponding to each creation step of different promotion data, automatically generate different HTTP requests, and connect in series according to the creation step sequence, thereby implementing automatic creation of the promotion data, and the promotion data creation method is high in creation efficiency and reliable in data, and is widely applicable to various different data types.
Example two
As shown in fig. 4, a flowchart of a method for creating promotional data according to a second embodiment of the present application is provided. In this embodiment, the promotion data creation method further includes steps S300 to S302 on the basis of the first embodiment. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. Some steps in the flowchart may be added or deleted as desired.
The method comprises the following steps:
and S300, receiving the type of the promotion data required to be created.
Aiming at each different type of promotion data, a different series of creation steps exist respectively. When promotion data needs to be created, a user firstly inputs the type of the promotion data, and after the client 2 receives the type, the subsequent process is executed according to the type.
S302, acquiring a creating step sequence corresponding to the type of popularization data from a preset template.
Different creating steps can be preset respectively for different types of promotion data. In this embodiment, the template may be a corresponding relationship list between the type and the creating step, or may be a template file in any other feasible form, which is not limited herein. Generally, one type of promotion data corresponds to a plurality of creation steps, which constitute the sequence of creation steps in execution order.
After the client 2 receives the type of the promotion data to be created, the creation step sequence corresponding to the promotion data of the type is obtained from the preset template, and then the corresponding creation steps are executed according to the creation step sequence.
S304, configuring interface request data corresponding to each creation step in the creation step sequence.
Each of the creation steps in the sequence of creation steps needs to call a corresponding HTTP interface to send an HTTP request to the server 4. Different creating steps correspond to different HTTP interfaces, HTTP interface request data of each creating step in the creating step sequence are configured, and the HTTP interface requests of each creating step are connected in series, so that automatic creating of the popularization data can be achieved.
In this embodiment, in order to simplify the HTTP request calling process, the interface request data of the HTTP interface corresponding to each of the creating steps is defined in a YAML (a data format) file. The YAML file comprises the corresponding relation between each creating step and each interface request data. The interface request data includes, but is not limited to, an interface address, an interface request mode, and an interface request parameter. The subsequent client 2 may obtain the corresponding interface request data from the YAML file according to each of the creation steps.
In addition, some data in the interface request parameters may be defined as variables, and the values of the variables are dynamically set each time an HTTP request is made.
S306, traversing the creating step sequence and obtaining the current creating step.
And when the promotion data is created, acquiring the creation step sequence corresponding to the promotion data. The creating step sequence generally includes a plurality of creating steps, and the client 2 traverses the creating step sequence, sequentially acquires and executes each creating step according to the sequence in the creating step sequence. Each creation step that is acquired and being performed is referred to as a current creation step.
S308, acquiring the interface request data corresponding to the current creating step from the configuration.
In step S304, interface request data corresponding to each of the creating steps in the creating step sequence has been configured. After the current creation step is obtained, the interface request data corresponding to the current creation step is further obtained from the configuration (YAML file), wherein the interface request data comprises an interface address, an interface request mode and an interface request parameter.
S310, generating an HTTP request corresponding to the current creating step according to the interface request data.
Specifically, the interface request mode and the interface request parameter are extracted from the interface request data, and the HTTP request is generated according to the interface request mode and the interface request parameter.
The client 2 automatically packages the HTTP request according to the interface request data and sends the HTTP request to the server 4, and the request call of the HTTP interface is completed, so that the corresponding creating step can be realized.
Notably, the HTTP request also typically includes login information and upstream data. The login information comprises a login account and a login key. The login account can be transmitted from an upstream link (a creating step before a current creating step), and the login key is generated according to a predetermined rule (different login modes corresponding to different types of promotion data are different, and different login key generation modes are required). When the HTTP request is sent each time, the login information is sent to the server together, the server verifies whether the account is logged in or not according to the login information, and the server receives the HTTP request only after the login information is verified.
The upstream data is divided into two cases, which may be server feedback data stored in an HTTP request corresponding to an upstream link, or data input by a user on a front-end page. Whether the upstream data is used in the HTTP request calling process needs to be defined in the YAML file in advance, the format is $ { variable name } or $ variable name, and the variable name identifies the name of the data stored in the upstream link.
The specific process of this step is referred to fig. 3 and the related description, and is not described herein again.
S312, the HTTP request is sent to the server and the feedback data of the server is received.
Specifically, the interface address is extracted from the interface request data, and the HTTP request is sent to the server 4 according to the interface address in the interface request data.
After receiving the HTTP request, the server 4 first verifies the login information, receives the HTTP request after the verification is passed, and obtains corresponding feedback data according to the parameters requested in the HTTP request and sends the feedback data to the client 2. The client 2 receives the feedback data sent by the server 4.
And S314, executing the current creating step according to the feedback data, then returning to the step S306, and acquiring the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed to create the popularization data.
After receiving the feedback data sent by the server 4, the corresponding creating step may be performed according to the feedback data. And then continuing to generate a corresponding HTTP request according to the next creation step in the creation step sequence, sending the HTTP request to the server and receiving feedback data of the server, and executing to finish the next creation step according to the feedback data. And repeating the steps until all the creating steps in the creating step sequence are completed, and then creating the corresponding promotion data.
The popularization data creating method provided in this embodiment may set different creating step sequences corresponding to different types of popularization data in a template, and configure different interface request data corresponding to each creating step in the creating step sequences. When a certain type of the promotion data needs to be created, HTTP interface request data corresponding to each creation step of the promotion data of the type are extracted, different HTTP requests are automatically generated and are connected in series according to the creation step sequence, automatic creation of the promotion data is achieved, creation efficiency is high, data are reliable, and the method and the device are widely applicable to various different data types.
In order to explain the above steps of the method more thoroughly, a specific embodiment (the promotion data is advertisement data) is taken as an example for explanation. Those skilled in the art should appreciate that the following detailed description is not intended to limit the inventive concepts of the present disclosure and that appropriate content divergence and extensions can be readily devised by those skilled in the art based on the following detailed description of the embodiments.
As shown in fig. 5, a flowchart of a method for creating promotional data is provided in accordance with a specific embodiment of the present application. In this specific embodiment, the promotion data creation method includes the following steps:
s400, receiving the advertisement data type required to be created.
The advertisement data types comprise effect advertisements, brand advertisements, mutual selection advertisements (advertisers and uploaders), personal takeoff advertisements (tools for the uploaders to put original non-commercial video contents in commercial traffic and increase video exposure and click play volume through operation optimization so as to quickly expand the popularity), real-time bidding advertisements and the like. Different advertisement types have different selling modes, and the corresponding advertisement data has different creating steps.
S402, acquiring a creating step sequence corresponding to the advertisement data type from a preset template.
The following describes a sequence of creating steps corresponding to each advertisement data type, taking the above advertisement data types as examples:
when the advertisement data type is an effect advertisement, the corresponding sequence of creating steps includes:
(1) selecting an advertisement delivery account: in an advertisement delivery system (platform for delivering advertisement creatives), an account needing to deliver the advertisement creatives is selected, and the account is logged in.
(2) And (3) creating an advertisement plan: setting plan name, total budget, advertising promotion purpose, etc.
(3) Creating an advertisement unit: and setting unit names, directional information, release time, release frequency and the like.
(4) And (3) creating an advertisement creative: configure creative titles, descriptions, creative pictures, jump links, etc.
(5) And (4) checking of advertisement creativity: and examining and verifying the advertisement creativity on the advertisement examination platform, wherein the advertisement creativity can be displayed through an advertisement engine after the examination and verification is passed. When requested, the ad engine may expose different ad creatives based on the requested parameters (e.g., ad location, user information, IP information, device information, etc.).
Wherein the advertisement plan, advertisement unit and advertisement are created as three dimensions of information from large to small in the advertisement data.
When the advertisement data type is a brand advertisement, the corresponding creating step sequence comprises:
(1) and (3) contract creation: logging on to the customer relationship management system creates a sales contract.
(2) Creating an order: logging in an advertisement delivery system, selecting a contract and creating an order.
(3) Creating a scheduling: and configuring the display time, the display position and the like of the ad slot creatives.
It should be noted that when a schedule is newly created, once the display time or the display position of the advertisement schedule is occupied, the advertisement schedule and the display time or the occupation situation of the advertisement schedule and the display position need to be cleared up in the database (clearing does not affect the display of the advertisement).
(4) Contract submission: after the schedule is created, contract auditing is required to be carried out in a client relationship management system (the contract is associated with schedule information).
(5) Newly creating an original: after the contract is approved, the scheduling ID can be taken in the database, and the advertisement creative idea is created according to the scheduling ID, wherein the creative idea comprises configuration creative title, description, creative picture, skip link and the like.
(6) And (3) modifying the creative display time: the current time cannot be selected for creation of an advertising creative and the creative presentation time may need to be modified after successful creation of the advertising creative, for example, from the 0 th day.
(7) And (4) auditing creativity: and checking creativity on the advertisement checking platform, wherein the advertisement creativity can be displayed through an advertisement engine after the checking is passed.
The brand advertisement is subdivided into CPT (Cost Per Time, charged according to the user use duration or use period), GD (Guaranteed delivery), splash CPT, splash GD, and the like, and respectively corresponds to different delivery strategies. Different advertisement delivery strategies have slight differences in advertisement delivery steps, and separate logic judgment processing is required.
When the advertisement data type is a mutually selected advertisement, the corresponding creating step sequence comprises:
(1) and (4) releasing tasks: advertisers configure task names, task budgets, task times, platforms (Android or iPhone), creative styles, and the like.
(2) And (3) receiving a task: an uploader (a user who uploads a video file) logs in a task platform to upload a video, and mounts a task issued by an advertiser in an advertisement display area of the video (for example, the lower part of the video or the video area is on a playing page of the video, and the task is specifically represented as a recommendation position or a bullet screen).
When the advertisement data type is an individual takeoff advertisement, the corresponding creating step sequence comprises the following steps:
(1) creating a video order: the uploader selects the uploaded video in the video website and creates a video order, including setting the order amount, the order type and the like.
(2) And (3) executing a timing task: and sending the order information to an order auditing platform.
(3) And (4) checking orders: and (6) the order is approved.
(4) And executing the timing task again: after the order is inquired and approved, the advertisement creativity is automatically generated.
(5) And (4) auditing creativity: and checking creativity on the advertisement checking platform, wherein the advertisement creativity can be displayed through an advertisement engine after the checking is passed.
Aiming at the mutual selection advertisement and the personal takeoff advertisement, when the video is selected, the processing mode of the code layer is as follows: and searching the effective video ID of the uploader, binding the task by using the video ID and creating an order. The video ID cannot be reused after being occupied, and all valid videos cannot be bound again after being occupied, so that the association between the task, the order and the video ID needs to be removed in the database after the video ID is used each time.
S404, configuring the interface request data corresponding to each creation step in the creation step sequence.
Each step requires calling an HTTP interface in the advertisement service system to make an HTTP request. For each advertisement data type, firstly, according to each creating step in the creating step sequence corresponding to each advertisement data type, corresponding interface request data including an interface address, an interface request mode, an interface request parameter and the like are respectively defined in the YAML file.
S406, traversing the creating step sequence, and acquiring the current creating step and the interface request data corresponding to the current creating step.
When the advertisement data is created, acquiring the creation step sequence corresponding to the advertisement data type, traversing the creation step sequence, and sequentially acquiring and executing each creation step (current creation step) according to the sequence in the creation step sequence. After the current creation step is obtained, the interface request data corresponding to the current creation step is further obtained from the YAML file, wherein the interface request data comprises an interface address, an interface request mode and an interface request parameter.
S408, generating an HTTP request corresponding to the current creating step according to the interface request data, and sending the HTTP request to a server and receiving feedback data of the server.
Reading the interface request data in the YAML file, automatically packaging the HTTP request and sending the HTTP request to the server 4, and receiving the feedback data sent by the server 4. The HTTP request further needs to encapsulate login information, wherein the login information comprises a login account and a login key, the login account can be transmitted from the previous creating step, and the login key is generated according to a login mode corresponding to the advertisement data type. It is also necessary to see from the YAML file whether the HTTP request requires upstream data. The upstream data may be server feedback data stored in an HTTP request corresponding to the upstream link, or may be data input by the user on a front-end page.
The feedback data saved after the HTTP request is invoked is typically some identification ID generated by the ad delivery system, such as an ad plan ID, an ad unit ID, an ad creative ID, and so on. Taking an effective ad as an example, the step of creating an ad unit requires an ad plan ID stored in the previous step (ad plan creation), the step of creating an ad creative requires an ad unit ID stored in the previous step (ad creation), and the step of reviewing an ad creative requires an ad creative ID stored in the previous step (ad creative creation).
The data input by the front-end page comprises account ID, putting position, promotion type, plan name, unit name, creative name and the like, and is used for creative differentiated advertisement data. Background code can connect the whole creating process in series, and users do not need to care about dimension information of advertisement plans, units and the like. The ad creatives can be directly acquired by the ad engine after being successfully created and can be directly taken for testing.
After the HTTP request call for each creation step is completed, the database needs to be searched for data that is successfully created. Taking the step of creating an ad plan as an example, the ad plan ID that was just created successfully needs to be found, and needs to be saved in the code, and the ad plan ID can be used as a parameter in the next HTTP request call, for example, the ad plan ID needs to be used in the step of creating an ad unit.
S410, executing the current creating step according to the feedback data, then returning to the step S406, and acquiring the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed, so as to create the advertisement data of the advertisement data type.
After receiving the feedback data sent by the server 4, the corresponding creating step may be performed according to the feedback data. And then continuing to generate a corresponding HTTP request according to the next creation step in the creation step sequence, sending the HTTP request to the server and receiving feedback data of the server, and executing to finish the next creation step according to the feedback data. Taking effect advertisement as an example, after generating an HTTP request corresponding to the step of selecting an advertisement delivery account and obtaining feedback data of the server 4, executing the step of selecting an advertisement delivery account, then generating an HTTP request corresponding to the step of creating an advertisement plan, executing the step of generating an advertisement plan after obtaining the feedback data, then generating an HTTP request corresponding to the step of creating an advertisement unit, and so on until all creating steps in the creating step sequence are completed, the corresponding effect advertisement data can be created.
In addition, it is noted that different advertisement templates (different placement positions) require different picture sizes, and the advertisement picture can be scaled and cropped according to the size required by the template in the embodiment.
The promotion data creation method provided by the embodiment can extract the HTTP interface information corresponding to each step of creating advertisement data in different advertisement service systems, serially connect the HTTP interface requests of each step through codes, and request to create the HTTP interface corresponding to each step of creating advertisements according to the steps of creating advertisements in the advertisement service systems strictly, so that the second-level creation of advertisement originality is realized, code calling abnormity generated by a reference tool kit cannot occur, the creation flow of the advertisements is completely simulated, and the problem of unreliable advertisement data cannot occur.
EXAMPLE III
As shown in fig. 6, a hardware architecture of an electronic device 20 is provided for a third embodiment of the present application. In the present embodiment, the electronic device 20 may include, but is not limited to, a memory 21, a processor 22, and a network interface 23, which are communicatively connected to each other through a system bus. It is noted that fig. 6 only shows the electronic device 20 with components 21-23, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead. In this embodiment, the electronic device 20 may be the client 2.
The memory 21 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 21 may be an internal storage unit of the electronic device 20, such as a hard disk or a memory of the electronic device 20. In other embodiments, the memory 21 may also be an external storage device of the electronic apparatus 20, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the electronic apparatus 20. Of course, the memory 21 may also include both an internal storage unit and an external storage device of the electronic apparatus 20. In this embodiment, the memory 21 is generally used for storing an operating system installed in the electronic device 20 and various application software, such as program codes of the promotion data creation system 60. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 22 is generally used to control the overall operation of the electronic device 20. In this embodiment, the processor 22 is configured to run the program codes stored in the memory 21 or process data, for example, run the promotion data creation system 60.
The network interface 23 may include a wireless network interface or a wired network interface, and the network interface 23 is generally used for establishing a communication connection between the electronic apparatus 20 and other electronic devices.
Example four
Fig. 7 is a schematic block diagram of a promotion data creation system 60 according to a fourth embodiment of the present application. Promotional data creation system 60 can be partitioned into one or more program modules that are stored in a storage medium and executed by one or more processors to implement embodiments of the present application. The program modules referred to in the embodiments of the present application refer to a series of computer program instruction segments capable of performing specific functions, and the following description will specifically describe the functions of each program module in the embodiments.
In this embodiment, the promotion data creation system 60 includes:
a configuration module 600, configured to configure interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data.
Different promotion data respectively have different a series of creation steps, constitute a kind of creation step sequence. Each creation step of the promotion data requires a corresponding HTTP interface to be invoked to send an HTTP request to the server 4. Different creating steps correspond to different HTTP interfaces, HTTP interface request data of each creating step in the creating step sequence are configured, and the HTTP interface requests of each creating step are connected in series, so that automatic creating of the popularization data can be achieved.
In this embodiment, in order to simplify the HTTP request calling process, the interface request data of the HTTP interface corresponding to each of the creating steps is defined in a YAML (a data format) file. The YAML file comprises the corresponding relation between each creating step and each interface request data. The interface request data includes, but is not limited to, an interface address, an interface request mode, and an interface request parameter. And acquiring corresponding interface request data from the YAML file according to each creating step.
In addition, some data in the interface request parameters may be defined as variables, and the values of the variables are dynamically set each time an HTTP request is made.
An obtaining module 602, configured to traverse the creating step sequence, obtain a current creating step, and obtain, from the configuration, interface request data corresponding to the current creating step.
And when the promotion data is created, acquiring the creation step sequence corresponding to the promotion data. The creating step sequence generally includes a plurality of creating steps, and the obtaining module 602 traverses the creating step sequence, and sequentially obtains and executes each creating step according to an order in the creating step sequence. Each creation step that is acquired and being performed is referred to as a current creation step. After the current creation step is obtained, the obtaining module 602 further obtains, from the configuration (YAML file), the interface request data corresponding to the current creation step, including an interface address, an interface request mode, and an interface request parameter.
A generating module 604, configured to generate, according to the interface request data, an HTTP request corresponding to the current creating step.
Specifically, the interface request mode and the interface request parameter are extracted from the interface request data, and the HTTP request is generated according to the interface request mode and the interface request parameter.
Notably, the HTTP request also typically includes login information and upstream data. The login information comprises a login account and a login key. The login account can be transmitted from an upstream link (a creating step before a current creating step), and the login key is generated according to a predetermined rule (different login modes corresponding to different types of promotion data are different, and different login key generation modes are required). When the HTTP request is sent each time, the login information is sent to the server together, the server verifies whether the account is logged in or not according to the login information, and the server receives the HTTP request only after the login information is verified.
The upstream data is divided into two cases, which may be server feedback data stored in an HTTP request corresponding to an upstream link, or data input by a user on a front-end page. Whether the upstream data is used in the HTTP request calling process needs to be defined in the YAML file in advance, the format is $ { variable name } or $ variable name, and the variable name identifies the name of the data stored in the upstream link.
A transceiver module 606, configured to send the HTTP request to a server and receive feedback data of the server.
Specifically, the transceiver module 606 extracts the interface address from the interface request data, and sends the HTTP request to the server 4 according to the interface address in the interface request data.
After receiving the HTTP request, the server 4 first verifies the login information, receives the HTTP request after the verification is passed, and obtains corresponding feedback data according to the parameters requested in the HTTP request and sends the feedback data to the client 2. The transceiver module 606 receives the feedback data sent by the server 4.
A creating module 608, configured to execute the current creating step according to the feedback data, and then trigger the obtaining module 602 to obtain a next creating step from the creating step sequence until all creating steps of the creating step sequence are completed, so as to create the popularization data.
After receiving the feedback data sent by the server 4, the corresponding creating step may be performed according to the feedback data. And then continuing to generate a corresponding HTTP request according to the next creation step in the creation step sequence, sending the HTTP request to the server and receiving feedback data of the server, and executing to finish the next creation step according to the feedback data. And repeating the steps until all the creating steps in the creating step sequence are completed, and then creating the corresponding promotion data.
The promotion data creation system provided by this embodiment can extract HTTP interface request data corresponding to each creation step of different promotion data, automatically generate different HTTP requests, and connect in series according to the creation step sequence, thereby implementing automatic creation of the promotion data, and the promotion data creation system is high in creation efficiency and reliable in data, and is widely applicable to various different data types.
EXAMPLE five
The present application further provides another embodiment, which is to provide a computer-readable storage medium storing a promotion data creation program, which is executable by at least one processor to cause the at least one processor to perform the steps of the promotion data creation method as described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications that can be made by the use of the equivalent structures or equivalent processes in the specification and drawings of the present application or that can be directly or indirectly applied to other related technologies are also included in the scope of the present application.

Claims (12)

1. A method for promotional data creation, the method comprising:
configuring interface request data corresponding to each creating step in the creating step sequence corresponding to the promotion data;
traversing the creating step sequence to obtain the current creating step;
acquiring the interface request data corresponding to the current creation step from the configuration;
generating an HTTP request corresponding to the current creating step according to the interface request data;
sending the HTTP request to a server and receiving feedback data of the server; and
and executing the current creating step according to the feedback data, and then acquiring the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed so as to create the promotion data.
2. The promotion data creation method according to claim 1, wherein before configuring interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data, the method further comprises:
receiving a type of the promotional data;
and acquiring a creating step sequence corresponding to the promotion data of the type from a preset template.
3. The promotion data creation method according to claim 1 or 2, wherein the configuring of the interface request data corresponding to each creation step in the sequence of creation steps corresponding to the promotion data includes:
defining the corresponding relation between each creating step and each interface request data in a file with a preset format, wherein the interface request data comprises an interface address, an interface request mode and an interface request parameter.
4. The promotion data creation method according to claim 3, wherein the generating of the HTTP request corresponding to the current creation step according to the interface request data includes:
extracting the interface request mode and the interface request parameter from the interface request data;
and generating the HTTP request according to the interface request mode and the interface request parameters.
5. The promotional data creation method of claim 4 wherein said sending said HTTP request to a server comprises:
extracting the interface address from the interface request data;
and sending the HTTP request to a server according to the interface address.
6. The promotional data creation method according to claim 4 wherein said generating an HTTP request corresponding to said current creation step based on said interface request data further comprises:
judging whether the HTTP request corresponding to the current creating step needs upstream data or not;
when the upstream data is needed, acquiring the upstream data;
and generating the HTTP request according to the interface request data and the upstream data.
7. The promotion data creation method according to claim 6, wherein the determining whether the HTTP request corresponding to the current creation step requires upstream data includes:
and judging whether the HTTP request corresponding to the current creating step needs upstream data according to the definition in the file with the preset format, wherein the upstream data comprises the feedback data saved in the previous step of the current creating step or data input by a user on a front end page.
8. The promotional data creation method according to claim 7 wherein said obtaining said upstream data comprises:
and acquiring the upstream data from the feedback data saved in the previous step of the current creating step or the received data input by the user on the front end page.
9. The promotional data creation method according to claim 6 wherein said generating an HTTP request corresponding to said current creation step based on said interface request data further comprises:
and generating login information and adding the login information into the HTTP request, wherein the login information comprises a login account and a login key, the login account is obtained from the previous step of the current establishing step, and the login key is generated according to a login mode corresponding to the type of the promotion data.
10. A promotional data creation system, the system comprising:
the configuration module is used for configuring interface request data corresponding to each creation step in the creation step sequence corresponding to the promotion data;
the acquisition module is used for traversing the creation step sequence, acquiring the current creation step and acquiring the interface request data corresponding to the current creation step from the configuration;
a generating module, configured to generate, according to the interface request data, an HTTP request corresponding to the current creating step;
the receiving and sending module is used for sending the HTTP request to a server and receiving feedback data of the server;
and the creating module is used for executing the current creating step according to the feedback data, and then the obtaining module obtains the next creating step from the creating step sequence until all creating steps of the creating step sequence are completed so as to create the promotion data.
11. An electronic device, comprising: a memory, a processor, and a promotional data creation program stored on the memory and executable on the processor, the promotional data creation program when executed by the processor implementing the promotional data creation method of any of claims 1 to 9.
12. A computer-readable storage medium, characterized in that a promotion data creation program is stored thereon, which realizes the promotion data creation method according to any one of claims 1 to 9 when executed by a processor.
CN202011398613.7A 2020-12-02 2020-12-02 Popularization data creation method and system Active CN112435071B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011398613.7A CN112435071B (en) 2020-12-02 2020-12-02 Popularization data creation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011398613.7A CN112435071B (en) 2020-12-02 2020-12-02 Popularization data creation method and system

Publications (2)

Publication Number Publication Date
CN112435071A true CN112435071A (en) 2021-03-02
CN112435071B CN112435071B (en) 2024-02-23

Family

ID=74691815

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011398613.7A Active CN112435071B (en) 2020-12-02 2020-12-02 Popularization data creation method and system

Country Status (1)

Country Link
CN (1) CN112435071B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112990979A (en) * 2021-04-01 2021-06-18 上海哔哩哔哩科技有限公司 Data processing method and device

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102187357A (en) * 2008-10-17 2011-09-14 三星电子株式会社 Apparatus and method for measuring advertising metrics
CN105263030A (en) * 2015-09-17 2016-01-20 北京暴风科技股份有限公司 Advertisement synthesizing and displaying method and system
CN107092501A (en) * 2017-03-20 2017-08-25 武汉斗鱼网络科技有限公司 The implementation method and device of advertisement general-purpose interface in a kind of android system
CN107659831A (en) * 2017-05-19 2018-02-02 腾讯科技（北京）有限公司 Media data processing method, client and storage medium
CN107734397A (en) * 2017-10-25 2018-02-23 深圳市雷鸟信息科技有限公司 Television advertisement obtaining and displaying method, advertisement server, television and system
CN108230024A (en) * 2017-12-29 2018-06-29 北京皮尔布莱尼软件有限公司 Automotive engine system is launched based on the advertisement that clue is collected
CN108269060A (en) * 2018-01-09 2018-07-10 百度在线网络技术（北京）有限公司 Advertising contract system
CN109299983A (en) * 2018-09-30 2019-02-01 北京金山安全软件有限公司 Mobile application advertisement generation method and device, electronic equipment and storage medium
CN111724206A (en) * 2020-06-18 2020-09-29 五八有限公司 Advertisement processing method, responsibility chain object generation method, device, equipment and medium

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102187357A (en) * 2008-10-17 2011-09-14 三星电子株式会社 Apparatus and method for measuring advertising metrics
CN105263030A (en) * 2015-09-17 2016-01-20 北京暴风科技股份有限公司 Advertisement synthesizing and displaying method and system
CN107092501A (en) * 2017-03-20 2017-08-25 武汉斗鱼网络科技有限公司 The implementation method and device of advertisement general-purpose interface in a kind of android system
CN107659831A (en) * 2017-05-19 2018-02-02 腾讯科技（北京）有限公司 Media data processing method, client and storage medium
CN107734397A (en) * 2017-10-25 2018-02-23 深圳市雷鸟信息科技有限公司 Television advertisement obtaining and displaying method, advertisement server, television and system
CN108230024A (en) * 2017-12-29 2018-06-29 北京皮尔布莱尼软件有限公司 Automotive engine system is launched based on the advertisement that clue is collected
CN108269060A (en) * 2018-01-09 2018-07-10 百度在线网络技术（北京）有限公司 Advertising contract system
CN109299983A (en) * 2018-09-30 2019-02-01 北京金山安全软件有限公司 Mobile application advertisement generation method and device, electronic equipment and storage medium
CN111724206A (en) * 2020-06-18 2020-09-29 五八有限公司 Advertisement processing method, responsibility chain object generation method, device, equipment and medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112990979A (en) * 2021-04-01 2021-06-18 上海哔哩哔哩科技有限公司 Data processing method and device

Also Published As

Publication number Publication date
CN112435071B (en) 2024-02-23

Similar Documents

Publication Publication Date Title
CN109600669B (en) Object playing monitoring method and device, storage medium and processor
US20110246294A1 (en) System and method for content management and distribution
CN109542468B (en) Application program release method and device and electronic equipment
CN110544134A (en) resource processing method and device and computer storage medium
CN108347413B (en) Media content delivery method, device and system
CN107590682B (en) Advertisement putting method, server, hotspot device and system
CN112435071B (en) Popularization data creation method and system
CN111724206B (en) Advertisement processing method, responsibility chain object generating method, apparatus, device and medium
CN113225694A (en) Short message group sending method and device and computer equipment
CN107872483B (en) Media content pushing method, device and system
CN111784326A (en) Picture processing method and device and computer equipment
CN111865753B (en) Method and device for determining parameters of media information, storage medium and electronic device
CN109815106B (en) Interactive function testing method and device of information delivery platform
CN111008887A (en) Skill service bidding system
CN114169924A (en) Advertisement full-link automatic verification method and device and computing equipment
CN114254991A (en) Target object reporting method, device and equipment
CN112767039A (en) Method, device, equipment and medium for generating advertising machine delivery order
CN109934609B (en) Advertisement data association method and device, computer equipment and storage medium
CN113450062A (en) Project information processing method, system, electronic device and storage medium
CN111222065A (en) Information display method and device, electronic equipment and medium
CN114897415B (en) Product demand platform management method, device, terminal and storage medium
EP3975099A1 (en) Method and server for automatic matchmaking for new project in component e-commerce platform
CN112004121B (en) Information publishing method, system and playing terminal
CN108460575B (en) Written document generation method and device, terminal equipment and storage medium
CN111382923B (en) Online profit method and device for picture copyright

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
GR01 Patent grant
GR01 Patent grant