Posted: 18 Apr 2018 16:36 EDT Last activity: 4 May 2018 23:39 EDT
Ask the Expert - Pega Marketing with Saleem Abdelsayed
Ask your questions on Pega Marketing!
Saleem leads the Marketing and Decisioning product teams at Pega. He has been involved with Customer engagement, Marketing and CRM products for over twenty years and has been bringing Marketing & decisioning solutions to market for Pega for close to 18 years.
Message from Saleem:
Hi, I’m passionate about helping clients become successful one to one engagement practitioners. I look forward to answering your questions about how you can use Pega Marketing to achieve unprecedented results as you engage every customer as if you had a personal relationship with them. Please feel free to ask anything from general conceptual questions to specific questions on how to accomplish specific things in the Pega Marketing product to accomplish your objectives. I’ll be happy to share my knowledge and best practices with you.
We are in the process to define the production infrastructure for Outbound campaigns in our project. We already have a production set up for inbound marketing ( basically NBAs over web). I would like to know if there are any basic foundational aspects which we can follow for planning the sizing. What are the key parameters to consider here like number of outbound channels, response processing, delayed learning on D nodes etc. It would be great if you can share something.
I responded to your other post by suggesting you reach out to Pega Service representative to ensure you get your system sized appropriately.
Having said that, at a high level, outbound sizing is primarily driven by heavy batch processing. This will impact your Database, Batch Agent nodes for Campaign processing Segment processing and delivery processing (Email, SMS), DDS nodes (for delayed learning), Interaction History and VBD. Going through your detailed requirements is the only way to size properly, so please do go through the Pega sizing process, where all these dimensions will be accounted for.
We are facing performance issues on campaign runs. We are running 7 million records through the batch outbound campaign using batch decision strategies. Our problem is it is taking 10 plus hours to run on parallel on 28 nodes.
To improve performance what is correct partition key count for customer data?
What is the correct “Thread count”, and “Batch Scalability factor” we should keep? By default, we are using Thread count as 1 and batch scalability factor 2 at data flow nodes edit settings
Is there any formula to keep correct thread count and partition?
Do we have any proper documentation of campaign performance issues? Can you guide is it is really helpful.
Thank you for posting your question. 10 hours for 7M customers definitely suggests your system is not configured correctly. Can you please highlight the version of Pega Marketing you are using as the configurations to highlight are likely to be version specific. Also, you highlight 28 nodes for this system. Can you clarify what type of work they have been designated for? Systems typically have batch processing nodes, VBD nodes, ADM nodes, Delivery nodes (Email/SMS), etc. Understanding how the 28 nodes relate to these will help us to identify better configurations.
The new app wizard is responsible for creating an implementation stack for you and not really an operational deployment strategy. You should continue to reference the documentation to identify the best deployment topology for the types of nodes your use cases will require.
I'm note sure I fully understand your question, but let me answer it as best I can and we can take it from there. Today, bundled offers can be made up of one or more offers/propositions. There needs no be any relationship between the bundle head and its children from a hierarchy perspective. For example, in the Communications vertical, customers often bundle a plan, with a device and some add-ons. Plans, devices and add-ons are typically different parts of the hierarchy, but can get bundled together. The way to accomplish this from a strategy perspective is to include separate concerns responsible for their part of the hierarchy. For example, you might create a overall 'bundle' strategy that includes a plans sub-strategy, device sub-strategy and add-ons sub-strategy. Each of the sub strategies is responsible for their concern and the bundle strategy is responsible for bringing them together in the bundle with any inter-hierarchy rules that might exists.
Crossing the chasm from campaigns to always on marketing.
What a great title and aspiration we should all have as Pega Marketing practitioners. Two of my colleagues, Dr. Robert Walker and Matt Nolan, put together this great paper on this topic and I encourage all of you to read it and consider some of the disciplines it calls out: https://www.pega.com/always-on-engagement
Review and lets see how many of you are aspiring to crossing the chasm.