Building branded Customer Preference Center with Salesforce

Building branded Customer Preference Center with Salesforce, NodeJS & Cloud Compliance

Overview

In few weeks, you can deliver robust marketing preference capability, that protects your company from privacy fines, and keeps Marketing, Legal & Finance happy.

3 things your employer & clients care about Customer Experience, Brand Trust & Compliance Hit all 3 with a branded customer preference portal – How?

You start with any web technology for the Portal, & integrate Salesforce’s customer 360 data model, And sync these preferences with your Marketing apps

A lot of Salesforce customers want to integrate a privacy portal within their website.

Your Marketing wants to offer consistent branding and a customer experience by extending it from the corporate website or an existing portal.

An existing portal can be a WordPress, NodeJS, Salesforce Communities, or some other technology-based solution.

How do you offer an opt-in/opt-out functionality on your current website with your existing Salesforce investments?

Can Salesforce and Cloud Compliance offer consent and preference management functionality that fully integrates?

Let’s take a look at the demo video that has a custom branded preference center. This HTML5 web app has a Node JS backend that is running on Google’s Firebase.

It is a demo website with a hardcoded server-side Salesforce authentication for a specific user and updates their preferences.

This website has checkboxes that correspond to the logged-in user’s preferences on a Salesforce instance.

As these preferences are checked on & off, the Node JS App utilizes Cloud Compliance’s APIs to create opt-out and opt-in Salesforce records.

Consent needs enterprise-wide integration

Consolidating preferences in Salesforce enables Sales, Service, and Marketing to have a single view of preferences and deliver a consistent customer experience & comply with GDPR.

These preferences are accessible from Marketing Cloud, Pardot, Marketo, Eloqua, and MailChimp so that your email outreach respects customer preferences.

Under the hood, our code is making simple REST calls to Cloud Compliance’s APIs hosted in your Salesforce instance – a straightforward and lightweight way for your IT team to extend your portal.

You can build this with any web technology – HTML5, WordPress, NodeJS, PHP, Asp.Net, etc.,

Also, host it on any IaaS – Amazon web services, Azure, Google Cloud, or use Salesforce Communities, if you so prefer.

This approach offers complete design flexibility for your end-user experience while utilizing an enterprise-grade consent management capability.

You can unlock Salesforce’s Customer 360 consent management objects with Cloud Compliance’s automation and API capabilities – thus avoiding heavy Salesforce customization.

Curious to hear if you have done anything like this?

Thanks!