Known issues and limitations in Unified Profiles in Flex (Public Beta)
Public Beta
Unified Profiles in Flex is currently available as a limited Public Beta product and the information contained in this document is subject to change. This means that some features are not yet implemented and others may be changed before the product is declared as Generally Available. Public Beta products are not covered by a Twilio SLA.
Not a HIPAA Eligible Service or PCI Compliant
Unified Profiles in Flex is not a HIPAA Eligible Service or PCI compliant and should not be used in Flex or Segment workflows that are subject to HIPAA or PCI.
-
If your Segment data uses a phone number format other than E.164, work with your Twilio account team to define conversion rules from E.164. Phone numbers in Flex use E.164 format, so to perform a successful search, you must convert phone numbers from E.164 to the formats used by your data in Segment or have your data sources transform phone numbers in E.164 format when sending data to Segment. Typically, Segment uses the same phone number format as your CRM or data warehouse.
-
For all Flex UI versions prior to 2.8.0,
customer header and profile search
settings are read-only.
-
In the
customer details UI component
, when you create a recent activity group, spaces are not allowed in the
Group name
field. Also note that the
Group name
that you add in Console doesn't match the recent activity widget name that's displayed in Flex UI.
-
Your Flex source is an essential part of your Unified Profiles workspace and is automatically connected during setup. You should not delete or rename this source. If your Flex source gets deleted, you'll need to
use these steps
to reconnect it in your Segment workspace.
-
To display customer highlights and enable automatic customer search in Flex UI versions prior to 2.8.0, you must add the
Set up the Search for a Profile widget
to your Studio Flows for the channels that you use with Unified Profiles data.
This section contains common sync errors that might occur, along with some recommended steps you can take to troubleshoot.
If you're using Salesforce, you can check the sync status for any errors that might have occurred during the sync.
-
Navigate to
Connections
>
Sources
, and select your Salesforce source.
-
You'll see sync history in the
Overview
tab.
-
Select the most recent failed sync.
-
On the side panel, click
Errors
to see more detail.
One common error you might encounter here is related to reauthorizing your connection due to invalid or expired credentials.
To reauthorize your connection:
-
From your Salesforce source, navigate to
Settings
>
Connections
.
-
Click
Reauthorize
to update your credentials.
Warning
Segment syncs with Salesforce immediately after you connect it to your Unified Profiles workspace. This initial sync can take up to 72 hours. After Segment completes the initial sync with Salesforce, Segment initiates a sync with Salesforce every three hours.
If you're using a data warehouse as a source, use the following steps to view sync status and errors:
-
In your Segment workspace, navigate to
Connections
>
Sources
and select your data warehouse.
-
From the
Models
tab, select your model.
-
Locate the Mappings section, and select your mapping.
-
This opens a side panel where you'll see sync history and status.
-
Select a sync to view sync details, status, and results. If a sync has failed, you can view why it failed along with any recommended next steps in the error message.
Warning
Note that Segment's initial sync with your data warehouse can take up to 24 hours to complete.
Use the Profile explorer to view all user data, including event history, traits, and identifiers. To view your Profile explorer, navigate to Unify > Profile explorer in your Segment workspace.
If you don't see data in your Profile explorer, here are a few things to keep in mind:
-
Once you've connected and enabled your source, it will take several minutes before you start seeing the profiles appear in the Profile explorer.
-
If you're using a web or mobile source, check the debugger to make sure data is flowing from your sources.
To check your debugger:
-
Click
Connections
>
Sources
.
-
Find and select your source.
-
Click
Debugger
, and confirm events are flowing through your source.