Hosting models hosting-models
ÃÛ¶¹ÊÓƵ Campaign offers a choice of three hosting models, providing flexibility and freedom to choose the best model, or models to suit business needs.
Managed Services / Hosted
ÃÛ¶¹ÊÓƵ Campaign can be deployed as a Managed Service: all components of ÃÛ¶¹ÊÓƵ Campaign, including the user interface, the execution management engine, and the customer’s Campaign database are fully hosted by ÃÛ¶¹ÊÓƵ, including email execution, mirror pages, tracking server, and externally-facing web components such as unsubscribe page/preference center and landing pages.
As a hosted customer, most of the installation and configuration steps are performed by ÃÛ¶¹ÊÓƵ. You can access the following sections to customize your implementation:
- Configure tracking and mirror page URLs per brand. For transactional messages, refer to this section.
- Install the client console: refer to this section.
- Learn more on the deliverability tools and best practices by reading the detailed documentation.
- Configure Campaign options: refer to this section.
- Configure CRM connectors: refer to this section.
On-premise
ÃÛ¶¹ÊÓƵ Campaign can be deployed on-premise: all components of ÃÛ¶¹ÊÓƵ Campaign, including the user interface, execution management engine and database reside on-site in the customer’s data center. In this deployment model, the customer manages all software and hardware updates and upgrades, and a dedicated database administrator needs to perform maintenance and optimization tasks to ensure Campaign instance management.
As an on-premise customer, before starting deploying Campaign Classic, take care of the following prerequisites and recommendations:
- Read out the Compatibility matrix which lists all versions of the systems and components supported for ÃÛ¶¹ÊÓƵ Campaign.
- Depending on your environment, read out the prerequisites for Windows and prerequisites for Linux.
- Learn recommendations related to database engines in this section.
- Check the required database access layers are installed on the server and accessible from the ÃÛ¶¹ÊÓƵ Campaign account. Learn more.
- Configure your networks as some processes need to communicate with others or to access the LAN and internet. This means that some TCP ports need to be open for these processes. Learn more about Network configuration requirements.
- Read out .
- Check general guidelines for estimating hardware requirements for on-premise deployment .
Hybrid
When deployed as a hybrid model, the ÃÛ¶¹ÊÓƵ Campaign solution software resides on-premise at the customer site, and execution management is delivered as a cloud service by ÃÛ¶¹ÊÓƵ. ÃÛ¶¹ÊÓƵ Campaign marketing instance is installed inside a customer’s firewall, so personally identifiable information (PII) remains in-house and only data required to personalize emails is sent to the Cloud for email execution. The execution instance, hosted in the Cloud, receives the requests from the On-premise instance to deliver emails. This instance personalizes all the emails and delivers them. No data of any kind is permanently stored in the cloud.
As a hybrid customer, most of the installation and configuration steps are performed by ÃÛ¶¹ÊÓƵ. You can access the following sections to customize your implementation:
- Configure transactional messages: refer to this section.
- Configure tracking and mirror page URLs per brand. For transactional messages, refer to this section.
- Install the client console: refer to this section.
- Install built-in packages: refer to this section.
- Deliverability: configure MX rules and email formats. Learn more on the deliverability tools and best practices by reading the detailed documentation.
- Configure Campaign options: refer to this section.
- Configure an external database (Federated Data Access): refer to this section.
- Configuring CRM connectors: refer to this section.
- To learn more on mid-sourcing deployment principles, refer to this section.