With Adobe Campaign, you can send cross-channel campaigns including emails, SMS, LINE messages, Push notifications and direct mails, and measure their effectiveness using various dedicated reports. These messages are designed and sent though deliveries, and can be personalized for each recipient.
Core functionalities include targeting, definition and personalization of messages, execution of communications, and the associated operational reports. The main functional access point is the delivery wizard. This access point leads to multiple capabilities covered by Adobe Campaign.
Delivery sending can be automated by preparing a delivery and/or sending it in the process of a workflow. For more on delivery-type activities in workflows, refer to this section.
Adobe Campaign offers the following delivery channels:
Email channel: email deliveries let you send personalized emails to the target population. Refer to About email channel.
Direct mail channel: direct mail deliveries let you generate an extraction file which contains data on the target population. Refer to About direct mail channel.
Mobile channel: deliveries on mobile channels let you send personalized SMS or LINE messages to the target population. Refer to SMS channel.
Mobile application channel: mobile app deliveries let you send notifications to iOS and Android systems. Refer to the Mobile app channel chapter.
Other channels are described on this page.
The number of available channels depends on your contract. Please check your license agreement.
Deliveries can be carried out online (via email, one of the mobile channels and push notifications), and offline (direct mail channel).
Depending on the channel, delivery modes can be:
External accounts are configured via the Administration > Platform > External accounts node. This configuration should be performed by expert users only.
The Email channel is one of the core channels in Adobe Campaign, allowing you to schedule and send personalized emails to specific targets.
You can send different types of emails:
To learn about delivery usage and recommendations, consult Campaign Delivery best practices.
For more on the different types of deliveries, refer to this section.
For SMS messages, you can create, modify, and personalize messages in text format only. You can also preview your SMS messages before they are sent.
For LINE messages, you can send text or images and links.
To deliver SMS or LINE messages to a mobile phone you need:
Adobe Campaign allows you to send personalized and segmented push notifications on iOS and Android mobile devices, through dedicated apps. Once configuration and integration steps have been performed, iOS and Android deliveries can be created and sent. You can also design rich notifications with images or videos.
Direct mail is an offline channel that allows you to personalize and generate the file required by direct mail providers. It gives you the possibility to mix online and offline channels in your customer journeys.
Online channels allow you to create your messages (email, SMS, mobile app delivery, etc.) and send them to your audience directly from Adobe Campaign. With offline channels, it is different. When you prepare a direct mail delivery, Adobe Campaign generates a file including all the targeted profiles and the chosen contact information (postal address for example). You will then be able to send this file to your direct mail provider who will take care of the actual sending.
Adobe Campaign offers Telephone delivery template, which is used to create external deliveries. Using this channel implies you set up dedicated methodologies to process output files. Configuration steps are the same as for Direct mail channel.
The Telephone channel is not available out-of-the-box. Its implementation requires Adobe Consulting or an Adobe Partner to be engaged. Please reach out to your Adobe representative for more information.
In addition, ‘Other’ type deliveries use a specific technical template which does not execute a process: this lets them manage marketing actions executed outside of the Adobe Campaign platform.
This channel has no specific mechanism. It is a generic channel that has its own external account routing option, delivery template type and campaign workflow activity, just like any other communication channel available in Adobe Campaign.
This channel is designed for descriptive purposes only, for example to define deliveries for which you want to keep a trace of the target of a campaign performed in a tool other than Adobe Campaign.
There are three types of delivery objects in Campaign:
A delivery is a standalone delivery object that is executed once. It can be duplicated, prepared again, but as long as it is in its final state (canceled, stopped, finished), it cannot be reused.
Deliveries can be created either from the list of deliveries, or within a workflow via a Delivery activity.
Workflows also provide specific delivery activities according to the type of channel you want to use. For more on these activities, refer to this section.
A recurring delivery lets you create a new delivery each time the activity is executed. This avoids you having to create a new delivery for recurring tasks.
As an example, if you run this type of activity once a month, you will end up with 12 deliveries after a year.
Recurring deliveries are created within workflows via the Recurring delivery activity. An example of this activity being used is presented in this section: Creating a recurring delivery in a targeting workflow.
A continuous delivery lets you add new recipients to an existing delivery, which avoids having to create a new delivery each time it is executed.
If an information in the delivery changes (content, name, etc.), a new delivery object is created at the delivery execution. If no information was changed, the same delivery object is reused and the delivery and tracking logs are added in the same object.
As an example, if you run this type of activity once a month, you will end up with a single delivery after a year (provided you did not make any change to the delivery).
Continuous deliveries are created within workflows via the Continuous delivery activity.