Manage external accounts
AVAILABILITY-
External accounts are currently available only for Bounce mails (POP3), Routing, and the Execution instance. Additional account types will be added later.
-
Non-supported external accounts created in Adobe Campaign console are visible in the Web User Interface but cannot be edited or accessed.
Adobe Campaign includes pre-configured external accounts for easy integration with various systems. To connect to additional platforms or customize connections to fit your workflow, create new external accounts using the Web User Interface. This ensures seamless data transfers.
Create an external account
To create a new external account, follow the steps below. Detailed settings depend on the type of external account. Learn more
-
From the left-pane menu, select External accounts under Administration.
-
Click Create external account.
-
Enter your Label and select the external account Type.
NOTEThe settings for Campaign-specific types are detailed in this section.
-
Click Create.
-
From the Additional options drop-down, change the Internal name or Folder path if needed.
-
Enable the Exported automatically in packages option to automatically export data managed by this external account.
-
In the Details section, configure access to the account by specifying credentials based on the chosen external account type. Learn more
-
Click Test connection to verify that your configuration is correct.
-
From the More… menu, duplicate or delete your external account.
-
Once configuration is complete, click Save.
Campaign-specific external accounts
Depending on the external account type you selected, follow the steps below to configure the account settings.
Bounce mails (POP3)
AVAILABILITYThe Bounce mails external account specifies the external POP3 account used to connect to the email service. All servers configured for POP3 access can receive return mail.
To configure the Bounce mails (POP3) external account, fill in the following fields:
-
Server - URL of the POP3 server.
-
Port - POP3 connection port number (default port is 110).
-
Account - Name of the user.
-
Password - User account password.
-
Encryption - Type of chosen encryption, including:
- By default (POP3 if port 110, POP3S if port 995).
- POP3 that switches to SSL after sending a STARTTLS.
- POP3 non-secure (port 110 by default).
- POP3 secure above SSL (port 995 by default).
-
Function - Select Inbound email to configure the account for receiving incoming emails or SOAP router to handle SOAP requests.
Routing
To configure a specific external account for external deliveries, follow the steps below.
-
Create an external account. Learn more
-
Select the Routing type.
-
Select the desired channel and click Create.
-
In the external account Details section, External is selected by default as the Delivery mode.
NOTECurrently, External is the only available mode. -
To handle the process after delivery execution, externalize this to a post-processing workflow. Create a workflow with an External signal activity and select it from the Post-processing field.
-
In the Activity field, edit the name of the post-processing workflow activity displayed in the logs.
Execution instance
If you have a segmented architecture, identify the execution instances associated with the control instance and establish connections between them. Transactional message templates are deployed on the execution instance.
To configure the Execution instance external account:
-
URL - URL of the server where the execution instance is installed.
-
Account - Name of the account, matching the Message Center Agent as defined in the operator folder.
-
Password - Password of the account as defined in the operator folder.
-
Method - Choose between Web service or Federated Data Access (FDA).
For FDA, select your FDA account. Note that Campaign connection to external systems is restricted to advanced users and only available from the client console. Learn more
-
Create archiving workflow - For each execution instance registered in the Message Center, regardless of whether you have one or multiple instances, create a separate archiving workflow for each external account associated with the execution instance.