
📣 Marketing, CRM & Support · Deployment · Pro
Where a marketing automation platform runs: tracking and APIs at the edge, journey workers, a message queue and channel providers.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment of a marketing automation platform on Azure: a CDN and Azure Front Door front the tracking API. AKS runs the tracking API, journey engine workers and the admin app. Azure Service Bus queues journey steps. Cosmos DB stores profiles and journeys; Azure SQL stores campaigns. Workers call SendGrid, an SMS provider and the WhatsApp API.
flowchart TB
V[Website Visitors] --> AFD[Azure Front Door and CDN]
M[Marketers] --> AFD
subgraph AZ[Azure Central India]
subgraph AKS[AKS Cluster]
TR[Tracking API]
ADM[Admin App]
JW[Journey Workers x4]
end
SB[Service Bus Queues]
COS[(Cosmos DB - profiles, journeys)]
SQL[(Azure SQL - campaigns)]
end
AFD --> TR
AFD --> ADM
TR --> COS
ADM --> SQL
ADM --> SB
SB --> JW
JW --> COS
JW --> SG[SendGrid]
JW --> SMS[SMS Provider]
JW --> WA[WhatsApp API]A customer data platform that joins a customer's activity from website, app, store and support into one profile, and sends audiences to marketing tools.
The states of a customer support ticket, from creation through assignment, waiting on the customer, resolution and reopening.
How an incoming support call is routed: caller recognition, IVR menu, self-service options and routing to the right skilled agent queue.
How a marketing email campaign is sent: audience built, consent checked, emails personalised and sent in batches, and opens and clicks tracked.
Tables for a B2B sales CRM: accounts, contacts, leads, opportunities moving through stages, activities and quotes.
How visitors flow from marketing channels to sign-ups, trials and paying customers in a month, to see which channel brings buyers, not just traffic.