Use case
Campaign results video for Cybersecurity
Summarize campaign performance as soon as a campaign ends.
Why Cybersecurity teams still ship reports manually
- Security updates are noisy and hard to summarize.
- Stakeholders need digestible incident/status reporting.
- Manual summaries are inconsistent under pressure.
- Teams need reliable communication during events.
Automate campaign results video with an API
- Trigger the workflow when a campaign ends happens.
- POST structured data to /render using template campaign-results-v1.
- Render asynchronously at scale and receive a webhook when the MP4 is ready.
- Deliver the video via Slack, email, or status page.
Input (structured data)
{
"brand": "cybersecurity",
"data": {
"alerts": 1842,
"campaignId": "example-campaignId",
"coverage": "92%",
"criticalVulns": 11,
"highlight": "alerts",
"incidents": 3,
"kpis": {
"alerts": 1842,
"coverage": "92%",
"criticalVulns": 11,
"incidents": 3,
"mttr": "2h 14m"
},
"mttr": "2h 14m",
"period": "2026-01-14"
},
"template": "campaign-results-v1"
}Output (deterministic MP4)
- 30-60s MP4 video
- Campaign KPI summary
- Visual comparison vs benchmarks
- Webhook with output URL
Architecture
Data source / event | v Rendivia Render API | v Queue + Workers | v Remotion templates | v Branded MP4 + webhook
How it works
Collect KPIs
Aggregate reach, conversion, and spend metrics.
Render
POST to /render with campaign-results-v1.
Async delivery
Receive a webhook with the MP4 URL.
Distribute
Share internally or to clients automatically.
Benefits
- Create consistent incident and status updates.
- Automate post-incident communication.
- Deterministic output you can trust in production.
- A repeatable workflow triggered by a campaign ends.
Common questions
Can I include benchmarks?
Yes. Include target values and we render comparisons.
Is it multi-campaign?
Call /render per campaign for deterministic outputs.
Related
Generate campaign results video via API
Create an API key and render your first campaign results video in minutes.
Get API key