Campaign v8 Blueprint

Adobe Campaign v8 is the next-gen campaigning tool built for traditional marketing channels such as email and direct mail. It provides robust ETL and data management capabilities to help craft and curate the perfect campaign. Its orchestration engine provides for rich multi-touch marketing programs with a core focus on batch-based driven journeys. It also comes paired with a scalable real-time messaging server that enables marketing teams to send pre-defined messages based on a all-inclusive payload from any IT system for things such as password reset, order confirmation, e-receipt’s and much more.


Use Cases

  • Highly complex batch based messaging programs
  • Onboarding and re-marketing campaigns
  • Direct Mail advertising, brochure and magazine campaigns
  • Simple transactional messaging (i.e. password reset, email receipts, order confirmations, etc.)
  • Integration of Campaign data to Adobe Experience Platform for analysis and profile building
  • Sharing of Real-time Customer Data Platform audiences to Campaign.

Architecture

Reference architecture for Campaign v8 Blueprint

Integration Patterns

Scenario Description Capabilities
Journey Optimizer with Adobe Campaign Shows how you can use Adobe Journey Optimizer to orchestrate 1:1 experiences utilizing the Real-Time Customer Profile and leverage the native Adobe Campaign transactional messaging system to send the message Leverage the Real-Time Customer Profile and power of Journey Optimizer to orchestrate in the moment experiences while utilizing the native real-time messaging capabilities of Adobe Campaign to do the last mile communication

Considerations:
  • Can send up to 1M messages per hour via the Real-Time Message server
  • No throttling is performed from Journey Optimizer so ensure technical vetting by a Pre-Sales Enterprise Architect
  • Decision Management is not supported in payloads to Campaign v8

Prerequisites

Application Server and Real-Time Messaging Server

  • The Adobe Campaign Client Console is required to interact and use the Campaign v8 software. It is a windows based client and uses standard internet protocols (SOAP, HTTP, etc.). Ensure you have the necessary permissions enabled in your org to distribute, install and run software

  • IP Address Allow Listing

    • Identify the IP ranges that all users will leverage during access to the client console
    • Identity which enterprise systems will be allowed to talk to the Real-Time messaging server and ensure they have a statically assigned IP or range that you can allow list
    • This can be setup and controlled via the Campaign Control Panel
  • sFTP Key Management

    • Have SSH public keys available to use with the Campaign provided sFTP. This can be setup and controlled via the Campaign Control Panel.

Email

  • Have a subdomain ready to be used for message sending
  • Subdomain can either be fully delegated to Adobe (recommended) or CNAMEs can be used to point to Adobe-specific DNS servers (custom)
  • Google TXT record is needed for each subdomain to ensure good deliverability

Mobile Push

  • Have a mobile developer available to deploy, configure and build the mobile app
  • Adobe is only providing a SDK to collect the necessary information from FCM (Android) and APNS (iOS) to send message payloads to their servers. How the mobile app needs to be coded, deployed, managed and debugged is the responsibility of the customer

Webapps (optional)

  • Can delegate an additional subdomain for Campaign hosted unsubscribe and landing pages
  • SSL certificate is highly encouraged

Guardrails

Application Server sizing

  • Storage can be scaled to up 200M profiles with potential to scale up to 1B profiles
  • Setup and control user access via Adobe Admin Console
  • Data loading to Campaign is expected to be done through batch files
    • API data loading support is primarily for managing of profiles or simple objects within the database (i.e. create and update). It is not intended to be used for loading large volumes of data or batch like operations.
    • Using APIs to read data for custom application purposes is not supported
    • Data loaded via API is staged in the application database and then replicated every hour to Cloud database
  • API calls are limited to 15 per second or 150k per day at scale

Batch Messaging Server sizing

  • Can scale to handle up to 20M messages per hour

Real-Time Messaging Server sizing

  • Can send up to 1M messages per hour
  • By default two real-time messaging servers are provisioned. Ability to scale up to eight real-time messaging servers.

SMS Configuration

  • Campaign provides the ability to integrate with a SMS provider. The provider is procured by the customer and integrated with campaign for sending SMS based messages
  • Support is via the SMPP protocol
  • There are three (3) different kinds of SMS all of which Adobe can support:
    • SMS MT (Mobile Terminated): an SMS that is emitted by Adobe Campaign towards mobile phones through the SMPP provider.
    • SMS MO (Mobile Originated): an SMS that is sent by a mobile to Adobe Campaign through the SMPP provider.
    • SMS SR (Status Report) or DR or DLR (Delivery Receipt): a return receipt sent by the mobile to Adobe Campaign through the SMPP provider indicating that the SMS has been received successfully. Adobe Campaign may also receive SR indicating that the message could not be delivered, often with a description of the error.

Mobile Push Configuration

  • Only the Campaign SDK is supported for Campaign v8. Contact Adobe Customer Care to get access

  • Please follow the Campaign SDK documentation to learn how to install and configure the SDK

    IMPORTANT

    Other Experience Cloud applications will require the use of the Experience Platform Mobile SDK for data collection. This is a different SDK and will need to be installed along side the Campaign SDK


Implementation Steps

See the getting started guide for Implementing Adobe Campaign v8

On this page