Frequently Asked Questions faq

Adobe Campaign v8 is a powerful cross-channel marketing automation platform that helps you create, coordinate, and deliver personalized campaigns across email, mobile, social, and offline channels. It combines a robust marketing database, campaign orchestration engine, and real-time interaction capabilities to engage customers throughout their journey.

Key capabilities: Multi-channel campaign management, audience segmentation and targeting, workflow automation, personalization at scale, real-time and batch messaging, reporting and analytics, integration with Adobe Experience Cloud.

What makes v8 unique: Cloud-native architecture (Managed Cloud Services only), enterprise-scale performance powered by Snowflake database, automatic upgrades, enhanced security, and bi-directional integration with Adobe Experience Platform.

Ideal for: Enterprise marketing teams managing complex, high-volume campaigns across multiple channels and customer touchpoints.

Related topics:

Campaign v8 product description | What’s new in v8 | Get started guide

You can get the installation program and the client console from Adobe Download Center.

As an Admin user, access Adobe Software Distribution to download Adobe Campaign.

Learn more about the Distribution Center on this page.

You need to download and install Campaign client console to connect to Adobe Campaign. Learn more.

Starting Campaign v8.6 release, you have access to the Campaign Web user interface, available through the central Adobe Experience Cloud environment. Experience Cloud is Adobe’s integrated family of digital marketing applications, products, and services.

Learn how to connect to Adobe Experience Cloud, and access Adobe Campaign Web interface in this page. Learn more in the Adobe Campaign Web user interface documentation.

Related topics:

Install the client console | Campaign user interface | User permissions

Yes! Thanks to the integration with the IMS (Adobe Identity Management System), users connect to the Adobe Campaign console using their Adobe ID. This integration provides the following advantages:

• The same ID can be used for all Experience Cloud solutions.
• The connection is memorized when using Adobe Campaign with different integrations.
• Securer password management policy.
• Use of Federated ID accounts (external ID provider).

Learn more about accessing Campaign v8 with an Adobe ID.

Refer to this section to learn more about Adobe Campaign user interface basics.

Starting Campaign v8.6 release, you also have access to the new Campaign Web user interface, available through the central Adobe Experience Cloud environment.

Learn more in the Adobe Campaign Web user interface documentation.

As a Campaign administrator, you can set up permissions for users of your organization.

These are a set of rights and restrictions that authorize or deny to:

• Access to certain functionalities
• Access to certain data
• Create, modify and/or delete data

Related topics:

Get started with permissions | Manage user permissions | Add permissions on folders

Campaign offers multiple targeting methods to select the right audience for your messages:

Targeting methods:

• Query editor - Build audiences using visual filters on recipient attributes, behaviors, or demographics
• Lists - Use predefined static or dynamic recipient lists
• File import - Upload external recipient files for one-time campaigns
• Workflows - Create complex targeting logic with query, split, and enrichment activities
• Predefined filters - Apply ready-to-use filters (active customers, subscribers, VIPs)
• Segments from Adobe Experience Platform - Leverage unified profiles and real-time segments

You can combine multiple criteria (location, purchase history, engagement) and use exclusions, intersections, or unions to refine your audience.

Related topics:

Define audiences in Campaign v8 | Query editor | Target mappings

Creating your first email in Campaign v8 is straightforward. You start from a template, select your target audience, design your content with personalization, test it with proofs, and then send. Campaign offers two interfaces for email creation: the full-featured Client console for advanced users and the modern Campaign Web UI for faster, more intuitive email building.

5 key steps:

1. Create delivery - Start from an email template or create from scratch
2. Define audience - Select recipients using queries, lists, or workflows
3. Design content - Use the email designer to create your message with personalization fields
4. Send test proofs - Validate rendering and content across devices and email clients
5. Analyze and send - Run delivery analysis to check for errors, then send your email

Related topics:

Email design and validation | Create first delivery | Delivery templates | Personalize content

To contact Adobe Customer Support, connect to Adobe Admin Console to create a case or start a chat session.

Requires individual accounts with correct permissions. If you can’t log in, request access via Experience League. Learn more

Alternatively, join Campaign Community to search for answers or ask experts.

Yes. Campaign v8 seamlessly integrates with Adobe Experience Cloud solutions for a unified marketing ecosystem.

Key integrations: Adobe Experience Platform (unified profiles, real-time data), Adobe Analytics (performance measurement), Adobe Target (personalization), Adobe Experience Manager (content management), Adobe Audience Manager (audience segments).

Setup: Requires Adobe IMS authentication, automatically configured for Campaign v8 Managed Cloud Services.

Related topics:

Adobe Campaign integrations | Connect with Adobe ID

Campaign v8 brings significant performance improvements but has some architectural differences from Campaign Classic v7, especially in FFDA deployments.

Key considerations:

• FFDA architecture - Uses cloud database (Snowflake) with different data access patterns
• Data updates - Should be done in workflows, not via direct database access
• Batch-optimized - Optimized for batch operations rather than high-frequency individual updates
• Not available in FFDA - Surveys, Marketing Resource Management (MRM), some specific connectors

Migration impact: Custom code using direct database writes needs refactoring; API integrations may need adaptation for batch processing.

These limitations are evolving as Adobe enhances v8. Consult latest documentation for current status.

Related topics:

Campaign v7 to v8 migration | FFDA architecture

Automated migration from an existing Campaign Classic v7 environment is not yet available.

Campaign v8 is only available as a Managed Cloud Service, and cannot be deployed on an on-premise or hybrid environments.

For more information about the migration process, reach out to your Adobe representative.

Learn more in the Campaign v8 vs Previous versions section.

Adobe Campaign is regularly updated. Minor versions are released every year with new features, improvements and fixes. In addition, we periodically release builds with cumulative fixes only.

This regular frequency of updates aims at getting the latest and greatest in your hands, keeping your environment secure and improving your experience with our product. This is the reason why we believe it is critical that you run the most recent version of Adobe Campaign.

Note: As a Managed Cloud Services user, your instance is upgraded by Adobe with new releases.

Learn more about Campaign versions and upgrades.

Stay informed about new Campaign releases through these channels:

• Adobe representative - Contacts you directly when a new version is available
• Release Notes - All versions and changes documented in Campaign Release Notes
• Adobe Priority Product Updates - Subscribe for email notifications
• Campaign Community - Join discussions for early updates

As a Managed Cloud Services user, Adobe handles upgrades and coordinates timing with you.

Related topics:

Release Notes | What’s new | Campaign versions and upgrades

Upgrading to the latest Campaign version is critical for security, performance, and support quality.

Key benefits:

• Improved security - Protection against vulnerabilities, latest patches, enhanced data protection
• Better support - Faster issue resolution, access to bug fixes, priority support on recent versions
• Enhanced performance - Database and workflow optimizations, better scalability, more reliable operations
• New capabilities - Latest features, improved Adobe Experience Cloud integrations, modern UI enhancements

Adobe strongly recommends running the most recent version. As a Managed Cloud Services customer, upgrades are performed by Adobe with minimal disruption.

Related topics:

Campaign versions and upgrades | What’s new | Compatibility matrix

As a Managed Cloud Services customer, Adobe manages the entire upgrade process with minimal impact on your operations.

Process:

1. Notification - Adobe notifies you weeks in advance
2. Planning - Schedule upgrade at optimal time with your Adobe representative
3. Preparation - Adobe prepares environment and validates
4. Execution - Adobe upgrades infrastructure with minimal downtime
5. Validation - Post-upgrade testing by Adobe
6. Client console upgrade - You upgrade your client consoles to match server version

Your responsibilities:

• Coordinate internal stakeholders for timing
• Upgrade client consoles to the new version
• Test campaigns and workflows after upgrade
• Report issues to Adobe Support

Adobe performs the infrastructure upgrade. You don’t need to perform any technical actions on servers.

Related topics:

Campaign versions and upgrades | Upgrade client console | Release Notes

Campaign v8 is built on a modern cloud-native architecture with significant improvements:

• Managed Cloud Services only - Fully hosted by Adobe (no on-premise/hybrid options)
• Superior performance - Up to 20 million operations/hour, with Full Federated Data Access (FFDA) architecture
• New Campaign Web UI - Modern, intuitive interface alongside the classic console
• Automatic upgrades - Always on the latest version with zero downtime
• Enhanced features - AI Assistant, rich push notifications, upgraded SMS, improved integrations with Adobe Experience Cloud

For Campaign Classic v7 users: Learn about transitioning from v7 to v8 including architecture changes, unavailable features, and migration considerations.

For Campaign Standard users: Discover the transition path to v8 and Campaign Standard migration guide.

Related topics:

Campaign v8 key capabilities | Campaign v8 architecture | Capability matrix | Guardrails and limitations

Campaign v8 is Adobe’s platform, ideal for organizations needing high-volume campaigns (20M operations/hour), modern web UI, cloud-native benefits, and long-term support.

Key benefits:

• For Campaign Standard users - Familiar Web UI, feature parity (Dynamic Reporting, REST APIs, Landing Pages), smooth data migration
• For Campaign Classic v7 users - Dual interface (console + Web UI), better performance, automatic upgrades, enhanced FFDA architecture

Consider migrating if you:

• Handle large data volumes or experience performance issues
• Want to reduce IT overhead and infrastructure management
• Need Adobe Experience Cloud/Platform integration
• Want future-proof technology with automatic updates

Next steps: Contact your Adobe representative to assess migration readiness and access migration tools.

Related topics:

From Campaign Classic v7 to v8 | Campaign Standard transition guide | Capability matrix

No. Campaign v8 is exclusively available as a Managed Cloud Service, fully hosted by Adobe.

Key benefits of Managed Cloud Services:

• Superior performance and scalability
• Automatic upgrades - always on the latest version
• Enhanced security with continuous monitoring
• No infrastructure management or IT overhead
• Built-in high availability and disaster recovery

Learn more about Campaign v8 architecture and the differences between Campaign v8 and Classic v7.

Migrating to Adobe Managed Services provides a strategic path from on-premise/hybrid v7 to the cloud, offering improved scalability, security, and reduced IT overhead. It’s often a stepping stone before transitioning to Campaign v8.

Key points:

• No automated migration tool available - manual planning and execution required
• Adobe Professional Services support highly recommended
• Benefits include cloud infrastructure, automatic security patches, expert support, and easier path to v8
• Migration involves due diligence, environment audit, data cleanup, stage migration, and production cutover

Getting started: Contact your Adobe representative to assess your environment and develop a detailed migration plan with Adobe Professional Services.

Learn more about migrating to Managed Services including challenges, best practices, and detailed migration roadmap.

Campaign v8 brings most v7/Standard capabilities with enhancements, but some terminology and features differ. You’ll find a summary of key changes below.

Key terminology changes (Campaign Standard → v8):

• Custom resources → Schemas | Messages → Deliveries | Product users → Operators
• Security Groups → Operator Groups | Organizational units → Folder Permissions

Campaign Web UI updates:

• Recipients → Profiles | Seed addresses → Test profiles | Delivery analysis → Delivery preparation
• Lists → Audiences | Email Preview → Simulate content

Not available in v8:

• On-premise/hybrid deployments (Managed Cloud Services only)
• Direct database access (use APIs)
• Manual infrastructure management (Adobe managed)

New features for Campaign Standard users:

• Dynamic Reporting, Centralized Branding, REST APIs, Landing Pages improvements, Visual Fragments

Related topics:

Capability matrix | v7 to v8 transition guide | Campaign Standard to v8 transition

Create recipients manually in the client console for individual profiles, import from files (CSV/TXT) for bulk additions, use web forms for self-registration, or integrate via APIs from external systems. Use import workflows for recurring data loads.

Related topics:

Create profiles manually | Import profiles from a file | Collect profiles with web forms

Campaign provides multiple import methods: simple file import using the import wizard, workflow-based import for complex transformations, recurring imports with scheduled workflows from SFTP, and API import for programmatic integration.

For file imports, prepare your data file (CSV/TXT, UTF-8 encoding), use the import wizard or workflow, map columns to Campaign fields, define update/insert rules, and test with a small sample first. Use workflows for recurring imports and apply deduplication rules.

Related topics:

Import data guide | Recurring import workflow | Data loading activity

Test profiles (seed addresses) let you target recipients who don’t match defined targeting criteria, allowing you to test your delivery before sending to your main audience. Add them via Seed addresses in the delivery properties or use the Seed addresses folder.

Learn more about test profiles.

Campaign offers multiple targeting methods: build queries with visual criteria, target existing lists or segments, import recipients from external files (CSV, TXT), or apply pre-defined filters. You can combine criteria with AND/OR logic, exclude specific populations, use control groups, and split for A/B testing. Always preview your target population size before sending.

Related topics:

Define campaign targets | Query activity | Create audiences

A list is a static set of recipients that you can target in deliveries and reuse across campaigns.

Three creation methods:

• Manual creation: Navigate to Profiles and Targets > Lists and click Create. Add recipients from a query, by individual selection, or from a folder.

• Workflow automation: Use the List update activity to create and maintain lists automatically from query results or imported data.

• During import: Create a list when importing profiles to save them as a reusable group.

Tip: Use workflows for lists requiring regular updates, and manual creation for one-time segmentation.

Related topics:

Create audiences | List update activity

Use the Deduplication activity in a workflow to remove duplicate recipients before delivery. Place it between your Query and Delivery activities, then choose your deduplication criteria (typically email address or recipient ID) and which record to keep.

Tip: Always deduplicate before sending to ensure each person receives your message only once.

Learn more about the Deduplication activity

Campaign automatically tracks newsletter subscriptions through information services. To target subscribers:

• Use a Query activity and filter on Subscriptions > select your newsletter service
• Target subscribers directly from your delivery by choosing To > Subscribers of an information service
• Build subscriber lists with the Subscription Services workflow activity

Campaign tracks subscription/unsubscription history and manages opt-in/opt-out automatically.

Related topics:

Manage subscriptions | Query activity

Use the Exclusion activity in a workflow to remove unwanted profiles from your target. Place it after your targeting activities and define which population to exclude.

Learn more about the Exclusion activity

Key guidelines: ensure mobile-responsive design, use HTML 4.0/XHTML compatible code with inline CSS, optimize images (under 100KB) with alt text, use personalization merge fields, test across email clients before sending, and include a plain text version. Aim for total email size under 500KB for optimal deliverability.

Related topics:

Email design guide | Delivery best practices

A delivery template is a pre-configured delivery that saves all settings and parameters for reuse across multiple campaigns. Templates include target rules, content design, personalization, technical settings (sender, reply-to), and typology rules. Create once and reuse to maintain consistency and speed up campaign creation.

Learn how to Create delivery templates

Yes. Import HTML content via direct copy/paste into the content editor, file upload from your computer, or load from a URL. Ensure your HTML uses email-compatible code (HTML 4.0/XHTML) with inline CSS, and host images on a public server. Campaign automatically adds personalization and tracking to imported HTML.

Tip: For the best email design experience, use the Email Designer in the Campaign Web UI, which offers modern drag-and-drop capabilities and built-in responsive templates, rather than importing raw HTML.

Learn how to Import HTML content

Yes. Use Campaign’s information services to manage newsletter subscriptions. Key capabilities include automatic opt-in/opt-out handling, subscription tracking, compliance management (GDPR, CAN-SPAM), multi-newsletter support, web integration for sign-up forms, and targeted delivery to subscribers.

Learn how to manage subscriptions

Campaign offers personalization capabilities to create relevant, targeted messages based on recipient data, behavior, and preferences.

Personalization options:

• Personalization fields - Insert recipient data (e.g., "Hello {{firstName}}")
• Personalization blocks - Use predefined or custom content blocks
• Conditional content - Display different content based on recipient criteria
• Behavioral data - Leverage browsing history, purchase patterns, or engagement metrics

Test personalization before sending to verify merge fields and conditional logic work correctly.

Related topics:

Personalization guide | Personalization fields | Conditional content

Personalized subject lines significantly increase open rates. Campaign allows you to dynamically insert recipient data, apply conditional logic, and test variations to optimize engagement.

Personalization techniques:

• Basic fields - Insert firstname, lastname, location: "<%@ firstName %>, exclusive offer for you"
• Conditional content - Different subjects by segment: "<% if (recipient.gender == 'F') { %>Special offer just for you<% } else { %>Exclusive deal inside<% } %>"
• Dynamic data - Include purchase history, loyalty points, or account info
• Emojis - Add visual appeal (test across email clients first)

Best practices: Keep under 50 characters, test personalization tokens before sending, use A/B testing to optimize, avoid spam trigger words, include value proposition or urgency.

Related topics:

Personalization fields | Conditional content

Yes. Campaign v8 offers multilingual capabilities, with the Campaign Web UI providing the easiest approach. The Web UI offers native multilingual delivery with language variants—add language variants to your delivery, and Campaign automatically sends the appropriate version based on recipient’s preferred language. Available for email, push notifications, SMS, and transactional messages.

Key features: automatic content duplication, automatic language-based sending, default language fallback, and easy variant management.

The client console also supports multilingual content using conditional content and workflows, but requires more manual configuration.

Related topics:

Multilingual deliveries (Web UI) | Conditional content (Client console)

Yes. Campaign web applications support multi-language localization. Define translations for all form elements (labels, buttons, messages, error text), with automatic language detection based on recipient profile or browser settings. Multiple language versions are supported within a single web application, with fallback to a default language when needed.

Learn more about Web application localization

Yes, but only through the Campaign Web UI. AI Assistant, powered by Microsoft Azure OpenAI and Adobe Firefly, helps create professional, brand-consistent content across email, SMS, and push notifications.

Key capabilities:

• Generate text (email copy, subject lines, SMS/push content) and brand-aligned images
• Create content variations optimized for different audiences
• Refine content (elaborate, summarize, rephrase, simplify)
• Upload brand assets and get brand alignment scoring
• Use existing content as reference and upload style reference images

Note: AI Assistant is available exclusively in the Campaign Web UI and currently supports English only. Users need proper permissions and must agree to a user agreement.

Related topics:

AI Assistant overview | AI Assistant use cases | Brand alignment

Email deliverability, a critical component to every sender’s marketing program success, is characterized by ever-changing criteria and rules. Effectively navigating in this digital world requires regular tuning of your email strategy, with consideration to key deliverability trends, to best reach your audiences.

Refer to this guide to learn Deliverability Best Practices

Learn how to implement deliverability in Campaign in this guide

Related topics:

Get started with deliverability | Control message content | Monitor deliverability | SpamAssassin

Before sending: Run delivery analysis, send test proofs, review warnings, verify target count.

During/after sending: Monitor delivery dashboard (sent, delivered, bounces, errors), check delivery logs, track success/bounce rates, review quarantined addresses.

Best practices: Set up alerts, use waves for large volumes, test with small volumes first, clean recipient database regularly, monitor sender reputation.

Related topics:

Track and monitor deliveries | Delivery best practices

Delivery analysis is a validation phase Campaign runs before sending. It calculates the target population, validates content, checks for errors, applies typology rules, and estimates delivery volume.

Campaign generates logs showing warnings and errors. Errors block delivery and must be fixed; warnings are advisory. Always review analysis logs before sending.

Learn more in the Delivery analysis guide

Proofs are test messages that validate your delivery before sending to your main audience. Use proofs to verify personalization, test content rendering across email clients, confirm links and tracking work, check images and attachments, and validate mobile responsiveness.

Proofs help catch errors before they reach thousands of recipients, enable stakeholder approval, and test inbox placement. Send proofs to multiple email clients and devices, and always obtain approval before production sends.

Learn more in the Proofs and preview guide

Seed addresses are special recipients automatically added to every delivery for testing, quality assurance, and monitoring—without matching your target criteria. Useful for ongoing monitoring, inbox placement testing, direct mail validation, and stakeholder visibility.

Key differences from proofs:

• Seed addresses - Added to production deliveries automatically, count toward send volume
• Proofs - Test sends before production, don’t count toward volume, used for validation

Manage seed addresses in Resources > Campaign management > Seed addresses. Keep lists small to avoid impacting delivery metrics.

Learn more in the Seed addresses guide

Campaign provides approval workflows to ensure messages meet quality standards before sending. Configure approvals for content, target, extraction (direct mail), and budget at the campaign or delivery level.

Setup:

Create operator groups in Administration > Access management > Operator groups, then assign approval groups in campaign or delivery properties. Campaign sends notification emails to reviewers who can approve, reject, or request changes.

For standalone deliveries (not in a campaign):

Use proofs as your approval process. Send proofs to your approval group for validation, and always send a new proof after making changes to ensure stakeholders review the latest version.

Related topics:

Delivery validation | Campaign approvals

Yes! Campaign allows you to run A/B tests (also called split tests) to optimize subject lines, content, sender names, send times, and more by comparing performance across different variants.

What you can test:

• Subject lines - Compare open rates across different subjects
• Content variations - Test different layouts, calls-to-action, or images
• Sender information - Test sender name or from address impact
• Send time - Identify optimal delivery windows
• Personalization strategies - Compare personalized vs. generic content

How it works:

1. Create your delivery and define test variants (up to 3)
2. Split your audience (typically 10-20% for test segments)
3. Campaign sends variants to test segments and tracks performance
4. Winning variant automatically sends to remaining audience (or you manually select winner)

Available in: Both Campaign Web UI and client console. Web UI offers simpler setup with visual comparison.

Related topics:

Delivery analysis | Send and track deliveries

Typology rules are automated business logic applied during delivery analysis to validate and optimize message sending. They ensure compliance with marketing policies, protect deliverability, and prevent customer fatigue.

Main rule types:

• Filtering rules - Exclude recipients (blocklisted, unsubscribed, quarantined)
• Pressure rules - Control message frequency to avoid overwhelming recipients
• Capacity rules - Limit message volume for processing capacity or ISP limits
• Control rules - Check message validity (subject line, unsubscribe link, sender format)

Rules are grouped into typologies and applied during delivery analysis. Campaign can exclude recipients, block the delivery, or generate warnings based on the rules.

Learn more in the Typology rules guide

Yes. Wave sending splits your delivery into multiple batches sent at scheduled intervals. This is essential for large-volume campaigns to balance server load, prevent ISP throttling, build sender reputation with new IPs, and manage opt-outs/bounces between waves.

Configuration:

In your delivery properties, enable wave sending and define the number of waves (or batch size), interval between waves, and wave distribution (linear or custom percentages). Campaign automatically divides your target population and sends each wave on schedule.

Use waves for large campaigns, monitor first wave performance before continuing, and allow sufficient time between waves to process bounces and opt-outs.

Learn how to Configure wave sending

Campaign allows you to schedule deliveries for future sending to optimize send times and coordinate campaigns.

Scheduling options:

• Delivery properties - Send immediately, schedule for specific date/time, or defer by hours/days
• Campaign level - Coordinate all deliveries within a campaign
• Workflow Scheduler activity - For recurring deliveries, complex patterns, and event-triggered campaigns

Campaign also supports contact date optimization (best send time per recipient) and time zone adaptation (same local time for all recipients).

Learn how to Schedule delivery sending

Yes. Campaign supports static attachments (same file for all recipients) and personalized attachments (different files per recipient based on profile data). Add attachments in the Attachments section of your delivery properties.

Important considerations:

• Keep attachments under 1MB for optimal deliverability
• Attachments can trigger spam filters; test thoroughly before sending
• Avoid file types commonly blocked by email clients (.exe, .zip, .js)
• For large files, consider using tracked download links instead

Use safe file formats (PDF, JPEG, PNG, DOCX) and test with seed addresses before production sends.

Learn more in the Email attachments guide

Campaign automatically converts all URLs in your email into tracked links to monitor recipient engagement. Access the Tracking section in your delivery to configure tracking settings for each link.

Configuration options:

• Enable/disable tracking - Control tracking per link
• Link labels - Add descriptive names for reporting (e.g., “Shop Now CTA”)
• Link categories - Group links by type for aggregated analysis
• Tracking type - Track clicks, opens, or both

Campaign tracks content links, mirror page links, unsubscribe links, and can include an optional tracking pixel for email opens. Use meaningful labels and categories to simplify reporting and quickly identify high-performing content.

Related topics:

Link tracking guide | Tracking best practices

Access delivery and tracking logs directly from each delivery dashboard. In the client console, click the Delivery tab at the bottom. In the Campaign Web UI, navigate to the Logs section.

Available logs:

• Delivery logs - Sent messages with recipient details and status (sent, pending, failed)
• Tracking logs - Recipient interactions (opens, clicks) with timestamps
• Exclusion logs - Excluded recipients with reasons (quarantine, typology rules, duplicates)
• Broadcast logs - Complete sending history including retries and errors

Use these logs to troubleshoot delivery issues, analyze engagement, and maintain list hygiene.

Related topics:

Delivery monitoring | Tracking guide

Campaign provides comprehensive built-in reports to analyze delivery performance, recipient engagement, and campaign effectiveness. Access reports from the Reports tab in any delivery, from the campaign dashboard, or from the global Reports menu for cross-campaign analysis.

Key reports include:

• Delivery summary - Send statistics, opens, clicks, bounces, and unsubscribes
• Hot clicks - Visual heatmap of link performance
• Tracking indicators - Click-through rates and engagement metrics
• Non-deliverables - Bounce analysis with failure reasons

Reports are available in both the client console and Campaign Web UI with modern visualizations.

Related topics:

Built-in delivery reports | Campaign reporting

Campaign automatically manages a quarantine list to protect your sender reputation and improve deliverability. Quarantined addresses are automatically excluded from future deliveries until they’re validated or removed from quarantine.

Why addresses get quarantined:

• Hard bounces - Permanent delivery failures (invalid email address, domain doesn’t exist, mailbox deleted)
• Soft bounce threshold - Repeated temporary failures (mailbox full, server temporarily unavailable) exceeding the error threshold
• Spam complaints - Recipients marking your emails as spam
• Invalid addresses - Addresses with syntax errors or that fail validation
• Blocklisted - Recipients who opted out or requested to be excluded

How quarantine works:

Campaign tracks delivery errors for each address. When an address reaches the configured error threshold, it’s automatically quarantined and excluded from all future deliveries during analysis. Hard bounces (permanent failures) are quarantined immediately, while soft bounces require multiple failures before quarantine.

Managing quarantined addresses:

Access quarantine management in Administration > Campaign Management > Non deliverables Management. You can view quarantined addresses, manually remove validated addresses from quarantine, or configure automatic cleanup rules.

Tip: Monitor your quarantine list regularly. Increasing quarantine rates often signal data quality issues that need attention before they impact sender reputation.

Related topics:

Quarantine management guide | Bounce management

Adobe Campaign includes workflows to orchestrate the full range of processes and tasks across the different modules of the application server. This comprehensive graphical environment lets you design processes including segmentation, campaign execution, file processing, human participation, etc. The workflow engine executes and tracks these processes.

You can use a workflow, for example, to download a file from a server, decompress it, and then import records contained within into the Adobe Campaign database.

A workflow can also involve one or more operators to be notified or who can make choices and approve processes. In this way, it is possible to create a delivery action, assign a task to one or more operators to work on content, specify targets, and to approve proofs before starting the delivery.

Learn more about workflows. You can also read out workflow best practices.

Related topics:

Get started with workflows | Build your first workflow | Workflow use cases | Monitor workflow execution

Yes. Campaign provides multiple monitoring tools: workflow dashboard (real-time status and errors), workflow logs (detailed execution logs), heatmap (visualize activity and bottlenecks), audit trail (track modifications), and alerts (notifications for failures).

To monitor, open the workflow and click the Logs tab. Failed activities appear in red.

Related topics:

Monitor workflow execution | Workflow best practices

Create workflows to automate marketing processes in Campaign:

1. Create a new workflow - Navigate to Profiles and Targets > Jobs > Targeting workflows or Administration > Production > Technical workflows and click Create
2. Add activities - Drag and drop activities from the palette (targeting, flow control, action activities)
3. Configure activities - Double-click each activity to set parameters and define logic
4. Connect activities - Link activities with transitions to define the execution flow
5. Test and validate - Use the workflow diagram to check logic, then test with a small dataset
6. Execute - Start the workflow manually or schedule it for automatic execution

Common workflow patterns: data import, audience segmentation, delivery sending, data enrichment, and cross-channel orchestration.

Related topics:

Build a workflow | Workflow activities | Workflow best practices | Workflow use cases

Use workflows with the Scheduler activity to automate campaigns that run on a regular schedule—daily, weekly, monthly, or custom intervals. Perfect for welcome emails, birthday messages, newsletter sends, abandoned cart reminders, and regular reporting.

Setup pattern:

1. Scheduler - Define frequency (e.g., “Every Monday at 9 AM”)
2. Query - Select target audience with dynamic criteria
3. Enrichment (optional) - Add personalization data
4. Delivery - Configure your message (email, SMS, push)
5. End - Workflow completes and waits for next scheduled run

Common automated campaigns:

• Welcome series - Daily workflow to send onboarding emails to new subscribers
• Birthday emails - Daily check for recipients with birthdays, send personalized message
• Re-engagement - Weekly targeting of inactive users with win-back offers
• Newsletters - Scheduled weekly or monthly content distribution
• Cart abandonment - Hourly workflow to identify and message cart abandoners

Tip: Use recurring delivery type in workflows to track each execution separately and maintain historical reporting.

Related topics:

Scheduler activity | Recurring deliveries | Campaign automation

Methods: Import wizard (one-time CSV/TXT), workflow-based import (Data loading (file) activity for complex/recurring imports with transformations), REST APIs (programmatic/real-time sync).

Best practices: Test with small samples, use UTF-8 encoding, map fields correctly, apply deduplication, schedule large imports off-peak.

Related topics:

Import best practices | Data loading activity | Recurring import workflow

Data quality is critical for successful campaign execution. Poor data leads to delivery failures, wasted resources, and compliance risks. Campaign provides tools to validate, clean, and enrich data during the import process.

Data validation steps:

1. Pre-import validation - Verify file format, encoding (UTF-8), column mapping, required fields present
2. Deduplication - Use Deduplication activity to identify and handle duplicates by email, ID, or custom keys
3. Data enrichment - Use Enrichment activity to add missing data from existing Campaign tables
4. Format standardization - Normalize phone numbers, email addresses, dates, country codes using JavaScript or enrichment
5. Validation rules - Apply constraints (valid email format, mandatory fields, value ranges)

Common issues and fixes:

• Character encoding errors → Always use UTF-8 encoding
• Date format mismatches → Standardize to YYYY-MM-DD format
• Invalid email addresses → Use validation rules or JavaScript to filter
• Duplicate records → Always include deduplication activity before updates
• Missing required fields → Set default values or reject incomplete records

Best practice: Create a reusable “data quality” workflow template with standard validation and cleaning activities that you can apply to all imports.

Related topics:

Data quality guide | Deduplication activity | Enrichment activity

Workflows automate marketing processes including:

Data management: Import/load data, cleansing, enrichment, list management
Campaign automation: Welcome series, birthday campaigns, re-engagement, cart abandonment
Advanced targeting: A/B testing, dynamic segmentation, lead scoring, cross-channel orchestration
Monitoring: Workflow/delivery monitoring, alerts, database maintenance
Integration: CRM sync, API integrations, event-triggered workflows

Related topics:

Workflow use cases library | Build a workflow | Workflow best practices

Use Update data activity for bulk database operations: Insert (add new records), Update (modify existing), Insert or update (upsert), Delete (remove matching records).

Common uses: Update profile attributes, synchronize with external systems, maintain list memberships, clean/deduplicate data, apply bulk status changes.

Configure reconciliation keys for accurate matching and choose update options.

Related topics:

Update data activity | Data management activities

Data management activities enable sophisticated operations: Enrichment (add data from related tables), Split (segment populations), Deduplication (remove duplicates), Update data (bulk operations), Change dimension (switch targeting dimensions), Intersection/Union/Exclusion (combine/filter populations).

Common uses: Enrich with purchase/behavior data, segment audiences, remove duplicates, integrate external databases (FDA), create complex multi-table queries.

Related topics:

Data management activities | Enrichment activity

Yes. Build automated workflows: Query (target audience) → Enrichment (add personalization data) → Split (optional segments) → Delivery (personalized messages) → Scheduler (recurring execution).

Personalization: Use profile data, behavioral data, conditional content, dynamic values. Common scenarios: birthday campaigns, cart abandonment, loyalty programs, win-back, event-triggered messages.

Related topics:

Personalization guide | Workflow use cases

Use Split activity to divide populations: Filtering conditions (age, location, VIP status), Percentage distribution (A/B testing), Limit records (first N, top X%), Data grouping (one subset per value).

Common uses: A/B testing, channel preference routing, progressive rollout, segment-specific messaging, load balancing. Each subset flows to separate transition for different processing.

Related topics:

Split activity | A/B testing guide

Yes. Workflow: Data loading (file) → Enrichment (optional) → Reconciliation (match keys like email/ID) → Update data (update matched records, insert new if no match).

Common uses: Update profile attributes from CRM, refresh subscription statuses, synchronize loyalty points, update opt-in/opt-out preferences.

Best practices: Use unique identifiers, validate data first, test with samples, schedule regular updates.

Related topics:

Import data guide | Data loading activity | Update data activity

Query Created date field to select recipients added within specific timeframe.

Automated welcome workflow: Scheduler (run daily) → Query (select new recipients) → Deduplication (optional) → Delivery (welcome message) → Update data (mark as “welcomed”).

Advanced: Use aggregate functions to dynamically identify recent additions.

Related topics:

Query activity | Using aggregates

Four activity categories:

Targeting: Query, Split, Deduplication, Enrichment, Intersection, Union, Exclusion (define/refine audience)
Flow control: Scheduler, Wait, Test, Fork, AND-join, OR-join, Jump (manage logic/timing)
Action: Delivery, Update data, Data loading/extraction, JavaScript code (perform operations)
Event: External signal, File collector, HTTP transfer (react to triggers)

Drag from palette, double-click to configure, connect with transitions.

Related topics:

Targeting activities | Flow control | Action activities

Design: Clear names, add labels/descriptions, group related activities, break complex processes into smaller workflows
Performance: Limit query sizes, use temporary tables, schedule off-peak, avoid excessive loops
Error handling: Add error paths, configure alerts, test with samples, review logs
Maintenance: Archive obsolete workflows, version control, limit complexity (<20 activities), use templates
Security: Apply permissions, clean temporary data, use variables not hardcoded values

Related topics:

Workflow best practices guide | Monitor workflows

It depends on which interface you’re using. The client console language is fixed, but the Campaign Web UI allows individual users to change their language preferences.

Client Console (Desktop Application):

• Language is set when your instance is created and cannot be changed
• The client console and server must use the same language
• Each Campaign instance operates in a single language
• For English installations, you can choose between US English or UK English (they differ in date and time formats)

Campaign Web UI:

• Users can change their interface language independently through their profile preferences
• Multiple languages are supported with locale-specific formatting for dates, times, and numbers
• Your Web UI language preference is independent of your Campaign server and client console language

Related topics:

Change language in Campaign Web UI | Get started with Campaign client console

Campaign Control Panel is a web-based administrative interface that helps Campaign administrators increase efficiency by managing settings and monitoring usage across Campaign instances. It provides self-service capabilities to manage critical instance configurations without contacting Adobe Support.

Key capabilities:

• Subdomain management - Delegate and manage subdomains, monitor SSL certificates
• Storage monitoring - Track database usage and prevent storage issues
• SFTP management - Monitor SFTP storage, manage IP allowlists, and SSH keys
• Instance settings - Configure IP allowlists, manage URL permissions, review instance details
• Active profiles monitoring - Track active profile usage against entitlements
• Performance monitoring - Monitor database and workflow performance
• Email deliverability - Configure DMARC, BIMI, and other authentication records

Access requirements:

• Admin users only - Control Panel is restricted to users with Administrator rights
• Adobe IMS authentication - Access through Adobe Experience Cloud with your Adobe ID
• Campaign v8 Managed Cloud Services - Available for hosted instances only

Additional resources:

Control Panel documentation | Control Panel tutorial videos

A subdomain is a division of your domain that can be used to isolate your brands, or various types of traffic (transactional messages, marketing information, etc.).

Campaign v8 provides comprehensive tracking to monitor recipient interactions with your messages. Tracking requires proper configuration of your instance and message settings.

What you can track:

• Email opens - Via tracking pixel (1x1 transparent image)
• Link clicks - All URLs automatically converted to tracked links
• Unsubscribes - Opt-out link tracking
• Mirror page views - When recipients view the web version
• Custom parameters - Add tracking data to URLs for advanced analysis

Key configuration steps:

1. Configure tracking server URL in your instance settings (managed by Adobe for v8)
2. Enable tracking in delivery properties
3. Set up tracking for individual links or all links automatically
4. Define tracking validity period and log retention

Best practice: Always test tracking with proofs before sending to your main audience to ensure links work correctly and data is captured.

Related topics:

Track and monitor deliveries | Configure tracked links | Test tracking

Email deliverability depends on technical configuration, content quality, and sender reputation. Campaign v8 provides tools and settings to optimize inbox placement.

Essential configuration steps:

• Domain authentication - Set up SPF, DKIM, and DMARC records to verify your sending domain
• IP warming - Gradually increase sending volume on new IPs to build reputation
• Sender configuration - Use consistent, recognizable sender addresses and names
• Bounce management - Configure quarantine rules to handle hard and soft bounces automatically
• Feedback loops - Set up complaint handling to manage spam reports

Content best practices:

• Test emails with SpamAssassin to check spam score
• Maintain proper text-to-image ratio
• Include plain text version alongside HTML
• Always provide unsubscribe link
• Avoid spam trigger words and excessive capitalization

Monitoring: Use Campaign’s deliverability reports to track bounce rates, complaint rates, and inbox placement. For Campaign v8, Adobe provides infrastructure-level deliverability optimization.

Related topics:

About deliverability in Campaign | Deliverability Best Practice Guide

Campaign v8 provides Federated Data Access (FDA) to query and use data stored in external databases without changing the Campaign data model. You configure an external account, then use FDA in workflows, queries, and targeting to combine external data with Campaign profiles.

FDA availability and connection requirements depend on your deployment and licensing. Review supported databases and required versions in the compatibility matrix.

Related topics:

Configure FDA connections | Compatibility matrix

Campaign v8 supports Federated Data Access (FDA) connections to major enterprise database systems (cloud databases, enterprise databases, data warehouses, big data platforms).

Supported database versions and connection requirements vary. Check the Compatibility matrix for your Campaign v8 version to confirm support for specific databases and ensure proper licensing for FDA connectors.

See Configure FDA connections

Yes. Campaign provides native CRM connectors for bidirectional synchronization with major CRM systems. Syncs contact data, leads, accounts, delivery logs, tracking data, and engagement metrics. Supports scheduled, manual, and real-time (via API) synchronization modes.

Use Campaign’s CRM connector assistant to map fields, select tables, and schedule sync. Check Compatibility matrix for supported CRM versions.

Related topics:

CRM connector configuration | Workflow CRM activities

Clearing the client console cache resolves many common display and functionality issues. The cache stores local configuration files that can sometimes become corrupted or outdated.

When to clear cache:

• New branding elements (logos, colors) not displaying correctly
• Export/import functions failing unexpectedly
• Interface elements not updating after configuration changes
• Performance issues or slow console response
• After upgrading to a new client console version

Steps to clear cache:

1. Open the Campaign client console
2. Go to File menu
3. Select Clear the local cache…
4. Confirm the action when prompted
5. Restart the client console

If the issue persists (advanced):

Close the client console, then manually remove the local cache files from your user profile.

Manual cache cleanup (Windows):

1. In the client console, select File > Clear the local cache….
2. Log out and close the client console.
3. Go to the cache location based on your Windows version. For Windows 10: C:\Users\<Username>\AppData\Roaming\Neolane\NL_5\
4. Delete the nlclient-config-<alphanumerical>.xml files and their associated folders.

Adobe Support can confirm the correct cache location for your version and OS and guide you through a safe manual cleanup.

Learn more in Install and configure client console

No. Campaign v8 does not support LDAP integration. Authentication uses Adobe IMS (Adobe ID or Federated ID). If you are migrating from Campaign Classic v7, review unsupported features and authentication changes.

Related topics:

Connect to Campaign v8 | Unsupported features in v8

Yes. Campaign administrators can customize the user interface to match organizational branding and optimize user experience. Configure settings at the instance or user level.

What you can customize:

• Branding - Logo, colors, and visual identity elements
• Default views - Home page layout, folder structure visibility
• List configurations - Default columns, sort order, filters in data lists
• Navigation - Available menu items and shortcuts
• Regional settings - Date/time formats, number formats, time zones
• Notifications - Email alerts, in-app notifications, workflow alerts

Configuration levels:

• Instance-wide - Apply to all users (requires administrator rights)
• User-specific - Individual preferences and personal settings

Related topics:

Configure UI settings | User permissions

Yes. Campaign’s flexible data model allows you to extend built-in schemas with custom fields and create entirely new tables to meet your specific business needs.

What you can customize:

• Add fields to existing tables - Extend recipient table with loyalty points, custom preferences, external IDs
• Create new custom tables - Store products, transactions, loyalty tiers, custom entities
• Define relationships - Link custom tables to existing Campaign tables
• Extend forms - Update UI to display and edit custom fields

Common use cases:

• Store additional profile attributes (customer lifetime value, preferred store, VIP status)
• Manage product catalogs with custom attributes
• Track custom events and interactions
• Integrate external system IDs for data synchronization
• Build industry-specific data models (retail, finance, travel)

Related topics:

Extend data model | Schema structure | Data model best practices

Campaign offers multiple reporting options depending on your needs and technical expertise: built-in reports, descriptive analysis, custom reports in the client console, and cubes.

Reporting options:

• Built-in reports - Ready-to-use delivery, campaign, and tracking reports accessible from the Reports tab
• Descriptive analysis - Quick statistical reports on any data with a wizard-driven interface
• Custom reports - Advanced reports built by technical users using the reporting editor
• Cubes - Multi-dimensional data exploration and pivot table analysis

Important: Campaign is designed for marketing operations reporting, not as a specialized business intelligence tool. For complex analytical needs, consider integrating with Adobe Analytics or dedicated BI platforms.

Related topics:

Get started with reporting | Campaign Web UI reports

Use Campaign’s descriptive analysis tool to quickly generate statistical reports on any population data. This wizard-driven feature helps you analyze distributions, trends, and patterns without technical expertise.

What you can analyze:

• Recipient demographics and segmentation breakdowns
• Campaign performance metrics and response rates
• Distribution of profile attributes (age, location, preferences)
• Delivery statistics and engagement patterns
• Custom field values and data quality metrics

How to create: Select any list or query result → Right-click → Actions > Analyze → Choose analysis type (qualitative or quantitative) → Configure display options → Generate report.

Sharing: Export reports to Excel/PDF or save them to the Reports folder for team access with appropriate permissions.

Learn more about Descriptive analysis

Use the client console to create advanced custom reports with complex analysis capabilities.

In the Client Console, you can:

• Build complex reports using SQL queries and custom calculations
• Create multi-page reports with charts, tables, and pivot tables
• Design conditional formatting and dynamic content
• Access the full Campaign data model and external databases (FDA)

Learn how to Create custom reports (client console)

Cubes are multi-dimensional data structures that enable business users to explore and analyze Campaign data through pivot tables without technical skills. Think of them as pre-configured data models that simplify complex reporting. This reporting tool is available in both the client console and Campaign Web UI.

• Technical users create and configure cubes defining dimensions (time, geography, channels) and measures (opens, clicks, revenue)
• Business users select a cube when creating reports and drag-and-drop dimensions to explore data
• Data is automatically aggregated and calculated based on cube configuration
• Results can be displayed as pivot tables, charts, or exported to Excel

Learn how to Explore data with cubes

Yes! Campaign includes a Survey module that allows you to create online questionnaires and generate built-in reports on survey responses.

Important: Survey management is not available in Campaign v8 Enterprise (FFDA) deployments. Learn more.

Survey capabilities:

• Create online questionnaires with multiple pages and question types
• Collect responses in the database or local variables
• View real-time tracking of survey responses
• Generate dedicated reports on survey answers (breakdown by question, general statistics)
• Export survey responses to Excel, PDF, or CSV for further analysis
• Use survey data in targeting workflows to personalize campaigns

Advanced analysis:

• Access survey responses from the Responses tab and export data
• Use Survey responses activity in workflows to target recipients based on their answers
• Combine survey data with other Campaign data for segmentation and personalization
• Create custom reports and cubes for multi-dimensional survey analysis

Related topics:

Get started with surveys | Survey reports

Control report visibility through folder permissions and named rights in Campaign.

Access control methods:

• Folder permissions - Place reports in folders with appropriate access for user groups
• Named rights - Assign rights to view, create, or modify reports
• Display context - Define where reports appear (Reports folder, campaign tabs, delivery screens)

Setup: Save report to specific folder → Configure folder access for operator groups → Define report properties and display context.

Related topics:

Custom reports | User permissions

Yes, Campaign supports multiple export formats for both client console and Web UI reports, enabling easy sharing with stakeholders and integration with other tools.

Available export formats:

• Excel (.xlsx) - Best for data manipulation, further analysis, and pivot tables
• PDF - Ideal for presentations, executive summaries, and printed reports
• CSV - Perfect for data imports into other systems and BI tools
• OpenDocument (.ods) - Open-source spreadsheet format
• XML - For system integrations and automated processing

How to export:

• Client console: Open report → Click Export button → Choose format → Save file
• Web UI: Open dashboard → Click export icon → Select format → Download
• Automated exports: Schedule regular exports using workflows with export activities

Best practices:

• Use Excel for reports requiring stakeholder analysis and annotations
• Use PDF for static reports sent to executives or archived for compliance
• Use CSV for integrations with data warehouses or external analytics tools
• Test exported reports to ensure formatting and data accuracy

Related topics:

Custom reports | Campaign Web UI reports

Campaign’s data model is a schema-driven relational database structure consisting of built-in tables (recipients, deliveries, campaigns) that can be extended for your business needs.

Key concepts: Schemas (XML definitions), built-in tables, links (relationships), enumerations (value lists), extensions (custom fields/tables).

Main schemas: Recipient (nms:recipient), Delivery (nms:delivery), Workflow (xtk:workflow), Campaign (nms:operation), Tracking logs.

Understanding the data model is essential for workflows, queries, schema extensions, and integrations.

Related topics:

Campaign data model | Data model best practices

Schemas define Campaign’s data structure in XML format, specifying table structure, field properties, relationships, indexes, and access control.

Working with schemas:

• View: Access via Administration > Configuration > Data schemas
• Extend: Create extension schemas (e.g., cus:recipient) to add custom fields without modifying core schemas
• Create: Build new tables for business-specific data
• Update: Apply changes via Tools > Advanced > Update database structure

Common uses: Add custom fields to recipient table, create custom tables, define relationships, implement business-specific models.

Important: Never modify built-in schemas directly. Always use extension schemas for upgrade compatibility.

Related topics:

Get started with schemas | Extend a schema

Use a custom recipient table when targeting B2B accounts, separate subscriber data, external systems, or multi-brand architectures instead of the standard recipient table.

Implementation: Create custom schema with mandatory fields (email, primary key, exclusions) → Configure target mappings → Update delivery templates → Adapt workflows/queries.

Key considerations: Must include required delivery fields, workflows/forms need adaptation, testing critical before production migration.

Best practice: Extend the standard recipient table first. Only use custom tables when truly necessary due to added complexity.

Related topics:

Custom recipient table | Target mappings

Campaign’s query editor builds database queries visually without SQL, used in workflow activities, delivery targeting, lists, reports, and filters.

Best practices:

• Start simple - build incrementally, test each step
• Use filtering dimensions - leverage table relationships
• Optimize performance - index queried fields, avoid complex calculations
• Reuse predefined filters for consistency
• Test with small samples first
• Document complex queries

Common patterns: Target delivery openers, find inactive contacts, segment by behavior, exclude previous recipients.

Access: Tools > Generic query editor for ad-hoc exploration.

Related topics:

Query editor | Query activity

Import packages via Tools > Advanced > Import package in the client console. Packages contain Campaign configurations (schemas, workflows, typologies) and data for deploying between instances.

Package types: User package (custom configs), Platform package (Adobe-provided), Data package (actual data).

Best practices: Test in dev first, back up before importing, export from same/older version.

Learn more in Work with data packages

Campaign v8 provides SOAP APIs (client console operations), REST APIs (modern integrations), and JavaScript APIs (workflow scripting).

Common uses: Integrate with CRM/ERP, automate campaigns, synchronize data, build monitoring solutions, create external interfaces.

Access: Campaign v8 API documentation

Campaign APIs let you programmatically control workflows: start, pause/resume, stop, query status, retrieve logs, monitor activity progress.

API endpoint: POST https://mc.adobe.io/<ORGANIZATION>/campaign/workflow/execution/<workflowID>/commands

Commands: {"method":"start"}, {"method":"pause"}, {"method":"resume"}, {"method":"stop"}

Use cases: Build monitoring dashboards, implement automated alerting, orchestrate from external schedulers, create dependencies across instances, generate custom reports.

Best practice: Combine API monitoring with audit trail for comprehensive governance.

See Control workflows via API

After modifying schemas (adding fields, creating tables, changing data types), update the physical database structure via Tools > Advanced > Update database structure to apply changes.

When needed: Adding fields, creating/extending tables, modifying field properties, adding/removing links, creating indexes.

Important: Backup first, test in dev, plan downtime for large changes, coordinate with Adobe support (Managed Cloud Services), note some changes may cause data loss.

Related topics:

Update database structure | Extend schema

Campaign helps you comply with privacy regulations (GDPR, CCPA, PDPA, LGPD) through tools for managing data subject rights, consent, and data retention. Key concepts include privacy regulations, personal data identification, data subject rights (access, deletion, portability), consent management, and data retention policies.

As Data Controller, you’re responsible for handling data subject requests, maintaining consent records, and ensuring transparent data use.

Learn more about Privacy management

Campaign provides tools for privacy compliance, but legal responsibility rests with you. Work with legal counsel for your privacy program.

Essential actions:

• Establish processes for handling data subject requests (access, deletion)
• Implement consent management with timestamps and scope tracking
• Include unsubscribe links in all marketing emails
• Audit data sources and remove unused data
• Apply least-privilege access controls

Campaign offers Privacy Core Service integration, consent tracking, automated deletion workflows, and audit trails for compliance.

Learn more about Privacy management

Valid consent requires active, specific, informed, and revocable agreement. Users must take explicit action—no pre-checked boxes or silence as consent. Separate consents for different purposes (unbundled), provide clear explanations, and maintain records with timestamps.

Best practices: Provide granular opt-in options, periodically refresh consent, make preference centers easy to access, and frame consent as building trust.

Technical implementation in Campaign:

Campaign provides subscription services, preference centers, opt-out flags, and custom consent fields for tracking consent.

• Extend recipient schema for consent fields (date, type, source)
• Create subscription services for each consent type
• Build preference center web forms
• Use workflows to enforce consent in targeting
• Maintain audit trails

Consult legal counsel to ensure your implementation meets regulatory requirements.

Related topics:

Subscription services | Privacy and consent | Privacy management

Campaign automatically deletes all data linked to a data subject: recipient profile, delivery and tracking logs, custom data with ownership relationships, and subscription history.

How it works: Campaign deletes all data where the link to the recipient has integrity="own" in the schema definition, ensuring cascading deletion across related tables.

You can customize deletion scope by modifying link integrity in schemas, but consult legal counsel first. Deletion is permanent and cannot be undone.

Related topics:

Privacy management | Schema links

No. Campaign reports are based on pre-calculated aggregated metrics (total sent, opens, clicks), not live queries on individual logs. Deleting individual recipient data doesn’t change historical aggregate statistics.

Overall delivery statistics and performance metrics remain intact, while individual tracking logs and personal details are removed. This allows you to maintain marketing analytics while respecting data subject rights.

Related topics:

Privacy management | Reports

You must delete data from all source systems, not just Campaign. Data often flows from external systems (CRM, e-commerce, data warehouses).

Required actions: Identify all data sources, delete from source systems, add to exclusion/suppression lists, update import workflows to respect deletion flags, and document the process.

As Data Controller, you’re responsible for complete data removal across your entire technology ecosystem.

Related topics:

Privacy management | Import workflows

Yes. Data subjects can opt in again after deletion. Campaign creates a completely new recipient record with no link to previous deleted data—the profile starts with a clean slate.

Campaign’s audit trail records both the deletion event and new profile creation, demonstrating compliance and showing the new opt-in was freely given after deletion.

Related topics:

Privacy management | Subscriptions