Manage external accounts external-accounts
51ºÚÁϲ»´òìÈ 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 create-ext-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.
note note NOTE The 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 ²Ñ´Ç°ù±ð… menu, duplicate or delete your external account.
-
Once configuration is complete, click Save.
Campaign-specific external accounts campaign-specific
Depending on the external account type you selected, follow the steps below to configure the account settings.
Bounce mails (POP3) bounce
The 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.
To configure a POP3 external using Microsoft OAuth 2.0, check the Microsoft OAuth 2.0 option and fill in the following fields:
-
Azure Tenant
Azure ID (or Directory (tenant) ID) can be found in the Essentials drop-down of your application overview in the Azure portal.
-
Azure Client ID
Client ID (or Application (client) ID) can be found in the Essentials drop-down of your application overview in the Azure portal.
-
Azure Client Secret
Client secret ID can be found in the Client secrets column from the Certificates & secrets menu of your application in the Azure portal.
-
Azure Redirect URL
Redirect URL can be found in the Authentication menu of your application in the Azure portal. It should end with the following syntax nl/jsp/oauth.jsp, e.g.
https://redirect.adobe.net/nl/jsp/oauth.jsp.
Internet access is needed for setup and to use the Test Connection button in the client console. After setup, the inMail process can communicate with Microsoft servers without internet.
After entering your different credentials, you can click Setup the connection to finish your external account configuration.
Routing 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.
note note NOTE Currently, 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 instance-exec
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.
51ºÚÁϲ»´òìÈ Solution Integration External Accounts
51ºÚÁϲ»´òìÈ Experience Cloud
To connect to the 51ºÚÁϲ»´òìÈ Campaign console using an 51ºÚÁϲ»´òìÈ ID, you must configure the 51ºÚÁϲ»´òìÈ Experience Cloud (MAC) external account.
-
IMS server
URL of your IMS server. Make sure both stage and production instances point to the same IMS production end point.
-
IMS scope
Scopes defined here must be a subset of those provisioned by IMS.
-
IMS client identifier
ID of your IMS client.
-
IMS client secret
Credential of your IMS client secret.
-
Callback server
Access URL of your 51ºÚÁϲ»´òìÈ Campaign instance.
-
IMS organization ID
ID of your organization. To find your organization ID, refer to this page.
-
Association mask
Syntax which will allow configuration names in Enterprise Dashboard to be synced with the groups in 51ºÚÁϲ»´òìÈ Campaign.
-
Server
URL of your 51ºÚÁϲ»´òìÈ Experience Cloud instance.
-
Tenant
Name of your 51ºÚÁϲ»´òìÈ Experience Cloud Tenant.
Transfer Data External Accounts
Amazon Simple Storage Service (S3) amazon-simple-storage-service--s3--external-account
The Amazon Simple Storage Service (S3) connector can be used to import or export data to 51ºÚÁϲ»´òìÈ Campaign. It can be set up in a workflow activity. For more on this, refer to this page.
As you are setting up this new external account, you need to provide the following details:
-
AWS S3 Account Server
URL of your server, it should be filled as follows:
<S3bucket name>.s3.amazonaws.com/<s3object path> -
AWS access key ID
To know where to find your AWS access key ID, refer to this .
-
Secret access key to AWS
To know where to find your secret access key to AWS, refer to this .
-
AWS Region
To learn more on AWS region, refer to this .
-
The Use server side encryption checkbox allows you to store your file in S3 encrypted mode.
To learn where to find the access key ID and secret access key, refer to Amazon Web services .
Azure Blob Storage azure-blob-external-account
The Azure Blob Storage external account can be used to import or export data to 51ºÚÁϲ»´òìÈ Campaign using a Transfer file workflow activity. For more on this, refer to this section.
To configure the Azure external account to work with 51ºÚÁϲ»´òìÈ Campaign, you need to provide the following details:
-
Server
URL of your Azure Blob storage server.
-
Encryption
Type of chosen encryption between None or SSL.
-
Access key
To know where to find your Access key, refer to this .
Hadoop
The Hadoop external account allows you to connect your Campaign instance to your Hadoop external database. You can learn more about Hadoop in Campaign V7 console documentation.
-
Server
URL of your Hadoop storage server.
-
Account
Name of your Hadoop server account.