isA Marketing

Multi-agent marketing platform with 8 specialized AI agents for automated campaign management, analytics, content, SEO, personalization, and compliance — plus CDP/PIM integrations and an autonomous brief-to-launch pipeline.

Overview

isA Marketing is an intelligent multi-agent system that automates marketing workflows end-to-end: campaign creation and management, analytics and reporting, audience insights, content and SEO optimization, real-time personalization, and compliance monitoring. Through natural language interaction, users can request any of these without needing technical expertise in data analysis or ad-platform APIs.

The platform runs as a single-container architecture where all agents operate in-process via the SwarmOrchestrator pipeline with shared state, communicating through NATS messaging and backed by PostgreSQL, Redis, Qdrant, and MinIO from the isA Cloud infrastructure.

Architecture

┌─────────────────────────────────────────────────────────┐
│                  Marketing Platform                      │
│                   API (Port 18792)                       │
└───────────────────────┬─────────────────────────────────┘
                        ↓
┌─────────────────────────────────────────────────────────┐
│           Orchestrator (Marketing Director)              │
│    Decision engine • A2A adapter • Shared state         │
└─┬────┬─────┬──────┬──────┬──────┬──────┬───────┬────────┘
  ↓    ↓     ↓      ↓      ↓      ↓      ↓       ↓
┌────┐┌────┐┌─────┐┌─────┐┌─────┐┌─────┐┌──────┐┌──────────┐
│Camp││Camp││Report││Audi.││Cont.││ SEO ││Person││Compliance│
│Mgr ││Anlst││Gen. ││Insig││Agent││Agent││alize ││  Agent   │
└────┘└────┘└─────┘└─────┘└─────┘└─────┘└──────┘└──────────┘
  │     │     │      │      │      │      │        │
  └─────┴─────┴──────┴──────┴──────┴──────┴────────┘
                     ↓
┌─────────────────────────────────────────────────────────┐
│         CDP / PIM Adapters (see below) + isA_Creative    │
│  Segment • RudderStack • Akeneo/Pimcore/Salsify • NATS   │
└───────────────────────┬───────────────────────────────────┘
                     ↓
┌─────────────────────────────────────────────────────────┐
│              External Integrations                       │
│  Google Ads • Facebook Ads • LinkedIn Ads               │
│  Google Analytics • HubSpot • Salesforce                │
└─────────────────────────────────────────────────────────┘
                     ↓
┌─────────────────────────────────────────────────────────┐
│              Infrastructure (isA Cloud)                  │
│  PostgreSQL • Redis • Qdrant • NATS • MinIO             │
└─────────────────────────────────────────────────────────┘

CDP and PIM Integrations

isA Marketing integrates with customer-data platforms (CDP) and product-information-management systems (PIM) through an adapter pattern, so a provider can be swapped without touching agent logic:

• CDP adapter — audience/event data in, campaign targeting out. Supported providers: a local placeholder (for development), Segment, and RudderStack. The CDP event bridge publishes provider webhook events onto NATS for the rest of the platform to consume.
• PIM adapter — product catalog data in, enriched campaign/personalization content out. Supported providers: a local placeholder, Akeneo, Pimcore, and Salsify. The PIM webhook bridge (POST /webhooks/pim) verifies Akeneo Events API callbacks and republishes them as NATS events.

Both adapters default to the placeholder provider for local development and swap to a real provider via configuration — no agent code changes needed.

Autonomous Brief-to-Launch Pipeline

A campaign brief (objective, target audience, product IDs, channels, budget, content types) can be run through a 12-stage, resumable pipeline that takes it from brief to a live, monitored campaign:

1. Brief received — a CampaignBrief is submitted.
2. Creative requested / received — the pipeline requests creative assets from isA_Creative over NATS.
3. Audience built — the CDP adapter builds the target audience segment.
4. Products enriched — the PIM adapter attaches product data for the campaign’s product_ids.
5. Personalized — the Personalization Agent generates per-user content variants from the combined CDP + PIM + campaign context.
6. Compliance checked — the Compliance Agent runs a guardian veto over the assembled campaign.
7. Approval pending / approved — a human approval gate, with configurable auto-approve thresholds (e.g. budget under a limit, audience under a size) and mandatory review for new channels or high-risk campaigns.
8. Launched — the Campaign Manager launches the campaign across the target ad platforms.
9. Monitoring / completed — ongoing performance monitoring with a feedback loop back into the pipeline.

Each stage is idempotent and the pipeline can resume from any point (e.g. after a transient failure or while waiting on human approval).

Brand Configuration

Service branding is wired through isa_common.BrandConfig, so per-edition brand values (name, logo, copy) propagate to this service the same way they do across the rest of the isA platform.

Key Features

Campaign Analytics

• Campaign metrics analysis and ROI calculation
• Conversion tracking and attribution modeling
• Campaign comparison and benchmarking
• Performance trend analysis

Report Generation

• Automated performance reports
• Executive summaries with AI-powered insights
• Multiple export formats (CSV, PDF)
• Standardized metrics and calculations

Audience Insights

• Segment analysis and profiling
• Cohort identification
• Behavioral analysis and targeting recommendations
• Cross-channel audience mapping

Content Management

• Content creation assistance and optimization
• Content performance tracking
• Cross-channel content coordination

SEO Optimization

• Search engine optimization analysis
• Keyword and ranking recommendations
• Technical SEO auditing

Compliance Monitoring

• Regulatory compliance checks
• Policy enforcement across campaigns
• Audit trail and reporting

Platform Integrations

Quick Start

# Clone the repository
git clone https://github.com/xenoISA/isA_Marketing.git
cd isA_Marketing
 
# Install dependencies
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
 
# Ensure isA Cloud infrastructure is running (PostgreSQL, Redis, Qdrant, NATS, MinIO)
 
# Start with Docker Compose
docker-compose up -d
 
# Or run directly
uvicorn src.orchestrator.main:app --port 18792 --reload

The service exposes a health check at http://localhost:18792/health.

Tech Stack

Project Structure

isA_Marketing/
├── src/
│   ├── api/                  # FastAPI routes
│   ├── orchestrator/         # Marketing Director, decision engine, A2A adapter
│   ├── campaign_analyst/     # Campaign metrics and ROI analysis
│   ├── campaign_manager/     # Campaign lifecycle management
│   ├── report_generator/     # Report creation and export
│   ├── audience_insights/    # Segment and cohort analysis
│   ├── content_agent/        # Content management and optimization
│   ├── seo_agent/            # SEO analysis and recommendations
│   ├── personalization_agent/ # Real-time per-user content variants (CDP + PIM + context)
│   ├── compliance_agent/     # Regulatory compliance monitoring
│   └── core/
│       └── services/         # CDP/PIM adapters + event bridges, autonomous_pipeline.py
├── tests/                    # Test pyramid (unit, component, integration, api, smoke)
├── config/                   # Service configuration (vibe.yaml)
├── deployment/               # Environment configs, requirements
├── docs/                     # Internal project documentation, PRD, design docs
├── k8s/                      # Kubernetes manifests
├── Dockerfile                # Container build
└── docker-compose.yml        # Local development

Roadmap