Define the campaign
An operator chooses the audience, language, format and regeneration rules.
How it works
The backend supports campaign create/update/copy operations and spreadsheet-based batch creation.
Service for generating creatives from sports events
An operations workspace that connects sports feeds, creative generation and advertising-platform lifecycle management.
Project overview
What the service does
An operator configures an advertising campaign once. The service checks a sports data feed, picks an eligible upcoming match, fills a text and image template, renders the image, then creates or updates the creative in the advertising platform. If there is no suitable match, the related live creative can be paused.
Campaign content changes with real-world events. Manually selecting events, preparing assets and reconciling advertising state makes the workflow difficult to maintain as the number of campaigns grows.
Who uses it
Advertising operations and media teams managing many campaigns whose text or image should follow changing sports events.
Input
- Campaign format, language, audience and event-selection rules.
- Sports feed data such as teams, start time and event status.
- Text and HTML image templates plus their assets.
Output
- Rendered text and image assets for an eligible event.
- A created or updated creative in the advertising platform.
- A pause or retry state when no event or an external request is available.
System requirements
- Campaigns have different audiences, languages and creative formats.
- Requests to the sports feed and ad platform follow their rate limits.
- If no match is available, the current creative can be paused.
- Operators can review campaign metrics and task errors in one interface.
01 / How the service works
Sports match → creative → advertising campaign
Process mapSolid line: normal flow · dashed line: retry or return
- INPUTCampaign settings
Format, language and event rules
ContinueLoad sports feed - SERVICELoad sports feed
Shared cache and provider limits
ContinueSuitable event? - DECISIONSuitable event?
Time window, team codes and priorities
yesFill text and templateno eventPause current creative - RESULTPause current creative
No eligible event was found
- STEPFill text and template
Localized copy and escaped template values
ContinueRender image - SERVICERender image
Browser converts HTML template to PNG
ContinueCreate and upload - SERVICECreate and upload
Call the advertising platform
ContinuePublication result - DECISIONPublication result
Success or external API failure
createdCreative activefailedUndo created object - RESULTCreative active
Local campaign state is synchronized
- STEPUndo created object
Best-effort compensation after failure
retryCreate and upload
02 / System architecture
Main components and their roles
Load the feed
Workers obtain the current sports data without needlessly repeating the same request.
How it works
The cache combines simultaneous requests for the same feed. A Redis limiter coordinates request rate and count across workers.
Select an event
The campaign selects an event that fits its time window and priorities.
How it works
Team-code availability, include/exclude windows and ordered priority groups constrain candidate selection. A missing event is distinct from a provider failure.
Build the creative
Localized text and a matching image are assembled from the chosen event.
How it works
Sports copy uses placeholders and length checks. HTML templates escape inserted values and render to PNG in Chromium. Promotional copy has a separate generator API path.
Synchronize assets
The system creates the remote creative, uploads its assets and activates it.
How it works
The service creates the ad, uploads its image and connects it to the local campaign.
Keep state relevant
Changed events trigger regeneration; missing suitable events can pause creatives.
How it works
Task history and the selected event determine when to update, pause or reactivate a creative.
Review operations
Operators review campaign metrics and task failures.
How it works
DuckDB and Pandas prepare campaign reports. Task logs and notifications show retries and final errors.
03 / Implementation details
Engineering decisions
Coordinate provider load
Shared admission control and single-flight caching address limits across workers, rather than per-process counters alone.
Model the creative lifecycle
Selection, regeneration, pause and reactivation are explicit parts of the campaign workflow.
Separate generation paths
Sports templates and browser-rendered images have different behavior from the promotional text generator integration.
Software development for business
Have a project in mind?
Tell me what the application should do, how the team works today and which requirements or deadlines matter.