Multi-platform aggregated short episode promotion management method and system and storage medium

Abstract

The invention relates to the technical field of Internet, in particular to a multi-platform aggregated short play promotion management method and system and a storage medium, and aims to solve the technical problems of resource dispersion, high copyright risk, inaccurate attribution and complex commission settlement in existing short play promotion. The method comprises the steps that after an operation instruction is received, content resources are synchronized from an external short episode platform, and the content resources are presented to a front end after persistent storage and hotspot caching; after an episode selection instruction is received, promotion channel information and a promoter account are bound through a reporting interface, a unique promotion identifier is generated, behavior data generated by a user through the identifier are captured, income attribution is completed, and attribution order data are obtained; and calculating a commission based on the attribution order data and a preset commission extraction proportion, storing a result and pushing the result to the promoter. According to the invention, resource aggregation efficiency, copyright compliance, attribution accuracy and settlement flexibility can be guaranteed, and the overall efficiency and reliability of movie promotion management are significantly improved.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a method, system, and storage medium for promoting and managing short dramas across multiple platforms. Background Technology

[0002] Against the backdrop of explosive growth in the overseas short-drama market, efficient marketing and accurate commission settlement have become core links in the industry chain. However, current related technical solutions have many significant flaws, severely restricting industry development. When promoters promote content on multiple platforms such as ReelShort and ShortTV, they need to frequently switch between the backends of each platform. Due to the lack of a unified aggregation platform, short-drama resources, promotional materials, and official event information are scattered, causing promoters to spend a lot of time screening content and managing multiple accounts, resulting in low decision-making efficiency and difficulty in achieving economies of scale. At the same time, static promotional links cannot accurately attribute order revenue to specific promoters, their teams, and promotional channels. When promoting through multi-level teams or mixed channels, the source of conversion is unclear, which not only causes opaque commission settlement and disputes, but also makes it impossible to analyze the promotion effect in detail to optimize strategies. Short-drama copyright management is strict. Promoters editing their own materials can easily lead to complaints, resulting in video removal or even account suspension. Existing technology lacks a reporting and copyright protection mechanism deeply integrated with the promotion process. Platforms rely on manual review and post-processing, which is inefficient and lacks pre-warning. Promoter authorization certificates also rely on manual communication, resulting in high management costs. In the team leader-member promotion model, the existing system has rudimentary functions, making it difficult to dynamically filter and display data within the permission range of different roles such as super admin, administrator, and team leader. Rigid permissions or the need for extensive custom development hinder team leaders from efficiently managing members and adjusting incentive policies, and administrators struggle to fully grasp business data. The system also suffers from insufficient scalability. The massive amounts of data generated by promotions, such as clicks, registrations, and recharges, make it difficult for traditional databases to support multi-dimensional queries and large-scale export requirements, resulting in slow system response or even crashes, impacting real-time data visualization and the timeliness of operational decisions. Furthermore, existing systems often employ tightly coupled, single-architecture designs, with modules such as the library and data dashboards being highly dependent. Any modification or upgrade can easily trigger systemic risks, preventing independent development and deployment of modules and hindering technological iteration and long-term stable operation. Summary of the Invention

[0003] In view of this, the purpose of this invention is to propose a multi-platform aggregated short drama promotion management method, system and storage medium to solve all or one of the above-mentioned technical problems.

[0004] To achieve the above objectives, this invention provides a method for managing the promotion of short dramas across multiple platforms, comprising the following steps: S1. After receiving the user's operation instructions, synchronize content resources from the external short drama content platform, persistently store the synchronized content resources in the data storage unit, cache frequently accessed content resources in the high-speed cache unit, and present the synchronized content resources to the front end. S2. After receiving the series selection instruction from the promoter, receive the promoter's promotion channel information through the reporting interface, bind and store it with the promoter's account, generate a unique promotion identifier, capture the behavior data carrying the promotion identifier when a behavior is generated through the promotion identifier, associate and record the revenue data generated by the behavior with the promoter's account, and obtain the attributed order data. S3. Calculate commissions based on the attributed order data and the preset commission rates at each level, and store and push the calculation results.

[0005] Preferably, this method further includes: S4. All data requests received by the management terminal from users undergo permission verification. The permission verification is based on the role-based access control model and the preset team hierarchy, dynamically generates data filtering rules, and applies the filtering rules to the user's data requests to obtain only the data within the user's permission range. After aggregating and calculating the data acquisition results, they are presented in a visual format for management to view.

[0006] Preferably, in step S1, the content resources include the latest TV series, materials, and event information; the frequently accessed content resources include information on popular TV series.

[0007] Preferably, in step S1, the synchronization of content resources from the external content platform adopts an automated synchronization pipeline based on distributed task scheduling, and the synchronization process includes: Configure a distributed task to be executed once at a set time in the distributed task scheduling platform. When there are multiple executor instances, the synchronous task will be automatically assigned. Within the task executor, an independent asynchronous thread is created for each short drama content platform, and each asynchronous thread concurrently pulls the latest content resources from the corresponding platform; After receiving the latest content data, data cleaning, deduplication, and formatting operations are performed. Deduplication is achieved by generating a unique fingerprint through content identification information and comparing it. The newly added or updated content resources after data cleaning, deduplication, and formatting are then batch inserted or updated into the data storage unit.

[0008] Preferably, step S2 specifically includes: After receiving the TV series selection instruction from the promoter, the user ID, TV series ID, promotion platform identifier, and timestamp are hashed or encoded using a specific algorithm to generate a globally unique tracking ID as the unique promotion identifier. The unique promotional identifier is used as the key, and its associated metadata is used as the value. The information is stored in the cache unit and a preset expiration time is configured. A unique promotional identifier is embedded as a parameter in the promotional short link. After the user clicks on the promotional short link, the unique promotional identifier is sent back through the callback interface of the external short drama content platform along with the user's behavior on the third-party short drama platform, including but not limited to browsing, downloading, registering, and recharging. After receiving the callback notification, parse the unique promotion identifier, query the cache, and associate the corresponding revenue data of the behavior with the corresponding promoter account to complete the attribution.

[0009] Preferably, the callback interface of the external short drama content platform returns the following: For third-party platforms that do not provide callback notifications, configure a polling task to be executed once every set time. The polling task calls the order query interface of the external short drama content platform to pull recent orders and compares the order ID and unique promotion identifier to identify new orders. To support callbacks, a standardized HTTP Webhook endpoint is configured for external short drama content platforms. When a user makes a recharge, the order data containing a unique promotional identifier is actively pushed to the standardized HTTP Webhook endpoint through the external short drama content platform.

[0010] Preferably, this method further includes: When processing orders, idempotency checks are performed to ensure that the same order is not counted repeatedly by verifying whether the unique promotional identifier for the third-party order already exists.

[0011] Preferably, in step S3, the commission calculation based on the attributed order data and the preset commission rates at each level includes: The system includes a user table and a commission rate table. The user table establishes and stores a tree-like hierarchical relationship through the parent_id or path field. The commission rate table is configured with user_id, platform, rate, and start_time fields to achieve versioned management of commission rates. After order completion and attribution, the corresponding promoter is determined based on the unique promotion identifier. The path field of the promoter user in the user table is queried, and all its superiors are traversed from bottom to top. For each user on the path, the corresponding effective commission rate is queried from the commission rate table based on the order time and content platform information. The commission due to each level of user is calculated according to the preset settlement rules.

[0012] This invention also provides a multi-platform aggregated short drama promotion management system, which includes a resource aggregation module, a promotion management module, a business logic core, a data storage unit, a high-speed caching unit, a data intelligence module, and a commission calculation module; The resource aggregation module is used to receive user operation instructions, synchronize content resources from external short drama content platforms, persistently store the synchronized content resources in the data storage unit, cache frequently accessed content resources in the high-speed cache unit, and present the synchronized content resources to the front end. The promotion management module is used to receive the promotion channel information of the promoter through the reporting interface, bind and store it with the promoter's account, generate a unique promotion identifier, and capture the behavior data carrying the promotion identifier when the promoter generates behavior through the promotion identifier and send it to the business logic core. The core of the business logic is used to parse the behavioral data captured by the promotion management module, associate the revenue data with the promoter's account to complete the attribution, generate attribution order data and send it to the commission calculation module; The commission calculation module is used to receive the attribution order data sent by the business logic core and complete the commission calculation in combination with the preset commission rates at each level. The data intelligence module is used to receive the calculation results from the commission calculation module and the order data attributed by the core business logic, and to store and push the calculation results.

[0013] The present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method.

[0014] The beneficial effects of this invention are: 1. Centralized and intelligent management of promotional resources has been achieved, greatly improving promotional efficiency. By building a unified short drama aggregation platform (corresponding to the "Homepage" and "Drama Library" modules in the front-end project), short drama resources, official activities, and free materials scattered across multiple platforms are integrated in one stop. Promoters can complete the entire process of "selecting dramas - obtaining materials - generating links" without switching between multiple back-ends, and quickly locate high-value content based on the platform's trending lists and search functions. This fundamentally solves the problem of inefficient decision-making caused by resource dispersion, and significantly reduces the promotion threshold and time cost.

[0015] 2. A precise, transparent, and traceable promotion attribution and commission settlement system has been established. This invention ensures that the entire behavioral chain from user clicks and registration to recharge can be accurately tracked and attributed by generating a unique promotion link and password for each promoter and each short drama (corresponding to the "Short Drama Details" and "Data Center" modules). Combined with the "Short Drama Data" and "Distribution Data" modules in the backend, revenue data is presented in real time and transparently to promoters and their team leaders with the appropriate permissions, effectively avoiding settlement disputes, enhancing platform trust, and providing a data foundation for precise optimization of promotion strategies.

[0016] 3. A copyright compliance protection mechanism combining pre-emptive prevention and post-event management has been established. By integrating the "account reporting" function, promotion channel information is pre-registered in the system, forming a linkage basis with copyright holders, which greatly reduces the risk of promotional content being removed due to copyright issues. For platform administrators, this mechanism enables visualized management of promotion channels, shifting from reactive post-event handling to proactive pre-event compliance, effectively protecting the common interests of the platform and promoters, and reducing potential legal risks and economic losses.

[0017] 4. It achieves flexible, efficient, and secure multi-level team management and data access control. The backend management system (corresponding to the "Member Management" module) is designed based on the RBAC (Role-Based Access Control) model, dynamically and in real-time filtering data according to the hierarchical relationship of "Super Administrator - Administrator - Team Leader - Team Member." Team leaders can efficiently manage team members and adjust commission rates, while senior managers have a comprehensive overview. This granular access control design ensures data security (different roles only see the data they need) while also providing the organizational structure with great flexibility, supporting rapid business expansion and large-scale management.

[0018] 5. Through optimized technical architecture and asynchronous processing mechanisms, the system's high performance and stability under high concurrency and large data volumes are ensured. This invention adopts the concepts of front-end and back-end separation and microservices, splitting the system into multiple independently operable modules (which also lays the foundation for software copyright separation). The back-end utilizes a series of technologies such as Redis caching of hot data, database indexing to optimize queries, and XXL-Job asynchronous processing of large data export tasks (corresponding to the "Export List" module), effectively solving the performance bottleneck problem of massive data querying and processing, ensuring the real-time performance of the data visualization dashboard and the system stability of large-scale data export, and providing a smooth user experience. Attached Figure Description

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

[0020] Figure 1 This is a schematic diagram of the short drama promotion management method according to an embodiment of the present invention; Figure 2 This is a system block diagram of the short drama promotion and management method according to an embodiment of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments.

[0022] It should be noted that, unless otherwise defined, the technical or scientific terms used in this invention should have the ordinary meaning understood by one of ordinary skill in the art to which this invention pertains. The terms "first," "second," and similar terms used in this invention do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0023] Example 1: This embodiment 1 provides a method for managing the promotion of short dramas across multiple platforms, such as... Figure 1 As shown, the specific steps include: S1. After receiving the user's operation instructions, synchronize the latest drama series, materials and event information from the external short drama content platform, persist the synchronized latest drama series, materials and event information to the MySQL database, and cache frequently accessed content resources such as hot drama information to Redis to improve access speed, and present synchronized content resources to the front end. The synchronization of content resources from external content platforms employs an automated synchronization pipeline based on distributed task scheduling. The synchronization process includes: Configure a distributed task that executes every 30 minutes in the distributed task scheduling platform (XXL-JOB). When there are multiple executor instances, the synchronization task is automatically assigned (for example, instance A synchronizes with platform X, and instance B synchronizes with platform Y), thereby improving the overall synchronization efficiency and reliability.

[0024] Within the task executor, an independent asynchronous thread is created for each short drama content platform (such as DramaBox, FlickReels) to concurrently fetch the latest episode lists from each platform's official API or through secure and compliant methods. This avoids blocking the synchronization process of other platforms due to slow response times from one platform's API. After receiving the latest content data, data cleaning, deduplication, and formatting operations are performed. Deduplication is achieved by generating a unique fingerprint using the drama ID, name, and lead actor for comparison. The newly added or updated content resources after data cleaning, deduplication, and formatting are then batch-inserted or updated into the data database. This process ensures the timeliness and accuracy of the film library.

[0025] S2. After receiving the TV series selection instruction from the promoter, the system receives the promoter's promotion channel information through the reporting interface, binds and stores it with the promoter's account, and generates a unique promotion identifier (such as a link or password containing specific parameters). This identifier links the promoter's identity, TV series information, and even the reporting account. When a user performs actions such as clicking, registering, or recharging through external channels using this unique promotion identifier, the system captures the behavioral data carrying the promotion identifier, associates and records the revenue data generated by this behavior with the promoter's account, obtains attributable order data, and achieves precise tracking of promotion effects.

[0026] This step specifically includes: Upon receiving the TV series selection instruction from the promoter, a dedicated service is invoked to hash or encode the user ID, TV series ID, promotion platform identifier, and timestamp using a specific algorithm. This generates a globally unique tracking ID, which serves as the unique promotion identifier (UID), ensuring its uniqueness and unpredictability. Using a unique promotional identifier as the key and its associated metadata (user, series, platform, etc.) as the value, it is stored in a high-performance cache cluster (such as Redis) and configured with a preset expiration time for fast querying.

[0027] A unique promotion identifier is embedded as a parameter in the promotional short link (e.g., https: / / xxx.com / promote?uid=abc123). After the user clicks on the promotional short link, the unique promotion identifier is sent back through the callback interface of the external short drama content platform along with the user's behavior on the third-party short drama platform, including but not limited to browsing, downloading, registering, and recharging. After receiving the callback notification, the unique promotion identifier within it can be parsed to accurately attribute this recharge order or other valid behavior to the original promoter, thus completing the revenue association.

[0028] To address the varying levels of technical support from different third-party platforms, this approach employs a hybrid model of "callback as the primary method and polling as a secondary method" to construct a highly real-time order attribution system.

[0029] For third-party platforms that do not provide callback notifications, this method also utilizes XXL-JOB to establish a high-frequency polling task (e.g., every 5 minutes). The task will proactively call the third-party platform's order query interface to retrieve recent orders, and identify new orders and perform attribution processing by comparing fields such as order ID and UID.

[0030] For advanced platforms that support callbacks, this approach provides a standardized HTTP Webhook endpoint. When a user makes a payment, the third-party platform proactively pushes the order data (including the UID) to the promotion management system endpoint in real time, achieving millisecond-level attribution latency.

[0031] To prevent data duplication due to network retransmissions and other reasons, this method also incorporates idempotency checks when processing orders. By checking whether the third-party order ID already exists, it ensures that the same order will not be counted twice.

[0032] S3. Based on the attributed order data and preset commission rates at each level (such as the sharing ratio for the platform, team leader, and team member), the commission is calculated, and the results are stored and pushed. For large-scale data queries (such as exporting historical orders from several months), this method does not immediately perform time-consuming database operations. Instead, the export task is submitted to an asynchronous task processor (XXL-Job). The processor executes the query and file generation tasks asynchronously in the background without blocking other user operations. After the task is completed, the result file is stored on the server, and a download link is provided to notify the user. This mechanism effectively avoids the impact of massive data operations on system real-time performance and ensures system stability under high concurrency.

[0033] Specifically, to support complex multi-level and multi-type distribution relationships and flexible proportion strategies, this method is implemented through a carefully designed database table structure and settlement calculation engine.

[0034] This method pre-defines a user table and a commission rate table. The user table records basic information and uses the `parent_id` (parent ID) or `path` (hierarchical path, e.g., ` / 1 / 5 / 13 / `) field to visually establish and store a tree-like hierarchical relationship, facilitating the querying of all descendants of any node. The commission rate table is a core configuration table. Fields include `user_id` (user ID), `platform` (short drama platform), `rate` (ratio), and `start_time` (effective time). This design supports configuring different commission rates for the same user on different platforms and at different historical periods, achieving versioned management of rate configurations.

[0035] Once an order is attributed, the corresponding promoter (team member) is determined based on the unique promotion identifier. The path field of the promoting user is queried in the user table, and all its superiors (team leaders, administrators, etc.) are traversed from bottom to top. For each user on the path, the corresponding effective commission rate is queried in the commission rate table based on the order time and content platform information. The commission that each level of user should receive is calculated according to the preset settlement rules (such as differential calculation or fixed rate calculation).

[0036] This method uses scheduled tasks or triggers to pre-aggregate calculated commission data at all levels into a statistical table. When users query data on the front end, the page only needs to display the pre-calculated results, ensuring real-time data display and high performance.

[0037] This method deeply integrates the "account registration" process with promotional activities. Promoters register their accounts before generating promotional links; this information is stored and associated with all subsequent promotional links. When a partner platform receives a copyright complaint, it can quickly verify the promoter's identity based on the registered information, achieving both preventative measures and efficient post-complaint handling, thus reducing copyright risks.

[0038] As one implementation method, this method further includes: S4. All data requests received by the management terminal from users undergo permission verification. The permission verification is based on the role-based access control (RBAC) model and the pre-set team hierarchy, dynamically generating data filtering rules and attaching the filtering rules to the user's data requests to obtain only the data within the user's permission scope. For example, when a team leader requests to view "distribution data", the business logic core will automatically attach conditions when querying MySQL to retrieve only the data of its team members.

[0039] After aggregating and calculating the data acquisition results, they are presented in a visual format for management to view.

[0040] This "dynamic permission filtering" mechanism ensures that different roles can only view and operate data within their authorized scope, achieving secure data isolation and flexible management.

[0041] Example 2: This embodiment provides a multi-platform aggregated short drama promotion management system, used to execute the multi-platform aggregated short drama promotion management method provided in this embodiment, such as... Figure 2 As shown, the design adopts a microservice architecture with front-end and back-end separation. It can be divided into four logical layers: the front-end application platform, the back-end core system, the functional module cluster, and the external system that interacts with the outside world.

[0042] The front-end application platform consists of a user promotion client (front-end, typically an H5 page or cross-platform app) for promotional users and a back-end management client (back-end) for operations and management personnel. Both ends interact with the back-end through API interfaces, achieving separation of display and operation.

[0043] The backend core system is responsible for all core business logic, data processing and access control, including API gateway, core business logic, identity authentication and permission verification module, data persistence layer (MySQL database), high-speed caching unit (Redis) and asynchronous task processing unit; The functional module cluster includes a resource aggregation module, a promotion management module, a data intelligence module, and a permission management module.

[0044] The resource aggregation module receives user commands, synchronizes content resources from external short drama content platforms, persistently stores the synchronized content resources in the data persistence layer, and caches frequently accessed content resources in the high-speed cache unit. It then presents the synchronized content resources to the front end. Finally, the front end presents a unified resource center to promoters through categorization, sorting, and search, thus solving the technical problem of resource dispersion.

[0045] The promotion management module is used to receive the promotion channel information of promoters through the reporting interface, bind and store it with the promoter's account, generate a unique promotion identifier, and capture the behavior data carrying the promotion identifier when the promoter takes action through the promotion identifier and send it to the business logic core. After a team leader or administrator logs into the backend management interface, all their data requests first pass through the identity authentication and permission verification module. This module dynamically generates data filtering rules based on the RBAC (Role-Based Access Control) model and pre-defined team hierarchical relationships. For example, when a team leader requests to view "distribution data," the core business logic automatically adds conditions when querying MySQL, retrieving only data from their subordinate team members. After aggregation and calculation, the query results are presented in chart form on the data dashboard through the data intelligence module. This "dynamic permission filtering" mechanism ensures that different roles can only view and operate data within their authorized scope, achieving secure data isolation and flexible management. These permissions can be configured through the permission management module.

[0046] The core of the business logic is used to parse the behavioral data captured by the promotion management module, associate the revenue data with the promoter's account to complete the attribution, generate attribution order data and send it to the commission calculation module; The commission calculation module is used to receive the attribution order data sent by the business logic core and complete the commission calculation by combining the preset commission rates at each level. The data intelligence module is used to receive the calculation results from the commission calculation module and the order data attributed by the core business logic, and to store and push the calculation results.

[0047] Example 3: This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in Embodiment 1.

[0048] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0049] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0050] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0051] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0052] The implementation of all or part of the processes in the methods of the above embodiments can also be accomplished by a computer program product. When the computer program product is run on a terminal device, the terminal device can implement the steps in the various method embodiments described above.

[0053] The embodiments described above are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for managing the promotion of short dramas across multiple platforms, characterized in that, Includes the following steps: S1. After receiving the user's operation instructions, synchronize content resources from the external short drama content platform, persistently store the synchronized content resources in the data storage unit, cache frequently accessed content resources in the high-speed cache unit, and present the synchronized content resources to the front end. S2. After receiving the series selection instruction from the promoter, receive the promoter's promotion channel information through the reporting interface, bind and store it with the promoter's account, generate a unique promotion identifier, capture the behavior data carrying the promotion identifier when a behavior is generated through the promotion identifier, associate and record the revenue data generated by the behavior with the promoter's account, and obtain the attributed order data. S3. Calculate commissions based on the attributed order data and the preset commission rates at each level, and store and push the calculation results.

2. The short drama promotion management method based on multi-platform aggregation according to claim 1, characterized in that, The method further includes: S4. All data requests received by the management terminal from users undergo permission verification. The permission verification is based on the role-based access control model and the preset team hierarchy, dynamically generates data filtering rules, and applies the filtering rules to the user's data requests to obtain only the data within the user's permission range. After aggregating and calculating the data acquisition results, they are presented in a visual format for management to view.

3. The short drama promotion management method based on multi-platform aggregation according to claim 1, characterized in that, In step S1, the content resources include the latest TV series, materials, and event information; the frequently accessed content resources include information on popular TV series.

4. The short drama promotion management method based on multi-platform aggregation according to claim 1, characterized in that, In step S1, the synchronization of content resources from the external content platform adopts an automated synchronization pipeline based on distributed task scheduling. The synchronization process includes: Configure a distributed task to be executed once at a set time in the distributed task scheduling platform. When there are multiple executor instances, the synchronous task will be automatically assigned. Within the task executor, an independent asynchronous thread is created for each short drama content platform, and each asynchronous thread concurrently pulls the latest content resources from the corresponding platform; After receiving the latest content data, data cleaning, deduplication, and formatting operations are performed. Deduplication is achieved by generating a unique fingerprint through content identification information and comparing it. The newly added or updated content resources after data cleaning, deduplication, and formatting are then batch inserted or updated into the data storage unit.

5. The short drama promotion management method based on multi-platform aggregation according to claim 1, characterized in that, Step S2 specifically includes: After receiving the TV series selection instruction from the promoter, the user ID, TV series ID, promotion platform identifier, and timestamp are hashed or encoded using a specific algorithm to generate a globally unique tracking ID as the unique promotion identifier. The unique promotional identifier is used as the key, and its associated metadata is used as the value. The information is stored in the cache unit and a preset expiration time is configured. A unique promotional identifier is embedded as a parameter in the promotional short link. After the user clicks on the promotional short link, the unique promotional identifier is sent back through the callback interface of the external short drama content platform along with the user's behavior on the third-party short drama platform, including but not limited to browsing, downloading, registering, and recharging. After receiving the callback notification, parse the unique promotion identifier, query the cache, and associate the corresponding revenue data of the behavior with the corresponding promoter account to complete the attribution.

6. The short drama promotion management method based on multi-platform aggregation according to claim 5, characterized in that, The callback interface returned through the external short drama content platform includes: For third-party platforms that do not provide callback notifications, configure a polling task to be executed once every set time. The polling task calls the order query interface of the external short drama content platform to pull recent orders and compares the order ID and unique promotion identifier to identify new orders. To support callbacks, a standardized HTTP Webhook endpoint is configured for external short drama content platforms. When a user makes a recharge, the order data containing a unique promotional identifier is actively pushed to the standardized HTTP Webhook endpoint through the external short drama content platform.

7. The short drama promotion management method based on multi-platform aggregation according to claim 5, characterized in that, The method further includes: When processing orders, idempotency checks are performed to ensure that the same order is not counted repeatedly by verifying whether the unique promotional identifier for the third-party order already exists.

8. The short drama promotion management method based on multi-platform aggregation according to claim 1, characterized in that, In step S3, the commission calculation based on the attributed order data and the preset commission rates at each level includes: The system includes a user table and a commission rate table. The user table establishes and stores a tree-like hierarchical relationship through the parent_id or path field. The commission rate table is configured with user_id, platform, rate, and start_time fields to achieve versioned management of commission rates. After order completion and attribution, the corresponding promoter is determined based on the unique promotion identifier. The path field of the promoter user in the user table is queried, and all its superiors are traversed from bottom to top. For each user on the path, the corresponding effective commission rate is queried from the commission rate table based on the order time and content platform information. The commission due to each level of user is calculated according to the preset settlement rules.

9. A short drama promotion management system that integrates multiple platforms, characterized in that, The system includes a resource aggregation module, a promotion management module, a business logic core, a data storage unit, a high-speed cache unit, a data intelligence module, and a commission calculation module. The resource aggregation module is used to receive user operation instructions, synchronize content resources from external short drama content platforms, persistently store the synchronized content resources in the data storage unit, cache frequently accessed content resources in the high-speed cache unit, and present the synchronized content resources to the front end. The promotion management module is used to receive the promotion channel information of the promoter through the reporting interface, bind and store it with the promoter's account, generate a unique promotion identifier, and capture the behavior data carrying the promotion identifier when the promoter generates behavior through the promotion identifier and send it to the business logic core. The core of the business logic is used to parse the behavioral data captured by the promotion management module, associate the revenue data with the promoter's account to complete the attribution, generate attribution order data and send it to the commission calculation module; The commission calculation module is used to receive the attribution order data sent by the business logic core and complete the commission calculation in combination with the preset commission rates at each level. The data intelligence module is used to receive the calculation results from the commission calculation module and the order data attributed by the core business logic, and to store and push the calculation results.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 8.

Images