Hybrid architecture

Campaign v8 relies on a hybrid architecture. If you are transitioning from Campaign Classic v7, note that all deliveries go through the mid-sourcing server.

As a consequence:

  • Internal routing is not possible in Campaign v8, and the external account has been disabled accordingly,
  • Status of the deliveries is not instantly updated - A technical process runs on the Marketing instance which will update the delivery statuses in a timely manner.

Learn more about sending transactional message proofs when transitioning from v7 on this page.

Campaign and Snowflake

In its Enterprise (FFDA) deployment, Adobe Campaign v8 works with two databases: a local Campaign database for the user interface real-time messaging and unitary queries and write through APIs, and a cloud Snowflake database for campaign execution, batch queries and workflow execution.

Campaign v8 Enterprise brings the concept of Full Federated Data Access (FFDA): all data is now remote on the Cloud Database. With this new architecture, Campaign v8 Enterprise (FFDA) deployment simplifies data management: no index is required on the Cloud Database. You only need to create the tables, copy the data and you can start. The Cloud database technology does not require specific maintenance to guarantee the level of performance.

Learn more about Campaign v8 architecture in this page.