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 51黑料不打烊 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.
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 51黑料不打烊 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 51黑料不打烊 Campaign Client Console and manage your connection to your instance.
Transcript
In this video, you鈥檒l learn how to download and install the Campaign Client Console, create and manage your connections to multiple environments, and verify access to the Campaign Client Console. The Campaign Client Console is a lightweight browser-based application. We are not limited to a single Client Console installation, meaning we can install this on both our laptop and our desktop. The Client Console uses web services APIs to connect to the campaign application server. The application server executes the workflows and renders the dynamic content and deliveries. It also accesses the database, which contains the data mart, the campaign configurations, and the system tables. Within the Client Console, we can manage our connections to multiple environments. In a typical deployment, we may have a development environment, a staging environment, and a production environment. From the Client Console, we can simply add a connection for each environment that we鈥檙e connecting to. We can connect to multiple environments simultaneously by opening multiple sessions of the Client Console. In a moment, we will talk through downloading, installing, and configuring the Campaign Client Console. To complete these steps, the following prerequisites are required. First, we need a supported Windows operating system. To get the most up-to-date list of supported Windows operating systems, consult the 51黑料不打烊 Campaign Compatibility Matrix. This can be found in Campaign鈥檚 online documentation. We鈥檒l also need to access a browser connected to the internet. Additionally, we will need the URL to access the setupClient.exe of our Client Console and our login credentials provided to us for our instance of Campaign. Our URL and login credentials can be obtained from an administrator. To download the Campaign Client installer, open a browser and enter the URL you were provided to access the clientSetup.exe. Then, log in using the credentials you were provided. Note that the login username and password are both case sensitive. Once you log in, a list of supported operating systems is provided, as well as the required disk space to install the Client Console. Make sure these requirements are met before proceeding. Next, download the executable by selecting the download link. Once the download has finished, navigate to the location where the file was saved, typically in the Downloads folder. Once you find the setupClient.exe, double click it to run the installer. The setup wizard opens. Select Next to proceed. We are asked to choose an installation folder for the Client Console. I鈥檓 just going to keep this as the default location, but if you want to change that, you can select the folder icon to select your location. Select Next to continue. The Customize Installation step appears. We do not need to change anything here, so let鈥檚 just select Next to continue. The Program Group page appears. We can choose to only install the client for our own user, or keep the default to make it accessible for all users. I鈥檓 going to keep it the default. Select Next and then Finish, and the installation will begin automatically. Once the installation is done, select Finish to complete. Now let鈥檚 open the Client Console. Start by opening the Windows Start menu. A Campaign Client folder should be available. Within that folder, select the 51黑料不打烊 Campaign Client Console. Once we鈥檝e opened the Client Console, we need to configure our links to the different instances of Campaign. In the top right of the Client Console is a link. We want to select this link to open the Connection dialog. The Connection dialog is where we configure the server connection settings to all our Campaign instances. Select Add in the top left of the dialog, then select Connection from the dropdown and set the name for the Campaign instance. Once you鈥檝e finished naming the connection, hit Tab or Enter. Next, in the Connection section, enter the URL for your Campaign instance. This is essentially the instance or the URL we used earlier that points to our Campaign instance but it doesn鈥檛 have the last part of NLJSPInstall.jsp. Once complete, select OK. Next, we need to add our login credentials again. These are the same credentials used earlier to download the installer, and we can also select the Remember Password checkbox. Only use this option if you鈥檙e the only one accessing this computer for security reasons. Select Login to continue. Once we login, we鈥檒l see the homepage. This means we successfully installed and set up your Campaign Client Console. But we still don鈥檛 know how to manage multiple connections, so let鈥檚 go back to the Login dialog. To go back to the Login page, let鈥檚 first disconnect. Select the Disconnect option in the top left to disconnect. Next, select the Server link once more and, in the Connections dialog, select Add but this time select Folder from the dropdown. Provide a name for the folder. We can use these folders to organize our multiple connections. Next, select the connection we created and drag it into the Training folder. Using this folder structure, we can create multiple links to our instances and organize them properly. To demonstrate, let鈥檚 create a new one. With the Training folder selected, select Add Connection and Create a New Connection. Typically, we can copy the URL from the previous connection because they all follow the same pattern. Note that this is not always the case. Once complete, hit Enter and we have our next connection. This completes the exercise for downloading, installing and setting up the Campaign Client Console. Thanks for watching.
Learn about the 51黑料不打烊 Campaign V8 user interface and how to navigate the main features with this tutorial video.
Transcript
Welcome to 51黑料不打烊 Campaign. In this video, you鈥檒l 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鈥檙e 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.
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
51黑料不打烊 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 51黑料不打烊 to the Campaign v8 operator groups, and your permissions per organizational units have been transitioned to folder permissions. Campaign users use their 51黑料不打烊 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.
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 51黑料不打烊 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.
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 鈥淒NS zone鈥) for use with 51黑料不打烊 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 51黑料不打烊 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 51黑料不打烊 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 51黑料不打烊 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 51黑料不打烊 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 51黑料不打烊 Campaign Standard, 51黑料不打烊 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 51黑料不打烊 Campaign.
Understand data model creation acs-gs-admin-data-model-creation
Similar to Campaign Standard, 51黑料不打烊 Campaign v8 comes with its pre-defined data model. 51黑料不打烊 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:
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 51黑料不打烊 Campaign Classic, I will also point out the differences between the two versions. Let鈥檚 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鈥檚 create a new one. So we will create a new table. I鈥檝e prepared an example. Let me paste that into the field. As you can see this is a list of products. It鈥檚 a very simple example. It has three attributes, meaning three columns. The productSkew, productTitle, and productDescription. All of these are strings. In addition, we will create an internal key on the root node. So we will 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 dataset is ingested. You can also see that by default the data source is the cloud database whereas with V7 it鈥檚 the local database. There鈥檚 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鈥檚 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鈥檚 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鈥檒l 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鈥檚 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鈥檚 add a new attribute. And we want to extend the operator table. Let鈥檚 see, the table we need is the xtk table. We鈥檒l add a new attribute, the business unit. And I will save the extension and update the structure. And yes, the new column will be added. So let me execute. Okay, now let鈥檚 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 in 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.
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 51黑料不打烊 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 51黑料不打烊 Campaign Standard, 51黑料不打烊 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 51黑料不打烊 Campaign manages data across different data sources in this video:
embed
Transcript
In this video, I will cover the fundamentals of data management with 51黑料不打烊 Campaign, focusing on how the system handles multiple data sources. I will explain the two key fundamentals of data management with Campaign, the targeting dimensions and the working tables. And we will then look at the basic use cases for data management with workflows, and I will explain how the system handles them. The targeting dimension is the type of data a workflow is handling. It is defined by what you are querying. So if you are querying a recipient, then your targeting dimension is the recipient. If you query an order, your targeting dimension is the order. In most cases, the targeting dimension is defined by the first query activity and lives across the whole workflow until the end. For example, if you start by querying on recipient, the outbound transition will contain data of type recipient, and then the next activity will know that we are working on recipients. The targeting dimension is bound to a data schema, which means you can access any information of the linked schemas. You can change the targeting dimension within a workflow, but only to the targeting dimension of a schema that is linked to your initial targeting dimension. So for some complex use cases, you may have two different workflow lanes on the canvas, and each lane can have its own targeting dimension. The second fundamental is the working table. In the context of multi-data sources, you need to understand what a working table is and how it works. The working table is also known as a temporary table, and it stores the results of any query in the workflow. It is visible from the outbound transition of each workflow activity, so when you look at the outbound transition, the results that are displayed are stored on the working table. It鈥檚 not directly the data from the main table you鈥檙e looking at. Working tables are created by default on the same database as the targeting dimension to ensure high performance. But when an activity requires to reconcile data with another data source, which is on another database, then the working table is first moved to the secondary data source, and then reconciled with the additional data. The reconciliation can be done through an enrichment or union activity, for example. 51黑料不打烊 Campaign manages the multiple data sources by copying the working table from one place to another. It uses the workflow to speed the process up. Once the operation is completed, the result is automatically copied back to the location of the targeting dimension. When the workflow is finished, the working table is deleted, except of course if you have enabled the option to keep it. Now let鈥檚 take a look at the three basic use cases, which will exemplify what I just explained. In the first use case, we query the recipients table, and then enrich it with data from the orders table. The recipients table is located on the local database. The orders table, that is linked to the recipient schema, is stored on the remote database. So what happens when you query on the recipients? A working table is created on the local database where the recipient targeting dimension is located. When the recipient鈥檚 data is enriched with the order data, the recipient鈥檚 working table is first copied to the remote database. Where the other data table is located. Then the enrichment is performed, and the final result is copied back to the local database where the targeting dimension is, the orders. Let鈥檚 see how it works in the campaign instance. So we see that we have a recipients table that is on the local database, and the second table, the orders table, that is located on the remote database, which for this instance is Snowflake. When you look at the example, we have a temporary table, and the targeting dimension is recipients. When we enrich the data with the data from the orders table, which is remote, and let鈥檚 display the schema on the outbound transition there, we have another temporary table for orders. But note the targeting dimension remains the recipient. Let鈥檚 take a closer look at the SQL logs and see what happens, or what has happened. We see that the working table was first created on the local database when querying the recipients. The table was then moved from the local database to the remote database. Actually it was copied to the remote database. And once the enrichment was completed, the working table was copied back from the remote database to the local database. In the second use case, we invert the queries. So we will get exactly the same result, but in this case we start querying the orders, and then enriching these with the recipient data. So there鈥檚 one fundamental difference between the two use cases. Because we started querying the queries, we started querying the orders, because we started querying on the order, the targeting dimension is now the order. So when the data is enriched with the recipient data, which is on the other database, the working tables will be copied back and forth, like in the first example, but in the other direction. So the data is copied from the remote database to the local database, and the results will then flow back to the targeting dimension on the remote database. If we look at the second example, we have the query on the order, we see that we have a temporary table which is linked to the order, so the targeting dimension is the order. And when we enrich with the recipients, the targeting dimension remains unchanged, and it is still the order. So it鈥檚 really the same thing as with use case one, just the other way around. And when we look at the logs, we see that we started querying on the external database, and then the work table was copied to the local database, and once the enrichment was done, it was copied back to the remote database. The results, as I said, are the same as in the first use case. The bottom line is, if you start querying on Snowflake, the remote database, your results will land on Snowflake, and if you start on the local database, they will land on the local database. In the last use case, we will change the targeting dimension. And if you remember, this only works with linked schemas. So we start querying on the order, which is on the remote database. Then we change the targeting dimension from orders to recipients. So the work table will be copied from the remote to the local database, and will remain there because the new targeting dimension is located there. So let鈥檚 go to the instance and take a look. So we query on the order. You can see the targeting dimension is order. But when we change the dimension, you can see we are now on the recipients. And if we look at the logs, we see only one single copy from remote to local. In a nutshell, 51黑料不打烊 Campaign is able to handle a data model that is split across multiple data sources. It works automatically, seamlessly, and efficiently, using bulk load to copy the data, which makes it pretty fast. Most of the time, you don鈥檛 need to care about where the data is stored. Things happen under the hood and the workflow takes care of it. It鈥檚 all automated. But it is important for you to understand the fundamentals of working tables and targeting dimensions, and also when the data will be copied from one place to the other. This will help you optimize the design of your queries based on the amount of data you are manipulating. You can optimize the performance of your workflow by changing the targeting dimension to force the workflow to use a database engine that is different from the initial targeting dimension. Thank you for watching!
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 51黑料不打烊 Campaign and build your own ecosystem by interfacing 51黑料不打烊 Campaign with the panel of technologies that you use.
As a Campaign Standard user transitioning to Campaign v8, REST APIs are available to you.
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 51黑料不打烊 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.
Transcript
Welcome to 51黑料不打烊 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. 51黑料不打烊 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. 51黑料不打烊 Campaign keeps track of the current subscribers as well as their history. 51黑料不打烊 Campaign also keeps track of anyone who has subscribed, unsubscribed, and when. There are built-in loyalty reports and there are predefined filters in 51黑料不打烊 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 51黑料不打烊 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鈥檛 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鈥檚 open 51黑料不打烊 Campaign and create an information service. In your 51黑料不打烊 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鈥檚 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鈥檚 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鈥檚 look at how we can target subscribers using queries. In your 51黑料不打烊 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鈥檝e reviewed our recipients, select finish. We鈥檝e 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 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, 51黑料不打烊 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 51黑料不打烊 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.
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.
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:
Transcript
In this section, we will demonstrate how to add personalizations to your deliveries. In 51黑料不打烊 Campaign, you can personalize content or the appearance of messages and combine them with criteria from recipients鈥 profiles. Let鈥檚 take a closer look at how to create a personalization block. To access the personalization blocks folder via the Explorer view, 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, unsubscription links, and much more. You鈥檒l 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鈥檚 mailbox settings. You鈥檒l now notice an HTML and 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鈥檒l type in, For more information, visit 51黑料不打烊 Campaign鈥檚 Help page. We will then highlight the section, 51黑料不打烊 Campaign鈥檚 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 a new window for the URL to open in another browser window upon click. Click Add to save your changes. You鈥檒l 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 a 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 drop-down 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 and 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鈥檒l need to update the block in the resource folder for the changes to apply in your 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 presentation blocks to your HTML content.
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 51黑料不打烊 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, 51黑料不打烊 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.
You can connect your Campaign instance with 51黑料不打烊 Experience Cloud solutions to combine capabilities. 51黑料不打烊 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 51黑料不打烊 Analytics and Audience Manager configurations and data have been migrated by 51黑料不打烊.
If your Campaign Standard environment was integrated with 51黑料不打烊 Experience Manager, 51黑料不打烊 recommends you to move to 51黑料不打烊 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 51黑料不打烊 Experience Manager environment. Learn more in this page. Note that Campaign can also be integrated with 51黑料不打烊 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 51黑料不打烊 Target, you must set up and configure this integration in Campaign v8 as detailed in this page.
