Prerequisites for Integrating with Adobe Target
- Topics:
- Administering
CREATED FOR:
- Admin
As part of the integration of AEM and Adobe Target, you need to register with Adobe Target, configure the replication agent, and secure activity settings on the publish node.
Registering with Adobe Target
To integrate AEM with Adobe Target, you must have a valid Adobe Target account. This account must have **approver **level permissions at a minimum. When you register with Adobe Target, you receive a client code. You need the client code and your Adobe Target login name and password to connect AEM to Adobe Target.
The Client Code identifies the Adobe Target customer account when calling the Adobe Target server.
Enabling the Target Replication Agent
The Test and Target replication agent must be enabled on the author instance. Note that this replication agent is not enabled by default if you used the nosamplecontent run mode for installing AEM. For more information about securing your production environment, see the Security Checklist.
-
On the AEM home page, click or tap Tools > Deployment > Replication.
-
Click or tap Agents On Author.
-
Click or tap the Test and Target (test and target) replication agent, and then click or tap Edit.
-
Select the Enabled option, then click or tap OK.
NOTE
When you configure the Test and Target replication agent, in the Transport tab, the URI is set by default to tnt:///. Do not replace this URI with https://admin.testandtarget.omniture.com.Please note that if you try to test the connection with tnt:///, it will throw an error. This is expected behavior as this URI is for internal use only and should not be used with Test Connection.
Securing the Activity Settings Node
You must secure the activity settings node cq:ActivitySettings on the publish instance so that it is inaccessible to normal users. The activity settings node should only be accessible to the service handling the activity synchronization to Adobe Target.
The cq:ActivitySettings node is available in CRXDE lite under /content/campaigns/*nameofbrand*
* under the activities jcr:content node; *for example /content/campaign/we-retail/master/myactivity/jcr:content/cq:ActivitySettings
. This node is only created after you target a component.
The cq:ActivitySettings node under the activity’s jcr:content is protected by the following ACLs:
- Deny all for everyone
- Allow jcr:read,rep:write for “target-activity-authors” (author is a member of this group out of the box)
- Allow jcr:read,rep:write for “targetservice”
These settings ensure that normal users do not have access to the node properties. Use the same ACLs on author and on publish. See User Administration and Security for more information.
Configuring the AEM externalizer
When editing an activity in Adobe Target, the URL points to localhost unless you change the URL on the AEM author node.
To configure the AEM externalizer:
-
Navigate to the OSGi web console at https://<server>:<port>/system/console/configMgr.
-
Find Day CQ Link Externalizer and enter the domain for the author node.
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management