Implementing Audience Manager and Outbound E-mail
Audience Manager enables marketing departments to gather information about audiences, such as interests and characteristics. Outbound E-mail is for marketing departments that need to implement and manage e-mail communication campaigns. This section describes how to implement Audience Manager and Outbound E-mail.
- Audience Manager and Outbound E-mail system diagram
- The system diagram shows the software components and services that send and tracking Mailings for Outbound E-mail and collect Contact data for Audience Manager.
- Address Books
- Address Books are used to organize and secure your Contacts so that only users with the necessary rights and access permissions can manage and send e-mails to certain Contacts. This section describes how to create and manage Address Books.
- Contact Subscription
- Audience Manager ships with sample ASPX and JSP Web pages Web pages that implement a basic subscription model for .NET and Java Web sites.
- Custom Contact extended details
- Outbound E-mail comes with a default set of extended detail fields and default fields to uniquely identify Contacts. You must configure the Contacts database to change these defaults, add your own Contact extended details and change the unique index.
- Audience Manager cartridge
- The Audience Manager cartridge puts Segments, Contact details and Contact extended details into the Claim Store as Claims. You need to install and configure the Audience Manager cartridge in the Web application in which your Web site is running.
- Target Groups
- A Target Group defines a category of user. In Outbound E-mail, you can personalize the content of a Mailing using Target Groups.
- User rights and permissions
- You need to set up user rights and permissions for Audience Manager and Outbound E-mail users to restrict access to certain content and specify the tasks a user is allowed to perform.
- System settings_ user accounts_ rights and permissions
- This section describes the Audience Manager and Outbound E-mail subsystems and services and the rights and privileges each part requires.
- Mailings (Modular Templating)
- You implement Mailings by assembling the default Outbound E-mail Template Building Blocks into a Page Template that is used in a Mailing and by modifying the Dreamweaver Template used to render the content of a Mailing.
- Mailings (VBScript)
- You can use the Outbound E-mail Script Extension to implement Mailings. The VBScript Templating Framework is supported for backwards compatibility. It is recommended to use the Modular Templating Framework based on the .NET platform.
- Outbound E-mail Script Extension API
- You can access the Outbound E-mail Script Extension to create Page Templates or Component Templates written in VBScript or Jscript. This appendix describes the methods and properties in the Outbound E-mail Script Extension API.
- Audience Manager and Outbound E-mail APIs and examples
- The Audience Manager and Outbound E-mail APIs allow you to customize and extend Audience Manager on the Content Manager Server (.NET) and APIs to access Audience Manager Contacts and Segments and Outbound E-mail Tracking on the presentation server (.NET or Java).
- Connecting to the Content Manager (Core Service)
-
Audience Manager and Outbound E-mail are configured by default to communicate with the Core Service using the
NetTcpBindingbinding. You can change the configured endpoint to usewsHttpBindingbinding in theOutboundEmail.xmlconfiguration file. You can also create your own custom binding. - Monitoring Audience Manager and Outbound E-mail processes
- Application monitoring allows you to monitor the status of Audience Manager and Outbound E-mail processes.