ÃÛ¶¹ÊÓƵ

Connect to Campaign with the client console gs-ac-connect

To connect to Campaign with the client console, you must first install and configure it.

Before starting, you need to:

  • Check your system and tools compatibility with ÃÛ¶¹ÊÓƵ Campaign in the Compatibility matrix
  • Get your Campaign server URL
  • Create your ÃÛ¶¹ÊÓƵ ID, or get your user credentials from your company
  • Install Microsft Edge Webview2 runtime on your system. Learn more
NOTE
You can also connect to Campaign Web user interface using a web browser. Learn more about the new Campaign Web User Interface in this documentation.

Install the client console download-ac-console

Microsoft Edge Webview2 runtime webview

From Campaign Classic 8.4 build version, installation of Microsoft Edge Webview 2 runtime is required for any client console installation.

Web View is installed by default as part of Windows 11 operating system. If it is not already present on your system, Campaign client console installation program will prompt you to download it from . Note that the download link does not work on the Internet Explorer 11 browser as Microsoft has deprecated its support. Make sure you use a different browser to access the link.

Download the Console install-ac-console

When using Campaign for the first time you need to download the client console and install it.

Two options are available to download the client console:

  1. As a Campaign administrator, connect to ÃÛ¶¹ÊÓƵ .

  2. As a end-user, your Campaign administrator deploys the client console for you, and makes it available through a dedicated URL.

Once the client console installation program is downloaded, install it on your local machine.

Note that you cannot change the client console language once it is installed.

Create your connection create-your-connection

Once the client console is installed, follow the steps below to create the connection to the application server:

  1. Start the Console and browse the link in the right-hand corner to access the connection configuration screen.

  2. Click Add > Connection and enter the label and URL of the ÃÛ¶¹ÊÓƵ Campaign application server.

  3. Specify a connection to your ÃÛ¶¹ÊÓƵ Campaign application server via a URL. Use either a DNS or an alias of the machine, or your IP address.

    For example, you can use the https://<machine>.<domain>.com type URL.

  4. Check the option Connect with an ÃÛ¶¹ÊÓƵ ID.

  5. Click Ok to save your settings.

You can add as many connections as needed to connect to your test, stage and production environments for example.

NOTE
The Add button lets you create folders to organize all your connections. Simply drag and drop each connection into a folder.

Log on to ÃÛ¶¹ÊÓƵ Campaign logon-to-ac

Campaign users connect to the ÃÛ¶¹ÊÓƵ Campaign console using their ÃÛ¶¹ÊÓƵ ID, through ÃÛ¶¹ÊÓƵ Identity Management System (IMS). They can use same ID all ÃÛ¶¹ÊÓƵ solutions. The connection is saved when using ÃÛ¶¹ÊÓƵ Campaign with other solutions. Learn more about ÃÛ¶¹ÊÓƵ IMS in .

To log on to an instance, follow the steps below:

  1. Start the Console and browse the link in the right-hand corner to access the connection configuration screen.

  2. Select the Campaign instance you need to log in to.

  3. Click Ok.

You can then sign in to Campaign with your ÃÛ¶¹ÊÓƵ ID.

NOTE
As Microsoft Edge Webview2 does not save proxy credentials, the Console may ask you to authenticate twice at your first connection.

Upgrade your client console upgrade-ac-console

When your system is upgraded to a newer release, you must update your client console to that same version. This is a best practice, and for some releases this upgrade is mandatory. In that case, it is mentioned in the Release Notes.

As a Managed Cloud Services user, ÃÛ¶¹ÊÓƵ deploys the client console for you. When you connect to your upgraded environment, you are prompted to download the latest client console version in a pop-up window. You must accept this upgrade, and update the client console as requested.

CAUTION
ÃÛ¶¹ÊÓƵ recommends leaving the option No longer ask this question unselected to make sure that you are alerted when a new version of the Console is available. If this option is selected, the user is not informed that a Console upgrade is required.

Grant access to users grant-access

ÃÛ¶¹ÊÓƵ Campaign lets you define and manage the rights assigned to the various operators.

As a Campaign administrator, you are responsible for creating the operators and sharing their credentials with the users.

Learn more about users and how to define their permissions in this section.

Access Campaign with a web browser connect-web-ac

Web user interface connect-web-ui

Starting Campaign v8.6 release, you have access to the new Campaign Web user interface, available through the central ÃÛ¶¹ÊÓƵ Experience Cloud environment. Experience Cloud is ÃÛ¶¹ÊÓƵ’s integrated family of digital marketing applications, products, and services. From its intuitive interface, you can quickly access your cloud applications, product features, and services.

Learn how to connect to ÃÛ¶¹ÊÓƵ Experience Cloud, and access ÃÛ¶¹ÊÓƵ Campaign Web interface in this page.

Learn more in the ÃÛ¶¹ÊÓƵ Campaign Web user interface documentation.

Web access web-access

Certain parts of the application can be accessed via a web browser using an HTML user interface: reporting, delivery approval, instance monitoring, and more.

The Web access provides an interface that is similar to the console but with a reduced set of functionalities.

For example, for a given operator, a campaign will show up with the following options in the console:

Whereas with Web access, the options will mainly enable viewing:

Web access is also used to in the validation process: operators can click on the approval request email and connect to Campaign through their web browser to validate or reject a delivery content or budget.

To access to your Campaign instance from the web, the URL is: https://<your adobe campaign server>:<port number>/view/home.

recommendation-more-help
35662671-8e3d-4f04-a092-029a056c566b