Add Business Line to Campaign Management
Extended campaign flows to carry business-line context across budget-management pages and download workflows — with contract-first, cross-region delivery.
- Role
- Backend Engineer
- Timeline
- 2025–2026
- Team
- 3
- Domain
- E-Commerce / Campaign
- Stack
- 9 tech
- Status
- Live
Overview
This project added Business Line support inside the campaign management / budget-management platform ecosystem so campaign pages, product detail views, and download flows could correctly surface and process business-line data. I joined mid-flight and took ownership of the technical assessment, interface changes, and cross-team alignment.
Gallery
A backend has no screens, so its "UI" is the operational surface: the API contract, the download/ops flow, and release dashboards.
Problem & Solution
Existing campaign flows did not consistently carry business-line context through page rendering and download paths. That created risk for downstream teams, unclear interface expectations, and potential data-correctness issues when budget-management-platform-related features shipped.
I ran a high-level end-to-end assessment of the page download flow and the product detail page flow, identified the new columns and fields required, and updated the relevant RPC and HTTP contracts before downstream implementation. I aligned with service owners on data availability, presented the design to regional stakeholders, and defined a delivery timeline from assessment through release.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
A thin API layer resolves business-line context and calls the seller-profile-service over RPC for the required fields. The download service was extended to include business-line columns. Contracts were updated first to unblock downstream teams, and all paths run across multiple regions with Prometheus/Grafana monitoring.
Features
- Campaign pages show correct business-line context
- Consistent product detail experience
- Download files enriched with business-line columns
- Reliable page download flow
- Contract-first RPC & HTTP updates
- Cross-service business-line data propagation
- Multi-region compatibility
Tech Stack
Engineering Challenges
The download mechanism spanned multiple services and downstream dependencies. Fix: proactive stakeholder communication to clarify the flow, then update RPC contracts first so downstream teams could build against stable interfaces.
I joined after the project had started, with limited context. Fix: a fast end-to-end assessment plus a clear timeline from assessment to release to re-align PM, QA, and engineering across regions.
Outcomes
Lessons Learned
Joining a project mid-flight rewards fast context building and proactive communication. Prioritizing contract clarity and early risk identification (the download flow) kept the project continuous and reduced integration risk for everyone else.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.