On Tuesday the 10th of September we had a Webinar to demonstrate some of the New SAP Customer Data Cloud Innovations recently released. The Presenters of this session were:
Ratul Shah – Senior Product Marketing Managers, SAP Customer Data Cloud
Ian Hametz – Identity Product Manager, SAP Customer Data Cloud
Stephen Purvis – Product Expert, SAP Customer Data Cloud
In this webinar we talked through the Business need and motivation behind our new Innovations and then demonstated how they can be implemented. Here is the link to the recording of this session https://enable.cx.sap.com/media/How+to+use+the+latest+Customer+Data+Cloud+innovationsF+-+Webinars/1_....
This blog post covers the hands-on section of the webinar and walks you through how you can easily layer our new innovations on top of an existing implementation. We used our Webinar demo site from August as a starting point https://blogs.sap.com/?p=853832. This blog post will walk through the following new innovation:
Account Progression
To understand Account Progression you first need to be familiar with our terms lite account and full account. A lite account is that early stage account where a user whom was previously anonymous has provided some basic information to create an account this could be to sign up for a newsletter or an offers email. Typically no password is created at this stage and in some cases you may only request an email address and consent to receive communications. A full account is where a user provides more detailed profile information typically to register for a service to view exclusive content or to purchase a product. The information provided at this stage is required to complete the transaction and can typically include users names, date of births, country of residence etc.
Account progression from lite to full (https://developers.gigya.com/display/GD/Lite+Registration) : When a new full account is created, either by standard registration, or social or federated login, and the email address used for creating that full account already exists for an email account, the newly created full account will share a UID with the existing email account.
To enable lite progression it's quite a simple process you need to enable the feature via the Site Policies:
Once you have enabled the feature then you can update your screen sets to make it easier for those users with lite accounts to progress to full accounts.
Create a new registration screen specifically for those user who have a lite account, to prevent the capturing data that has previously being captured during the lite reg flow.
Lite Progression to Full Account is now enabled on your site. You can test this on your demo site your previously created. Once you have created your account then you can see what the account looks like in Identity Access.
Within Identity Access you will now see within the Account Identities there will be a site account and lite-email account. Additionally any data and consent entered during the lite registration is carried over to the full account.
Mobile Number as a Login ID
The use of a mobile number with Social Media and Messaging Apps such as WhatsApp are becoming more widely used, so much so that in Asia more and more users just have a Mobile number rather than an email address. To cater for this demand our Mobile Number as a Login ID feature was launched.
Mobile Number as a Login ID allows for customers to enter a mobile number and receive a 4 digit pin code to register/login to their account. A user can use their mobile number alongside existing authentication methods such as social and email helping to expand the authentication methods offered to users yet still providing a single account.
To enable Mobile Number as a Login ID you will need to have an account with either Livelink or Twilio https://developers.gigya.com/display/GD/Phone+Number+Login. As a first step you must enter your mobile provider credentials via our Administration Menu.
When configuring your mobile sms provider you can define a white/black list (regex compatible) to determine which numbers can or cannot be used to authenticate with. A great use cases would be to restrict access to only those users whom are using numbers from the UK e.g. +44*
To speed up implementation of mobile number as a login ID on your site we have pre built screens/flows. You can view and customise these via the screen sets.
These screens can be used both for registration/login and can be linked to from the Profile Management Screen in order to allow a user to manage their phone number.
Once a user has a mobile number added to their account a Customer Services Representative can also update the number on behalf of a user via Identity Access.
Push Notification TFA
SAP Customer Data Cloud has recently launched Push Notification for TFA in conjunction with the release of our new iOS https://developers.gigya.com/display/GD/Swift+SDK and Android mobile SDK's https://developers.gigya.com/display/GD/Android+SDK+v4. For the purposes of this demo we have used the Android demo app.
Previously to this feature being launched offered TFA via SMS, Email and Google Authenticator. This is managed using our Risk Based Authentication Feature https://developers.gigya.com/display/GD/Risk+Based+Authentication
To enable Push Notification TFA you first need to ensure that you have a created a Firebase Push notification App https://firebase.google.com/ you will then need to create an RBA rule at an Account Level, and configure the Push Notification settings.
Once you have configured your Push Notification settings within the Console you will need to configure your mobile app to also use Firebase for Push Notifications https://developers.gigya.com/display/GD/TFA+Library+For+Android+SDK+4.x. Additionally within your Mobile App you will need to provide a mechanism to allow the user to enable TFA.
To enable Push TFA the user will need to log into their app
You will be prompted to approve push TFA
The next time the user authenticates via a desktop/different device they will be prompted on their device nominated for Push TFA to approve the authentication request. Only once approved will the user be logged in.
Conclusion
Please sign up for our next webinar on the 1st of October https://event.on24.com/wcc/r/2072281/7458FD8D54AB32A6BC890A2DE34040F8?partnerref=wiki
Ratul Shah – Senior Product Marketing Managers, SAP Customer Data Cloud
Ian Hametz – Identity Product Manager, SAP Customer Data Cloud
Stephen Purvis – Product Expert, SAP Customer Data Cloud
In this webinar we talked through the Business need and motivation behind our new Innovations and then demonstated how they can be implemented. Here is the link to the recording of this session https://enable.cx.sap.com/media/How+to+use+the+latest+Customer+Data+Cloud+innovationsF+-+Webinars/1_....
This blog post covers the hands-on section of the webinar and walks you through how you can easily layer our new innovations on top of an existing implementation. We used our Webinar demo site from August as a starting point https://blogs.sap.com/?p=853832. This blog post will walk through the following new innovation:
- Account Progression
- Mobile Number as a Login Identifier
- Push Notification TFA
Account Progression
To understand Account Progression you first need to be familiar with our terms lite account and full account. A lite account is that early stage account where a user whom was previously anonymous has provided some basic information to create an account this could be to sign up for a newsletter or an offers email. Typically no password is created at this stage and in some cases you may only request an email address and consent to receive communications. A full account is where a user provides more detailed profile information typically to register for a service to view exclusive content or to purchase a product. The information provided at this stage is required to complete the transaction and can typically include users names, date of births, country of residence etc.
Account progression from lite to full (https://developers.gigya.com/display/GD/Lite+Registration) : When a new full account is created, either by standard registration, or social or federated login, and the email address used for creating that full account already exists for an email account, the newly created full account will share a UID with the existing email account.
To enable lite progression it's quite a simple process you need to enable the feature via the Site Policies:
Once you have enabled the feature then you can update your screen sets to make it easier for those users with lite accounts to progress to full accounts.
Create a new registration screen specifically for those user who have a lite account, to prevent the capturing data that has previously being captured during the lite reg flow.
Lite Progression to Full Account is now enabled on your site. You can test this on your demo site your previously created. Once you have created your account then you can see what the account looks like in Identity Access.
Within Identity Access you will now see within the Account Identities there will be a site account and lite-email account. Additionally any data and consent entered during the lite registration is carried over to the full account.
Mobile Number as a Login ID
The use of a mobile number with Social Media and Messaging Apps such as WhatsApp are becoming more widely used, so much so that in Asia more and more users just have a Mobile number rather than an email address. To cater for this demand our Mobile Number as a Login ID feature was launched.
Mobile Number as a Login ID allows for customers to enter a mobile number and receive a 4 digit pin code to register/login to their account. A user can use their mobile number alongside existing authentication methods such as social and email helping to expand the authentication methods offered to users yet still providing a single account.
To enable Mobile Number as a Login ID you will need to have an account with either Livelink or Twilio https://developers.gigya.com/display/GD/Phone+Number+Login. As a first step you must enter your mobile provider credentials via our Administration Menu.
When configuring your mobile sms provider you can define a white/black list (regex compatible) to determine which numbers can or cannot be used to authenticate with. A great use cases would be to restrict access to only those users whom are using numbers from the UK e.g. +44*
To speed up implementation of mobile number as a login ID on your site we have pre built screens/flows. You can view and customise these via the screen sets.
These screens can be used both for registration/login and can be linked to from the Profile Management Screen in order to allow a user to manage their phone number.
Once a user has a mobile number added to their account a Customer Services Representative can also update the number on behalf of a user via Identity Access.
Push Notification TFA
SAP Customer Data Cloud has recently launched Push Notification for TFA in conjunction with the release of our new iOS https://developers.gigya.com/display/GD/Swift+SDK and Android mobile SDK's https://developers.gigya.com/display/GD/Android+SDK+v4. For the purposes of this demo we have used the Android demo app.
Previously to this feature being launched offered TFA via SMS, Email and Google Authenticator. This is managed using our Risk Based Authentication Feature https://developers.gigya.com/display/GD/Risk+Based+Authentication
To enable Push Notification TFA you first need to ensure that you have a created a Firebase Push notification App https://firebase.google.com/ you will then need to create an RBA rule at an Account Level, and configure the Push Notification settings.
Once you have configured your Push Notification settings within the Console you will need to configure your mobile app to also use Firebase for Push Notifications https://developers.gigya.com/display/GD/TFA+Library+For+Android+SDK+4.x. Additionally within your Mobile App you will need to provide a mechanism to allow the user to enable TFA.
To enable Push TFA the user will need to log into their app
You will be prompted to approve push TFA
The next time the user authenticates via a desktop/different device they will be prompted on their device nominated for Push TFA to approve the authentication request. Only once approved will the user be logged in.
Conclusion
This brings an end to the blog discussing the webinar demo of our new innovations. A key takeway for this session is that all of the new features (with the exception of the Mobile App) can be easily added to your site through configuration changes within the SAP Customer Data Cloud Console. So in turn this means:
- Don't need highly skilled developers to make use of new innovations
- Don't need to have downtime for deployments
- Increase speed to implement and benefit from our new innovations
Please sign up for our next webinar on the 1st of October https://event.on24.com/wcc/r/2072281/7458FD8D54AB32A6BC890A2DE34040F8?partnerref=wiki
- SAP Managed Tags:
