Adobe Campaign is an enterprise marketing automation platform that lets you design, orchestrate, and deliver personalized messages across email, SMS, push notifications, and direct mail from a single system. It works by combining a centralized customer database with a visual workflow engine, so you can build audiences, set up multi-step campaigns, and trigger messages based on customer behavior, all without switching between disconnected tools.
The Core Components
Adobe Campaign revolves around three pieces working together: a customer data layer, a workflow engine, and delivery channels. The data layer stores customer profiles and all their associated information (demographics, purchase history, engagement data). The workflow engine is a visual canvas where you drag and drop activities to define who gets targeted, what logic applies, and which messages go out. The delivery channels are the actual outputs: email, SMS, Android and iOS push notifications, and direct mail.
Adobe Campaign v8, the current version, runs on cloud-scale database technology. Adobe reports batch processing throughput of up to 20 million operations per hour and transactional message throughput of 1 million per hour. In practical terms, this means large-scale segmentation and message preparation happen quickly even when you’re working with millions of profiles.
You interact with the platform through either a desktop client console or a web-based interface. The client console offers deeper administrative and technical controls, while the web interface is designed for marketers who primarily need to build campaigns, review reports, and manage audiences.
How Customer Data Is Organized
Everything in Adobe Campaign starts with profiles. A profile is a record representing a single person, containing fields like name, email address, phone number, city, age, gender, and any custom attributes your business tracks. These profiles live in a structured database built on schemas, which are essentially blueprints that define what data fields exist and what type of data each field accepts (text, number, date, and so on).
You can extend the default profile schema with custom fields. If your business needs to track loyalty tier, subscription type, or product preferences, you add those as custom fields. The system enforces data consistency: if a field is defined as a date, it won’t accept a text string.
Data flows into Adobe Campaign through several paths. You can import files directly, sync data from Adobe Experience Platform, pull records from external databases through dedicated connectors, or use REST APIs to push data in from other systems. When integrating with Adobe Experience Platform, campaign log data (delivery events, tracking clicks, opens) is structured using XDM schemas and stored as datasets in the platform’s data lake. This lets you combine campaign engagement data with broader customer behavior data from other Adobe tools.
Building Campaigns With Workflows
The workflow editor is where campaigns take shape. It’s a visual canvas where you place activity blocks and connect them in sequence. Activities fall into three categories.
Targeting activities define who receives your campaign. The “Build audience” activity lets you select an existing audience or create a new one using a query builder. You set conditions like “customers who purchased in the last 30 days” or “subscribers in a specific loyalty tier.” The “Split” activity segments that audience into subsets, so you can send different messages to different groups. “Combine” lets you merge, intersect, or exclude audiences from one another. If you want to remove duplicate records, there’s a dedicated “Deduplication” activity.
Channel activities define what gets sent. You drop an Email, SMS, or Push notification block onto the canvas and configure the message content, subject line, sender information, and personalization tokens. Personalization tokens pull data directly from profile fields, so each recipient sees their own name, relevant product recommendations, or location-specific offers.
Flow control activities manage timing and logic. You can set wait periods between steps, add conditional branches that route profiles down different paths based on their behavior, or use an “External signal” activity to trigger one workflow from another workflow or an API call. This is how you build multi-step journeys: send an email, wait three days, check if the recipient opened it, then send a follow-up SMS to non-openers and a different email to openers.
Data management activities handle the plumbing between steps. “Enrichment” adds extra data columns to your working population, so you can pull in purchase history or web browsing data mid-workflow. “Update data” writes changes back to the database in bulk. “Load file” and “Transfer file” let you bring in or export data from external systems via SFTP or HTTP. “Incremental query” is useful for recurring campaigns because it automatically excludes profiles that were already processed in previous runs, targeting only new records each time.
Cross-Channel Delivery
Adobe Campaign treats each message as a “delivery.” A single workflow can include multiple deliveries across different channels. You might start with an email, follow up with a push notification, and send an SMS as a final reminder, all orchestrated in one workflow with timing logic between each step.
For each channel, the platform handles rendering, personalization, and sending. Email deliveries support HTML templates with dynamic content blocks that change based on profile attributes. Push notifications on Android and iOS support rich content including images, buttons, countdown timers, and sounds. SMS deliveries handle character limits and encoding automatically.
Transactional messages work differently from marketing campaigns. These are triggered in real time by specific events, like a purchase confirmation, password reset, or shipping notification. Your application sends an event to Adobe Campaign via API, and the platform generates and delivers the personalized message immediately. Peak transactional volume is capped at 50,000 messages per hour under the standard product description.
Real-Time Triggers With Adobe Analytics
One of Adobe Campaign’s more powerful integrations is with Adobe Analytics through a feature called Triggers. This connection monitors user behavior on your website and automatically fires a campaign action when specific conditions are met. For example, if a shopper adds items to a cart and leaves without purchasing, Analytics detects the abandonment event and passes it to Campaign, which then sends a recovery email.
The integration works through a pipeline process that runs continuously on the Campaign server. It connects to Adobe Experience Cloud, retrieves trigger events, and processes them immediately. Typical response time from the triggering event to the marketing action is less than one hour. Setting up Triggers requires an Adobe Experience Cloud Organization ID, developer access to the relevant Analytics product profile, and an OAuth authentication project that connects the two systems.
Reporting and Optimization
Adobe Campaign v8 includes dynamic reporting that updates in real time. Reports cover standard email metrics like opens, clicks, bounces, and unsubscribes, but also layer in profile dimensions. You can break down campaign performance by gender, city, age group, or any custom profile attribute, which helps you understand not just how a campaign performed overall but which segments responded best.
Centralized branding controls let you define visual and technical guidelines (logos, email sender addresses, URL domains) that apply consistently across all campaigns. This prevents individual marketers from accidentally sending messages with inconsistent branding or unauthorized sender domains.
How Licensing Works
Adobe Campaign is licensed based on the number of active profiles in your database. An active profile is any profile you’ve attempted to contact through any channel in the past 12 months, charged in increments of 1,000. Your active profile tier determines the infrastructure resources allocated to your instance, including peak email sending volume. Organizations with fewer than 1 million active profiles get a peak volume of 1 million emails per hour, while those at the 50 to 100 million profile tier can send up to 10 million emails per hour.
Additional components are licensed separately. Database storage is measured in gigabytes per year. Engine calls, which are server-side API calls for things like survey processing, web app registrations, and data extraction, must be licensed in packs of 5,000 per day. Other add-ons include dedicated IP addresses, inbox rendering tests, additional SFTP accounts, and domain delegations. Pricing is not publicly listed and is negotiated directly with Adobe based on your profile volume and channel needs.