Adobe Campaign Implementation Guide for v8, Step by Step

An Adobe Campaign implementation follows a set order. You agree your use cases, design the data model and integrations, and have Adobe provision your Campaign v8 environments. Then you set up sending domains, build and test, and warm up your sending IP (Internet Protocol) addresses before you send at full volume. For one brand with email plus one other channel, plan on a first production send in about 12 to 20 weeks. That's our indicative range, not an Adobe figure.

This guide covers each phase: who does what, where settings live and where projects slip. New to the product? Read Adobe Campaign explained first, and see what Adobe Campaign can do for the feature tour.

What are the phases of an Adobe Campaign implementation?

We split a Campaign v8 project into nine phases. Several overlap, since provisioning and deliverability setup usually run during design.

How long does an Adobe Campaign implementation take?

These durations are planning ranges from delivery work, not Adobe data. They assume one brand, one market, email plus one other channel, two or three data feeds and no migration. Five factors move the Adobe Campaign implementation timeline most:

• Channels. Each extra channel (SMS, push, direct mail) adds setup, templates and testing.
• Data sources. Every feed needs mapping and an import workflow, and a customer relationship management (CRM) connector adds sync design.
• Brands. Each brand usually needs its own subdomains, branding settings and templates.
• Markets. More languages and consent rules mean more content variants and legal review.
• Migration. Coming from an older Campaign version or another platform adds an inventory, a rebuild and parallel running.

Multi-brand programs and migrations often take 6 to 12 months. IP warm-up is the one step with an Adobe benchmark. Adobe's deliverability guide says up to eight weeks is common for typical senders to build a reputation at most major mailbox providers.

What drives the cost?

Adobe doesn't publish Campaign prices, so budget from the drivers. Your license sets entitlements such as active profiles, which the Control Panel tracks for you. Your package sets how many mid-sourcing instances send your messages. Add-ons such as Campaign Optimization (unless your offering includes it) and Enhanced security add more. Services cost follows the timeline drivers above, and our page on Adobe Campaign pricing factors covers them in detail.

How do you scope use cases and design the solution?

Start with a written list of use cases, not a feature list. For each one, note the trigger, audience, channel, data needed and success measure.

Then decide what belongs in Campaign at all. Scheduled and batch programs suit Campaign well. Real-time, event-led messages may suit Adobe Journey Optimizer better, and many teams run both. Our comparison of Journey Optimizer vs Adobe Campaign helps draw that line. Still choosing a vendor? Settle that first with Adobe Campaign vs Salesforce Marketing Cloud.

Solution design turns use cases into decisions you'll live with for years:

• Data model: which tables, fields and keys you need.
• Integrations: which systems feed Campaign, and how often.
• Roles: who builds, who approves and who presses send.
• Domains: which subdomains carry marketing mail and which carry transactional mail.
• Environments: where you build and test, and how changes reach production.

What does Adobe provision, and what does your team set up?

Campaign v8 runs only as an Adobe Managed Cloud Service, so every Adobe Campaign v8 implementation starts with Adobe provisioning your environments. Adobe sets the environment and initial configuration under your license, and you can't modify built-in packages, schemas or reports. Capabilities that weren't provisioned go through your Adobe Transition Manager.

You get production and non-production environments, and you move configuration between them with packages.

Most of the Adobe Campaign setup on your side happens in the Campaign Control Panel, Adobe's self-service admin tool:

• IP allow listing. By default your instance can't be reached from just any IP address. Add office or virtual private network (VPN) ranges for console access, plus ranges for application programming interface (API) and Adobe Experience Manager (AEM) connections.
• SFTP. Most instances have SFTP (secure file transfer protocol) servers for file exchange. You add public SSH (secure shell) keys and allow-list the IP addresses that connect.

Users sign in with an Adobe ID and are created in Adobe's Admin Console. In Campaign, users are operators and operator groups represent roles. Match each operator group to a product profile, give each person their own operator and keep admin rights to a few. Marketers can use the web interface, while admins and developers also need the Windows client console, kept on the same version as the server.

How do you set up deliverability for Adobe Campaign?

Start with a dedicated sending subdomain, such as email.yourbrand.com, delegated to Adobe through the Control Panel. Adobe recommends full subdomain delegation, where it manages all the domain name system (DNS) records needed to send, render and track email. A CNAME (alias record) setup is the alternative, with DNS duties shared between you and Adobe.

Adobe's documentation sets a few rules worth following:

• Never delegate your root domain. If you do, that domain will only work with Adobe.
• Split marketing and transactional mail. Adobe recommends separate subdomains, and the Control Panel asks which use case each one serves.
• Pick the first subdomain with care. On a new instance, the first becomes the primary subdomain and can't be changed later.
• Wait for the audit. Adobe's deliverability team audits each new subdomain, which can take up to 10 business days. Don't send before it's done.

Adobe configures Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) by default. Domain-based Message Authentication, Reporting and Conformance (DMARC) is set up on request. For fully delegated subdomains, you can also add DMARC records in the Control Panel.

Then comes IP warm-up. New sending IPs have no history, so mailbox providers treat big sends from them with suspicion. Start small with your most engaged subscribers, send on a steady rhythm and grow volume step by step. You can't bring established IPs over from another email platform, so Adobe suggests ramping up on Campaign while winding down the old one. For the programs that follow, see email automation using Adobe Campaign.

How do you build the data model and integrations?

Get the data model right first, because every workflow and template depends on it. Campaign's built-in model centers on the recipient (profile) table, with tables for deliveries and their logs. Adobe recommends starting from that recipient table, since features such as subscriptions and seed lists already work with it.

You customize it by extending a schema with new fields, such as a loyalty tier, or by creating a linked table, such as purchases. Adobe's test for each attribute is simple: is it used for segmentation, data management or personalization? If not, leave it out. In Adobe's words, Campaign is neither a data warehouse nor a reporting tool.

Your deployment model matters too. Campaign v8 comes in two models: FDA (Federated Data Access), where PostgreSQL is the main database, and Enterprise, or FFDA (Full Federated Data Access). In FFDA, customer data sits in a Snowflake cloud database. Custom tables must live there, data updates should run through workflows and the platform favors batch work over frequent single-record writes.

Most teams combine four routes for data integration:

• File imports in text, CSV, TAB or XML format, run by scheduled import workflows.
• Workflows that clean, deduplicate, enrich and update data on a schedule.
• APIs for systems that write to Campaign directly. Technical accounts sign in through Adobe's Identity Management System (IMS), and Adobe limits API throughput.
• CRM connectors for Microsoft Dynamics and Salesforce, synced through a workflow activity. Federated Data Access can also query external databases without changing your data model.

Give each custom table a business key from its source system, such as a customer number. Adobe recommends this, and it makes imports, matching and packages much easier.

How do you build and test templates, content and workflows?

Build reusable templates before single campaigns. In Campaign, campaigns, deliveries, jobs and workflows are all based on templates, and delivery templates are a requirement in v8. Lock the shared parts (header, footer, unsubscribe link, tracking) into templates so every send starts compliant.

Next, set your typology rules. Control rules check messages before they go out. Pressure rules (for fatigue) and capacity rules come with Campaign Optimization, which is included or an add-on depending on your offering.

If your content team works in AEM, it can build emails there and sync them into Campaign deliveries. Marketers can also insert images from AEM Assets. On Managed Cloud Services, Adobe enables the Adobe Campaign and AEM integration on request.

Workflows carry most of the automation. Follow Adobe's workflow advice from day one. Use clear names and numbered labels, and set a supervisor group that gets error emails. Keep one scheduler per branch, and never edit production workflows directly.

Testing relies on two tools:

• Proofs are test sends that approvers check before the main send. Send a fresh proof after every change.
• Seed addresses (called test profiles in the web interface) are test addresses added to real deliveries. They're left out of open, click and unsubscribe reports.

Seed addresses live in their own table, so when you extend the recipient table, extend the seed table with the same fields. Finish with user acceptance testing (UAT), where real marketers run real use cases end to end.

How do you go live, run hypercare and hand over?

Go live in waves, not with one big send. Start with your most engaged audiences, then add segments as the warm-up plan allows. For transactional mail, Adobe suggests moving one message type at a time where needed, starting with high-engagement ones such as purchase confirmations.

Hypercare is the period after launch when the build team watches everything closely. Agree its length, owners and exit criteria before launch day. Daily checks usually cover delivery reports, bounces, quarantines, workflow errors and failed imports.

Treat handover as a launch condition. Train by role: marketers on deliveries, proofs and the web interface; admins on operators, the Control Panel and monitoring; developers on schemas, workflows and packages. Keep runbooks, naming rules and a data dictionary in your own systems.

What changes if you're migrating from Campaign Classic v7 or Standard?

A migration is a fresh implementation that also carries history, so plan it as one.

From Campaign Classic v7

Adobe says automated migration from Campaign Classic v7 to v8 isn't available yet, and v8 can't run on-premise or in a hybrid setup. Most v7 concepts carry over, but some don't:

• No longer supported: LDAP (Lightweight Directory Access Protocol) sign-in, user and password sign-in, Facebook social marketing and hybrid or on-premise hosting.
• Not in the FFDA deployment: Marketing Resource Management, coupons, web tracking and surveys.
• Custom code: code that writes straight to the database needs rework.
• Routing: all deliveries go through the mid-sourcing server, so internal routing no longer works.

Adobe's support matrix lists 31 December 2030 as the end of core support for Campaign Classic v7. That gives you time, but talk to your Adobe representative about the path early.

From Campaign Standard

Adobe says Campaign Standard users can now move to Campaign v8 on Managed Cloud Services, working with an Adobe Transition Manager. Adobe moves your data, and security groups become operator groups. Watch these points:

• Logs: historical workflow logs don't carry over.
• Keys: primary key values change, so integrations that store them must read them from the v8 APIs instead.
• Privacy: your Standard environment stays active for a while, so privacy requests may arrive in both systems.

The transition pages don't give a cut-off date, so confirm timing with your Adobe account team. Adobe Campaign migration services cover the inventory, rebuild and parallel running for either route.

Which Adobe Campaign implementation mistakes should you avoid?

Most troubled projects trip over the same few things:

• Loading everything. Importing every attribute "just in case" wastes database space and clutters the data model.
• Full volume on day one. New IPs and subdomains need a slow ramp, and sending before the audit ends risks your reputation.
• Waking old addresses on new IPs. Adobe advises re-permissioning inactive contacts on your current platform first.
• Editing production directly. Test in non-production and promote with packages.

Your next steps

• Write down your top use cases, each with its data, channel and success measure.
• Pick your sending subdomains and confirm who owns DNS changes.
• List every data source with its owner, format and frequency.
• Agree environments, roles and the approval flow.
• Put Adobe's provisioning and deliverability steps in the plan early, since they run on Adobe's clock.

You can see how DWAO's Adobe-certified Campaign consultants handled a large program in Tata AIA's Campaign transformation. If you'd like a second opinion on your Adobe Campaign implementation plan, our Adobe Campaign implementation service page shows how we scope the work.