External accounts external-accounts
ÃÛ¶¹ÊÓƵ Campaign comes with a set of pre-defined external accounts. In order to set up connections with external systems, you can create new external accounts.
External accounts are used by technical processes such as technical workflows or campaign workflows. For example, when setting up a file transfer in a workflow or a data exchange with any other application (ÃÛ¶¹ÊÓƵ Target, Experience Manager, etc.), you need to select an external account.
Create an external account creating-an-external-account
To create a new external account, follow the steps below. Detailed settings depend on the type of external account.
-
From Campaign Explorer, select Administration ‘>’ Platform ‘>’ External accounts.
-
Click the New button.
-
Enter a Label and an Internal Name.
-
Select your external account Type which one you want to create.
-
Configure the access to the account by specifying credentials depending on the chosen external account type.
The necessary information is usually provided by the provider of the server you are connecting to.
-
Check the Enabled option to activate the connection.
-
Click Save.
The external account is created and added to the external accounts list.
Campaign-specific External Accounts
Bounce mails bounce-mails-external-account
The Bounce mails external account specifies the external POP3 account to be used to connect to the email service. For more on this external account, refer to this page.
All servers configured for POP3 access can be used to receive return mail.
To configure the Bounce mails (defaultPopAccount) external account:
-
Server
URL of the POP3 server.
-
Port
POP3 connection port number. The default port is 110.
-
Account
Name of the user.
-
Password
User account password.
-
Encryption
Type of chosen encryption between By default, POP3 + STARTTLS, POP3 or POP3S.
-
Function
Inbound email or SOAP router
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-external-account
The Routing external account allows you to configure each channel available in ÃÛ¶¹ÊÓƵ Campaign depending on the packages installed.
The following channels can be configured:
Email routing email-routing-external-account
The email routing external account is provided by default, adapted to your configuration.
As an on-premise/hybrid customer, you can create new routing external accounts, or update parameters, as described below. This configuration is reserved to expert users and can impact your deliverability. For any question, contact ÃÛ¶¹ÊÓƵ customer care or your ÃÛ¶¹ÊÓƵ representative.
-
You can use a Mid-sourcing, External routing, or Bulk delivery routing type.
-
For Bulk and Mid-sourcing delivery modes, you can specify your branding parameters in the Branding tab. These parameters are used to override the default parameters for Mirror page URL and Error address with settings specific to your brand.
-
To configure a Mid-sourcing external account, refer to this section
Execution instance execution-instance-external-account
If you have a broken-down architecture, you need to specify the execution instances linked to the control instance and connect them. Transactional message templates are deployed to the execution instance.
-
URL
URL of the server on which the execution instance is installed.
-
Account
Name of the account, it must match the Message Center Agent as defined in the operator folder.
-
Password
Password of the account as defined in the operator folder.
For more information on this configuration, refer to this page.
Access to External Systems External Accounts
FTP ftp-external-account
The FTP external account lets you configure and test access to a server outside of ÃÛ¶¹ÊÓƵ Campaign. To set up connections with external systems such as FTP servers 898 used for file transfers, you can create your own external accounts. For more on this, refer to this page.
To do so, specify in this external account the address and credentials used to establish the connection to the FTP server
-
Server
Name of the FTP server.
-
Port
FTP connection port number. The default port is 21.
-
Account
Name of the user.
-
Password
User account password.
-
Encryption
Type of chosen encryption between None or SSL.
To know where to locate these credentials, refer to this .
SFTP sftp-external-account
The SFTP external account lets you configure and test access to a server outside of ÃÛ¶¹ÊÓƵ Campaign. To set up connections with external systems such as SFTP used for file transfers, you can create your own external accounts. For more on this, refer to this page.
-
Server
URL of the SFTP server.
-
Port
FTP connection port number. The default port is 22.
-
Account
Account name used to connect to the SFTP server.
-
Password
Password used to connect to the SFTP server.
External database (FDA) external-database-external-account
Use the External database type external account to connect to external an database. Learn more about Federated Data Access (FDA) option in this section.
External databases compatible with Campaign are listed in the Compatibility matrix
External account configuration settings depend on the database engine. Learn more in the following sections:
- Configure access to Vertica Analytics
- Configure access to Snowflake
- Configure access to Google BigQuery
- Configure access to Azure Synapse
- Configure access to Hadoop
- Configure access to Oracle
- Configure access to Netezza
- Configure access to SAP HANA
- Configure access to Snowflake
- Configure access to Sybase IQ
- Configure access to Teradata
ÃÛ¶¹ÊÓƵ Solution Integration External Accounts
ÃÛ¶¹ÊÓƵ Experience Cloud adobe-experience-cloud-external-account
To connect to the ÃÛ¶¹ÊÓƵ Campaign console using an ÃÛ¶¹ÊÓƵ ID, you must configure the ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Campaign.
-
Server
URL of your ÃÛ¶¹ÊÓƵ Experience Cloud instance.
-
Tenant
Name of your ÃÛ¶¹ÊÓƵ Experience Cloud Tenant.
For more information on this configuration, refer to this page.
Web Analytics web-analytics-external-account
The Web Analytics external account allows you to forward data from ÃÛ¶¹ÊÓƵ Analytics to ÃÛ¶¹ÊÓƵ Campaign in the form of segments. Conversely, it sends indicators and attributes of email campaigns delivered by ÃÛ¶¹ÊÓƵ Campaign to ÃÛ¶¹ÊÓƵ Analytics connector.
For this external account, the calculation formula for tracked URLs must be enriched and connection between the two solutions must be approved. For more on this, refer to this page.
ÃÛ¶¹ÊÓƵ Experience Manager adobe-experience-manager-external-account
The AEM (AEM instance) external account allows you to manage the content of your email deliveries as well as your forms directly in ÃÛ¶¹ÊÓƵ Experience Manager.
-
Server
URL of the ÃÛ¶¹ÊÓƵ Experience Manager server.
-
Port
Account name used to connect to the ÃÛ¶¹ÊÓƵ Experience Manager authoring instance.
-
Password
Password used to connect to the ÃÛ¶¹ÊÓƵ Experience Manager authoring instance.
For more on this, refer to this section.
CRM Connector External Accounts
Microsoft Dynamics CRM microsoft-dynamics-crm-external-account
The Microsoft Dynamics CRM external account allows you to import and export Microsoft Dynamics data into ÃÛ¶¹ÊÓƵ Campaign.
Learn more about Campaign - Microsoft Dynamics CRM connector in this page.
With Web API deployment type and Password credentials authentication, you need to provide the following details:
-
Account
Account used to sign in to Microsoft CRM.
-
Server
URL of your Microsoft CRM server.
To find your Microsoft CRM Server URL, access your Microsoft Dynamics CRM account then click Dynamics 365 and select your app. You can then find your Server URL in the address bar of your browser, e.g.
https://myserver.crm.dynamics.com/
. -
Client identifier
Client ID which can be found from Microsoft Azure management portal in the Update your code category, Client ID field.
-
CRM version
Choose Dynamics CRM 365 CRM version.
With Web API deployment type and Certificate authentication, you need to provide the following details:
-
Server
URL of your Microsoft CRM server.
To find your Microsoft CRM Server URL, access your Microsoft Dynamics CRM account then click Dynamics 365 and select your app. You can then find your Server URL in the address bar of your browser, e.g.
https://myserver.crm.dynamics.com/
. -
Private Key (Base64 encoded)
Note that the Private key needs to be encoded to Base64.
To do so, you can use the help of a Base64 encoder or use the command line
base64 -w0 private.key
for Linux. -
Custom Key identifier
-
Key ID
-
Client identifier
Client ID which can be found from Microsoft Azure management portal in the Update your code category, Client ID field.
-
CRM version
Version of the CRM between Dynamics CRM 2007, Dynamics CRM 2015 or Dynamics CRM 2016.
For more information on this configuration, refer to this page.
Salesforce.com CRM salesforce-crm-external-account
The Salesforce CRM external account allows you to import and export Salesforce data into ÃÛ¶¹ÊÓƵ Campaign.
To configure the Salesforce CRM external account to work with ÃÛ¶¹ÊÓƵ Campaign, you need to provide the following details:
-
Account
Account used to sign in to Salesforce CRM.
-
Password
Password used to sign in to Salesforce CRM.
-
Client identifier
To know where to find your client identifier, refer to this .
-
Security token
To know where to find your security token, refer to this .
-
API version
Select the version of the API.
For this external account, you need to configure you Salesforce CRM with the configuration assistant.
For more information on this configuration, refer to this page.
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 ÃÛ¶¹ÊÓƵ 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:
code language-none <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 ÃÛ¶¹ÊÓƵ Campaign using a Transfer file workflow activity. For more on this, refer to this section.
To configure the Azure external account to work with ÃÛ¶¹ÊÓƵ 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 .