Customer.io vs. Pega Customer Decision Hub

This tool is well-suited for companies looking to run email marketing campaigns or send out newsletters regularly to their users/customers. The workflow setup is especially useful for companies who want to send specific emails based on user behavior - i.e. they've not logged in recently, have bought a specific product, haven't opened any emails, etc. This could also be useful for freelancers like me since you can create different workspaces within Customer.io. I have configured it this way to handle email marketing for a few of my clients, and the software keeps everything organized and separate. This might not be the best tool for small businesses, considering the price. It may be better to start out with a cheaper email marketing tool, and then if/when necessary, scale-up with a tool like Customer.io.

PRPC is a BPM and Case management suite from Pega Systems. Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product but is very difficult to learn. Even, if we go to Pegasystems for training, we have to work on a project at least for a year to have some confidence. Areas where it requires improvements: 1) One of the first things that client's IT department questions about is proprietary BLOB column in PRPC, for them, it is a disadvantage, but as we all know BLOB is what makes the highly complex data model of any BPM application fit inside to a common schema which eliminates the help of a DBA. 2) Another area of improvement is: when using the wizards to generate rules (such as the connector wizards) you have to be careful about the level of coupling between the work object's data model and the interface's data model. This can also create maintenance issues. 3) The complete Pega suite of products have a long time to develop and deploy and it can be easily done using other low-cost software.

Incentivized

• Managing users, attributes and events. You are easily able to modify any user, based on their ID, and add or remove attributes, assign events to them. That makes it very easy to segment later and to assign them to several campaigns based on behavior. Just a warning: this integration isn't so easy (at least it wasn't for us).
• Creating workflows of campaigns is very easy. You can quickly create behavioral campaigns based on attributes, segments and add elements to the workflow. You can send an email, then wait, then send another, then exit the campaign if they converted, etc. The workflow is easy to configure and very powerful for automation.
• We don't use many email templates (we make them in MJML) but it's very easy to add senders, to change templates and in general to test designs.
• Deliverability works very well, at least for us. It sends emails pretty fast and without issues.
• Exporting is very quick and easy. Importing wasn't a feature until recently, but it works well too.
• Seeing activity it's also useful. In general, logs are awesome (be it of a customer, of activity on the site, email sends, etc.).
• We don't use environments, but it might be very useful for a bigger company.

Incentivized

• Ability to design custom integrated campaigns
• Analytics to provide key insights and ability to tune your campaign accordingly
• Ability to design agent workflows

Incentivized

• Push notifications are very rudimentary. Everything has to be done by hand unless you're sending an extremely simple message.
• A bit too email centric.
• Lacks an ability to schedule messages on a daily, weekly, etc. basis.

Incentivized

• Pega Customer Engagement Suite is ready to use out of the box with several features, but custom development is always needed.
• Although new features can be quickly implemented, they have to go through a screening Business analysis process, QA screening and SCRUM based development.
• Pega eliminates the need for custom code, but there are rare cases where an specific requirement has little to no support from Pega, and implementing custom code can break OOB functionality and make the system unstable.

Incentivized

Customer.io was really the first pure, full-featured drip email program on the market and as far as I know, it's still the simplest and best overall for that specific function. SendGrid has also added drip campaign features, but I would seriously evaluate Customer.io against any other drip email provider because they really have all the key elements you need to make it work.

Incentivized

I explained in detail in previous questions.

• Fast testing for new products to specific groups. It saves a lot of time and money.
• Removed workload from marketing = more time to make it better.
• Better contact with specific groups, seeing a increase in sales because of this.

Incentivized

• Cost savings on print marketing and email due to better targeting
• More timely campaigns to reach customers at the right time

Incentivized