Connectors
Number of Posts: 7
Filter By:
Number of Posts: 7
article-img
Marketing & Commerce | March 8, 2021
Configuring HCL Unica Deliver with HCL Unica Campaign
With the HCL Unica Deliver product introduction in version 12.1, we can say that HCL Unica Suite is a complete martech solution.
article-img
Marketing & Commerce | January 22, 2021
Unica Journey – Handling Dynamic Content using Decision and Engagement Split
HCL Unica Journey is a product developed for marketers, helping them design the entire customer journey using different capabilities of Unica Journey like Touchpoints, Engagement split, Decision splits, etc.
article-img
Marketing & Commerce | December 25, 2020
Integration of Unica Campaign with Unica Link
This integration enables Campaign to send data to customers’ in-house developed delivery system, which sends email or SMS based on each custom configuration as per the client requirements.
article-img
Marketing & Commerce | October 1, 2020
Configuring HCL Unica Campaign with Amazon Redshift Database
Marketers these days are more involved and skilled with using data than ever. The customer information is gathered, stored, and retrieved from a central database, and it is increasing exponentially.
article-img
Marketing & Commerce | July 30, 2020
Unica V12.1 = 4; Are You Ready for More?
we’re going to illustrate how Unica V12.1 harnesses the power of the number 4. This means we’re going to show you 4 key features of our new integrated cloud-native platform and 4 functions that make each of the 4 features work!
article-img
Marketing & Commerce | April 29, 2020
Understanding Campaign Listener Clustering and Listener Failover – Part 2
Clustered Listener Environments With the introduction of Clustered listener setups in Campaign, you have to think of them as a setup with multiple independently operating listener nodes that are being directed requests from a centralized entity. Each listener process behaves as it would in a single listener environment (See Part 1 of this Blog for more information), independently starting up and shutting down unica_acsvr processes local to its machine and maintaining its own unica_aclsnr.udb file. Each listener node does NOT share information. They act like individual, independent SINGLE listener nodes even though a "master listener" is managing them. The following shows a depiction of what a Clustered Campaign Listener setup would look like. Think of a master listener process as a load balancer. When a request comes down from the Campaign J2EE Web application server to login to Campaign or to view/edit/run a flowchart, instead of the Campaign web application talking to a specific listener to do that, it passes those requests over to the master listener in a clustered setup. The master listener then reviews its configuration settings to know which child listener node should take on this task. Once the Master listener determines which child listener node should receive the request, the request is passed along to that child listener node. At that point, the child listener node on that specific machine processes the request as if it was a single listener node running in a non-clustered setup. It spawns applicable unica_acsvr processes, and those unica_acsvr processes perform the requested action. The listener node then updates its local copy of unica_aclsnr.udb to understand the unica_acsvr's it's managing. No other child listener in the cluster has any idea about what other child listeners are working on. All activity is localized to a single child listener node. The child listener...
article-img
Marketing & Commerce | January 30, 2020
Unica and Email Service Provider (ESP) Integration – Best Practices
Let’s Geek out on Unica! Best Practices Blog post: Unica and Email Service Provider (ESP) integration. I think 2020 will be shaping up to be the year where everyone starts to realize they have too much tooling to manage in their martech stacks. I have been getting many requests lately around best practices for getting tools to work together or to provide clarity about what function should be performed in which tool in the stack. Recently, one of our banking customers reached out for some advice. They have outgrown their current email service provider, replacing them with a larger enterprise-grade email engine. They hit me with two questions: What are the best practices around integrating our new ESP and Unica? How do we architect the integration to get the most out of both platforms? The first question is pretty straightforward, as Unica was designed to integrate with any ESP.  With the release of Unica - version 12 later this year, it will be even easier with Unica Link (more information in a future post) to achieve seamless integration. The second question is endemic of my opening prediction – confusion on the part of marketers about “what gets done where” because of the proliferation of tooling. Just because we can do segmentation or A/B testing in a given solution doesn’t mean we should. The answer also requires an understanding of the functionality in the context- how a customer is set up operationally. There’s no one right solution. So on to the answers: Diagram 1 below shows what we call the Unica to ESP “return trip” integration. Step one is to generate the email records to be sent to the ESP as a result of a flowchart run in an output list. This is specified in the mail list process box in...
Close
Filters result by
Sort:
|