Documentation Campaign Campaign Adoption Guide

Get started for admin & developers acs-gs-admin

Last update: Thu Nov 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

Beginner
Experienced
Admin
Developer

This page gives an overview of the key administrative and data management functionality of Campaign v8. It is for administrators and technical marketers transitioning from Campaign Standard to Campaign v8.

The major change for you is the introduction of the client console, the native application which communicates with the Adobe Campaign application server.

The Campaign client console centralizes all capabilities and settings. It is synchronized with the Campaign Web user interface, ensuring consistency accross both environments.

{modal="regular"}

Learn more about the client console user interface of Adobe Campaign v8 .

Campaign v8 architecture acs-gs-admi-archi

Campaign architecture is detailed in Campaign v8 (console) documentation. Learn basics in this page.

Useful link for you to start:

Adobe Campaign components and global architecture are described in this page.
Refer to Get Started with Campaign architecture to understand the Campaign architecture before starting to structure your instance.

Transactional messaging (Message Center) is the Campaign v8 module designed for managing triggered messages. It relies on a specific architecture model which is detailed in this section.

Campaign client console acs-gs-console

Install the client console acs-gs-admin-console

Administration and configuration tasks are performed in the client console. The first step is to set up your environment.

Campaign client console is a native application, which communicates with the Adobe Campaign application server through standard internet protocols, such as SOAP and HTTP. Campaign client console centralizes all capabilities and settings, and requires minimal bandwidth as it relies on a local cache. Designed for easy deployment, Campaign client console can be deployed from an internet browser, updated automatically, and does not require any specific network configuration as it only generates HTTP(S) traffic.

The following video explains how to download and install the Adobe Campaign Client Console and manage your connection to your instance.

https://video.tv.adobe.com/v/335375?quality=12&learn=on

For more information, see Connect to Campaign with the client console.

Note that the client console must be installed in a supported environment. Learn more in Campaign v8 (console) compatibility matrix.

Discover the client console interface acs-gs-ui

Learn about the Adobe Campaign V8 user interface and how to navigate the main features with this tutorial video.

https://video.tv.adobe.com/v/334496?quality=12&learn=on

Transcript

Welcome to Adobe Campaign. In this video, you’ll learn how to navigate the Campaign user interface. Campaign provides a business user interface designed for marketers called the Home view that provides an overview of all the marketing activities. From this view, the marketer can see and access all the marketing activities they’re working on. Campaign also provides an interface for technical users like administrators or developers called the Explorer. This interface provides a full view of all the data and configurations with the Campaign.

See Work with the client console for more details.

Administrate the environment acs-gs-admin-env

Once the client console is installed, follow the steps in this documentation to create the connection to the application server: Connection to the application server documentation.

Security practices are deeply ingrained into our internal software development and operations processes and tools and are rigorously followed by our cross-functional teams to prevent, detect, and respond to incidents in an expedient manner. Learn more in Campaign Security best practices.

Access rights and permissions acs-gs-admin-rights

Adobe Campaign lets you define and manage the rights assigned to users. These permissions are defined by combining operator group permissions, named rights and permissions on folders.

As a Campaign Standard user transitioning to Campaign v8, your permissions and access rights remain the same. Security groups have been moved by Adobe to the Campaign v8 operator groups, and your permissions per organizational units have been transitioned to folder permissions. Campaign users use their Adobe ID to connect to Campaign v8, and then can use the same login and password as in Campaign Standard.

Campaign folders are nodes in the explorer tree of the client console. Based on their type, they contain certain types of data. Programs are materialized by folders in Campaign v8. You can create folders and manage permissions to them to restrict access. Learn more.

Learn more in the User permissions documentation.

Campaign Control Panel acs-gs-admin-cp

As for Campaign Standard, you can use the Control Panel to administrate your environment. Note that for v8, the Control Panel provides additional capabilities.

Campaign Control Panel helps you increase efficiency in your work as a product admin of Adobe Campaign, by allowing you to manage settings and track usages for each of your instances. Its intuitive interface lets you easily monitor usage of key assets, as well as perform administrative tasks such as IP addresses allow list addition, SFTP storage monitoring, key management, and more.

Learn more in the Control panel tutorials and the Control panel documentation.

Add IP addresses - Campaign Control Panel allows you to set up new connections to your instances by adding IP addresses ranges to the allow list. Learn more in the IP allow listing documentation
Subdomain configuration - You can configure a sub-section of your domain (technically a “DNS zone”) for use with Adobe Campaign.
Learn more in the Subdomain delegation documentation
Manage SFTP servers - In the Control Panel, you can interact with all SFTP servers that are connected to Campaign instances that you have access to. Learn more in the SFTP management documentation

Audit trail acs-gs-admin-audit-trail

As already available in Campaign Standard, the Audit trail can be used in Campaign v8 to access the complete history of changes made within your instance.

In Adobe Campaign Web User Interface, the Audit trail capability provides users with full visibility into all modifications made to important entities within your instance, typically those that significantly impact a smooth operation of the instance. Learn more in the Audit trail documentation

Data packages acs-gs-admin-audit-packages

Similar to what can be achieved in Campaign Standard, administrators can define packages to exchange resources between different Adobe Campaign instances through structured XML files. These can be configuration parameters or data.

You can use data packages to export and import your platform custom settings and data. A package can contain different types of configurations and components, filtered or not. Learn how to work with data packages in Campaign v8 in this documentation.

Personalize the user interface acs-gs-admin-ui

Several options are available to you to customize the user interface in the client console, such as:

List and data display - Guidelines for managing user interface settings like lists, units, or data display are available in this document: User interface settings documentation
Folder management - Folders are objects in Adobe Campaign that allow you to organize your components and data. They are also used to manage permissions. Learn how to work with folders.
Custom fields - Custom fields are additional attributes added to the out-of-the-box schemas through the Adobe Campaign console. These custom fields are displayed in various screens, for example the details of a profile or a test profile. Learn more in the custom fields configuration documentation.

Configure the branding acs-gs-admin-branding

Every company has brand guidelines that define both visual elements and technical details. As for Adobe Campaign Standard, Adobe Campaign v8 helps you manage these guidelines centrally, so you can present a consistent brand image to your customers in everything you do, from logos in emails to the URLs and domains used in your campaigns. As a technical administrator, you can create and manage multiple brands within Adobe Campaign.

Learn more in the Branding documentation

Understand data model creation acs-gs-admin-data-model-creation

Similar to Campaign Standard, Adobe Campaign v8 comes with its pre-defined data model. Adobe Campaign relies on a Cloud database containing tables that are linked together. Learn more in the Data model documentation.

A schema is an XML document associated with a database table. It defines data structure and describes the SQL definition of the table. See the Schemas creation documentation

Learn how to create a schema and how to extend an existing schema in Campaign v8 in this video:

https://video.tv.adobe.com/v/337939?quality=12&learn=on

Transcript

Welcome. In this video, I will explain how to create schemas, and I will show you how to update an existing schema. If you are familiar with Adobe Campaign Classic, I will also point out the differences between the two versions. Let’s jump right in and create a schema.

Navigate to the Explorer tab.

And then under Administration, Configuration, you will find the data schemas. Here you can see all data schemas that are available in the product. Let’s create a new one.

So we will create a new table.

I’ve prepared an example. Let me paste that into the field.

As you can see, this is a list of products. That’s a very simple example. It has three attributes being three columns, the product SKU, product title, and product description. All of these are strings. In addition, we will create an internal key on the root node. So we’ll have an additional column which contains the key and it should be auto-generated. We need to make sure that autopk is set to true, as well as autouuid. This is specific to Campaign v8. In v8, the system creates UUIDs. Unlike in v7, where the IDs are numerical IDs and are counted up by one every time a new data set is ingested.

You can also see that by default, the data source is the cloud database. Whereas with V7, it’s the local database. There’s one more thing you need to be aware of.

If you create a table and want it to be exposed to the API and you know you will have a lot of access to this table, unitary calls mainly, updates and so on, then you should enable the staging mechanism by setting autostg to true. If you want to learn more about the staging mechanism, we do have a separate video available on this. So I will save the schema.

You can see it listed here.

Now we need to update the database structure to make sure the changes are applied.

You can see that two tables will be created. The new table that will be located on the cloud database and will contain the list of products. And, because we have enabled the staging mechanism, there’s a second table, which will be on the local database. It is a copy of the first table, so it will contain the same data structure. Let’s take a closer look. Remember, we created a new table with three columns and one internal key. We now have two tabs because we have multiple sources. The first one is for the cloud database. So what will happen there? We will create a new table, that is the list of products with the three attributes, the description, the SKU, and the title, as well as the internal key, which will be the UUID, which will be auto-generated each time a new data set is ingested.

The second tab, the default tab, is a table on the local database, which was created because we enabled the staging mechanism. It is a copy of the first table with some additional attributes.

When I click on Start, it’ll execute the SQL on both sides, first on the cloud database and then on the local one.

Okay, so the tables have been created. When you look at the tables, we now have a table with the products. It has the three attributes plus the key. And we have the local staging table, which of course is still empty. The way these tables will be used is the following. If we want to ingest the data through APIs, we will use the local staging table. If, however, we want to ingest the product list through data management and the batch workflows, we will use the main product table on the cloud database.

Next let’s extend the schema.

We will extend the out-of-the-box operator table.

The table we need to extend is the XTK table.

So let’s add a new attribute.

And we want to extend the operator table.

Let’s see. The table we need is the XTK table.

We’ll add a new attribute, the business unit.

And I will save the extension and update the structure.

Yes, the new column will be added.

So let me execute. Okay, now let’s take a look and see what happened. You will need to refresh the page, and there should be the new attribute, the business unit. We have extended the XTK schema on the local database and due to the data replication mechanism and Campaign v8, the XXL schema on the cloud database was synced and updated as well. You can see it here, but you will not be able to see the XXL table in your UI as all of this happens automatically in the background. If you want to know more about the data replication mechanism, this is covered in a separate video.

So, now you know how to create new schemas and how to extend the schema in Campaign v8. Thank you for watching. -

Similar to the capabilities available in Campaign Standard, you can create custom resources. IN Campaign v8, custom resources are custom or extended schemas.

Learn how to work with schema in this page.
Learn how to extend an existing schema in this page.
Learn how to create an new schema in this page.
When you create or extend a schema, you need to create or modify the associated input forms to make those changes visible to end-users. An input form lets you edit an instance associated with a data schema from the Adobe Campaign client console. The form is identified by its name and namespace. See the Input forms creation documentation.

Workflows and data management acs-gs-admin-data-management

Same as with Adobe Campaign Standard, Adobe Campaign v8 includes a workflow module that empowers you to orchestrate the full range of processes and tasks across the different modules of the application server. This comprehensive graphical environment lets you design processes including segmentation, campaign execution, file processing, human participation, etc. The workflow engine executes and tracks these processes. Learn how to start with workflows in Campaign v8 in this documentation.

See links to other useful resources below:

Learn what targeting dimensions and working tables are, and how Adobe Campaign manages data across different data sources in this video:

embed
https://video.tv.adobe.com/v/339992?quality=12&learn=on

embed

https://video.tv.adobe.com/v/339992?quality=12&learn=on

Campaign helps you add contacts to the Cloud database. You can load a file, schedule and automate multiple contact updates, collect data on the Web, or enter profile information directly into the recipient table. Learn more in the Import data (console) documentation.
You can easily export your different reports to PDF or CSV format, which enables you to share, manipulate, or print them. Learn more in the Export data documentation.

REST APIs acs-gs-admin-apis

Campaign REST APIs are aimed at letting you create integrations for Adobe Campaign and build your own ecosystem by interfacing Adobe Campaign with the panel of technologies that you use.

As a Campaign Standard user transitioning to Campaign v8, REST APIs are available to you.

Learn more in the Rest API documentation.

Note that some recommendations and limitations apply to REST APIs when transitioning from Campaign Standard to Campaign v8. They are listed in this page. Specific restrictions also apply when transitioning to Campaign v8 as listed in the Availability note below:

AVAILABILITY

PKEYs values change between existing Campaign Standard instance and migrated Campaign v8 instance. In case PKEYs are being stored in external database then the implementation needs to change in a way that they need to call Adobe Campaign v8 main APIs which provides pkeys / hrefs links with PKEYs and sub sequent API calls need to be dynamically formed by consuming the pkeys /hrefs from previous API calls
In Campaign v8, for the same body where vehicle linked to profile, we would get an error firstName property is not valid for cusVehicle but a request body with just the attributes without link works fine. { "vehicleNumber": "20009", "vehicleName": "Model E", "vehicleOwner":{ "firstName":"tester 11", "lastName":"Smith 11" } }
Timezone is shown to user as part of profileAndServicesExt/profile REST API call and not profileAndServices/profile REST API call since it is being added in an extended schema as part of data migration.
The ccpaOptOut is only shown to user as part of profileAndServicesExt/profile REST API call and not profileAndServices/profile REST API call since it is being added in an extended schema as part of data migration.

Subscription services acs-gs-admin-sub

Like in Campaign Standard, as an administrator, you can create subscription services and marketers can send messages to their subscribers. Key concepts and implementations steps are aligned with Campaign Standard. You can find useful links and video below.

Learn how to setup and manage subscriptions and target subscribers.

https://video.tv.adobe.com/v/334305?quality=12&learn=on

Transcript

Welcome to Adobe Campaign. In this module, we will learn how to configure and manage subscription services. By the end of this module, you should be able to explain services and subscriptions, manage subscriptions, and target subscribers. Adobe Campaign enables you to create and administer information services such as newsletters and manage a subscription to these services. The subscription service allows you to maintain subscriber lists of people who agreed to be contacted. Their incentive to subscribe is to get special offers, information that is of interest to them, or invitations to special events. Several services can be defined in parallel. For example, newsletters can contain product categories, subscriptions to various types of alert messages, and real-time notifications. Subscribers are a self-selected audience. This is important to note because they are less likely to mark our emails as spam or complain about them because they opted in. In other words, they have asked to be targeted. Adobe Campaign keeps track of the current subscribers as well as their history. Adobe Campaign also keeps track of anyone who has subscribed, unsubscribed, and when. There are built-in loyalty reports and there are predefined filters in Adobe Campaign that help you target subscribers to a particular service. You can also enable your delivery recipients to share them with members of their social or professional network. An information service is comprised of registrations, subscriptions, opt-ins, and so on. As a standard feature, these services include specific statistical reports, subscriber tracking, loyalty level, and other trends. For emails, the mandatory unsubscription links are generated automatically and the entire opt-in, opt-out process is fully automated. This includes history tracking to fully guarantee compliance with regulations. In Adobe Campaign, our subscription service is similar to a list but it also includes historical information. The subscriber has the ability to add or remove themselves from the subscription through a web form accessible through a link. There are three service subscription and unsubscription modes, manual, importing, and web form. When managing subscriptions, it is important to note that unsubscribing is different from opting out. When recipients unsubscribe from a service, they can still get other marketing communications. On the other hand, when they opt out globally, it won’t matter that they are subscribed to the service. The global opt-out flag overwrites subscriptions and ensures that they do not receive any communications. Now let’s open Adobe Campaign and create an information service. In your Adobe Campaign instance, navigate to profiles and targets. A list of all the services and subscriptions populates. If you want to edit a service or subscription, select the name and you will be redirected to the dashboard of the service. To close the service, select the X in the service tab. If you want to create a new service or subscription, select the create button and a pop-over appears. Provide a name for your service, then in the confirmation messages section, configure the confirmation messages for a subscription or unsubscription. To do this, select the drop-down arrow to reveal the delivery templates. These templates must be configured with a subscription type target mapping without the defined target. You can uncheck the unlimited option to define a duration for the service. The duration can be specified in days or months. Once the service has been saved, it is added to the service and subscriptions list. Let’s take a look at our new service. In the service tab for our travel newsletter, we have several additional tabs available, dashboard, edit and subscriptions. Let’s navigate to the subscriptions tab. This tab lets us look at the history of subscribers from the information service. Using the active subscribers and history tabs in the bottom left, we can add and delete subscribers from the subscription tab. Right click and select add, or select add in the top right to add subscribers. The select recipients pop-over appears. Here we can select the folder where our recipients are stored, and then select one or more recipients from the list. To select multiple recipients, hold the shift key while making the selection. For this demo, only one recipient is selected. Once completed, select OK, and then Yes. To delete subscribers, select the subscriber we wish to remove, followed by either right clicking and selecting the delete option, or by selecting delete in the top right corner. The detail button in the top right lets us look at and modify subscription properties for the selected recipient, such as the email format. Now the question is, how can we track our subscriptions? Navigate back to the dashboard tab, then select reports in the top right. Here we can track the changes in the subscriptions. In targeting subscribers, we can expect better results compared to mass mailings. These targeted subscribers have asked to receive communication and are therefore far more likely to open emails and participate in promotions and campaigns. A successful campaign keeps the content personal, relevant and consistent without too many notifications. If you want to take things a step further, ask your subscribers how often they would like to receive communication from you. This is not part of the default data model, but it may be something you want to do with your implementation. We can then target subscribers in your campaign workflow by using predefined filtering on subscribers to a service. Next, let’s look at how we can target subscribers using queries. In your Adobe Campaign instance, open the targeting and workflows tab. Then within targeting, drag and drop the query activity to the workspace. Next, double-click the query to open the query popover, then select edit query. The targeting and filtering dimension popover appears. From this popover, double-click subscribers of an information service. Next, select the travel newsletter that we just created. We can also preview and see our recipient list by selecting preview in the bottom left of the window. Once we’ve reviewed our recipients, select finish. We’ve now set up a workflow to target our subscribers. We could now make use of the email delivery activity and send subscribers the new travel offers we created for the next month, or we could create a new delivery from the delivery dashboard and target our subscribers in a similar manner. Now, you should be able to explain services and subscriptions, as well as manage subscriptions and target subscribers. Thanks for watching.

See the subscription services Web user interface documentation.
See also the documentation to set subscriptions services in the client console in this section.

Messages and deliveries acs-gs-msg

Configure delivery channels acs-gs-admin-channels

As Campaign Standard, Adobe Campaign v8 helps you send cross-channel campaigns including emails, SMS, 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 assistant. This access point leads to multiple capabilities covered by Adobe Campaign.

As an administrator, you must define your channel configurations. Refer to the links below to learn more.

Email - Email settings are all detailed in this page.
SMS - Learn how to configure your SMS channel in this documentation.
Push notifications - Steps to configure the push notifications channel are detailed in this section.
Transactional messaging - Steps to configure Transactional messaging in Campaign v8 are detailed in this section

External accounts acs-gs-ext-accounts

As an administrator, you are responsible for configuring and maintaining Campaign external accounts. As in Campaign Standard, external accounts are used by technical processes such as technical workflows or campaign workflows.

The transition process to Campaign v8 takes care of your existing Campaign Standard external accounts.

Learn more in the External account documentation.

Dynamic content acs-gs-dyn-content

Use Campaign to create dynamic content and send personalized messages. Personalization capabilities can be combined to improve your messages and create a custom user experience.

With Campaign v8, as an administrator, you can define dynamic content blocks and how to use them to personalize the content of your email delivery in this video:

https://video.tv.adobe.com/v/342088?quality=12&learn=on

Transcript

In this section, we will demonstrate how to add personalizations to your deliveries. In Adobe Campaign, you can personalize content or the appearance of messages, and combine them with criteria from recipients’ profiles. Let’s take a closer look at how to create a personalization block.

To access a personalization block folder via the explorer review, navigate to resources, Campaign management, personalization block. A personalization block is dynamic, personalized, and contains specific rendering code that can be added to deliveries. For example, you can add images, email headers, email footers, mirror page links, and subscription links, and much more.

You’ll notice there are several out of the box personalization blocks available to you, or you can also create custom blocks.

To create a customized personalization block, click on the new icon. Then add a label and a unique internal name.

Check the following tick box. The content of the personalization block depends upon the format, HTML or text.

This check box forces rendering in either HTML or text format depending on the recipient’s mailbox settings.

You’ll now notice an HTML in a source tab at the bottom of your screen. Best practice is to input the HTML content via the source tab.

Add to your content.

For this example, we’ll type in, “For more information, visit Adobe Campaign’s help page.” We will then highlight the section, “Adobe Campaign’s help page” part of the text, and add a hyperlink by clicking on the hyperlink icon in the toolbar menu.

Once the hyperlink window opens, add your URL to hyperlink, and change the target to new window for the URL to open in another browser window upon click.

Click add to save your changes.

You’ll notice basic HTML coding has been added to the source code to enable the hyperlink.

Additional HTML coding can be added to format any content block to fit in your HTML template.

In addition, we will add two line breaks before the content to force spaces between paragraphs.

Here are the line breaks.

You have just created a new personalization block.

You can now insert your block into delivery template or workflow delivery activity.

Open it in existing delivery.

In our case, we will add our personalization block right here.

Navigate to the delivery source tab. Locate and position your cursor in the content in the area where you want to add the personalization block.

Click on the personalized field icon, select include from the dropdown menu, and then select the other option.

Select the custom personalization block from the personalization block folder.

Note that the out of the box personalization blocks are also accessible via this folder.

In the source in HTML tabs, this will generate the personalization block with the internal name that was added with the following syntax.

To view how the newly created personalization block renders in the creative, go to the delivery preview tab.

Click on test personalization, select the recipient, and scroll down in the creative until you can see the block that was added.

To make adjustments to the personalization block rendering, you’ll need to update the block in the resource folder for the changes to apply in the delivery template. This is very helpful when you need to apply the same changes to multiple deliveries at the same time.

You can also add out of the box personalization blocks to your HTML content. -

Useful links:

Delivery templates acs-gs-templates

Using delivery templates is a requirement in Campaign v8, like in Campaign Standard.

For an accelerated and improved design process, create delivery templates to easily reuse custom content and settings across your campaigns. This functionality enables you to standardize the creative look and feel, in order to be quicker in executing and launching campaigns. Learn how to create delivery templates in Campaign web user interface. See also how to create delivery templates in the client console in this section.

Typology rules acs-gs-admin-rules

As an administrator, you are responsible for creating and maintaining typology rules for your deliveries. Same as in Adobe Campaign Standard, in Campaign v8, typology rules are business rules that allow you to perform checks and filtering on your message before sending it.

When transitioning to Campaign v8 from a Campaign Standard environment, your typoligy rules are moved to Campaign v8.

In Campaign v8, typology rules come with a specific Campaign Optimization ass-on. This module which lets you control, filter and monitor the sending of deliveries. To avoid conflicts between campaigns, Adobe Campaign can test various combinations by applying specific constraint rules. This guarantees that the messages sent meet the needs and expectations of customers and company communication policies. Learn more in the Typology rules documentation.

Quarantine management acs-gs-admin-quarantine

All quarantined addresses and quarantine rules have been migrated from your Campaign Standard environment to Campaign v8. No specific action is needed for quarantine management.

As an administrator, get familiar with quarantine management in Campaign v8 starting from this page. See also the client console detailed documentation about quarantine management in this section.

Manage Adobe Campaign integrations acs-gs-integrations

You can connect your Campaign instance with Adobe Experience Cloud solutions to combine capabilities. Adobe Campaign comes with several connectors that allow you to communicate with external applications, connect to database engines, share and synchronize data. Learn how to combine your solutions in this documentation.

As a Campaign Standard user migrating to Campaign v8, the following applies to you:

If you were using these integrations with Campaign Standard, your Adobe Analytics and Audience Manager configurations and data have been migrated by Adobe.
If your Campaign Standard environment was integrated with Adobe Experience Manager, Adobe recommends you to move to Adobe Experience Manager as a Cloud Service so that you can use this capability when designing emails in the Campaign Web user interface, and facilitate the streamlined management of email delivery content and forms directly within your Adobe Experience Manager environment. Learn more in this page.
Note that Campaign can also be integrated with Adobe Experience Manager 6.5. To configure this integration, refer to this documentation.
If your Campaign Standard environment was integrated with Triggers, you must set up and configure this integration in Campaign v8 as detailed in this page.
If your Campaign Standard environment was integrated with Adobe Target, you must set up and configure this integration in Campaign v8 as detailed in this page.

recommendation-more-help

9af4c60b-1f7d-4c0e-a34a-c78c7dd3fc45