Updates: Web Messaging Performance Enhancements: Content Security Policy &
New Masking Indicator Reporting in Messaging Interaction API
➡️ Exact delivery dates may vary, and brands may therefore not have immediate access to all features on the date of publication. Please contact your LivePerson account team for the exact dates on which you will have access to the features.
🚨The timing and scope of these features or functionalities remain at the sole discretion of LivePerson and are subject to change.
Web Messaging Performance Enhancements
Content Security Policy
Action Required for brands that are utilizing a Content-Security-Policy header on their websites.
LivePerson is making important updates to the web messaging stack, which changes the protocol and domains that the scripts embedded into a brand's website use. Brands that are adding an additional layer of security by using a Content-Security-Policy (CSP) may have to adapt the CSP header to include these new domains.
This knowledge center page has been updated to reflect the latest recommendations.
Why is it changing?
LivePerson is rolling out performance enhancements and is modernizing the frontend stack. This includes loading assets from a geographically distributed content delivery network as well as deprecating JSONP as a protocol to fetch data (such as account configuration).
In addition to that, with the migration to the public cloud, LivePerson updates the domain names of some of the consumer side APIs. These changes may require updates to the CSP, otherwise web messaging and chat conversations can no longer be started.
What action is required?
Please verify if your website is using a CSP header. If not, no action is required. In case you are leveraging a CSP, then please update the header to align with our latest recommendation which can be found on this page in the Knowledge Center. Please ensure that the updated CSP is in place no later than August 15, 2025.
If determined an update is required, the updated CSP can then be verified to ensure it is compliant:
- [Recommended] Opt-in to performance enhancements early to verify that the updated CSP is not blocking resources
- Contact your LivePerson Account Team, or the LivePerson Customer Care team via 24/7 Messaging at LivePerson.com, for assistance with opting-in
- [Optional] Use the "LivePerson Web Messaging Debugger" Chrome/Edge browser extension to uncover potential CSP compliance/compatibility issues
- If you have not yet confirmed with a LivePerson representative or completed the required CSP updates, please submit this form after reviewing this documentation and confirming your readiness.
Our Commitment to Support
LivePerson is dedicated to ensuring a seamless implementation. Following August 15th, LivePerson will begin conducting a multi-week, phased rollout of updates to the web messaging stack.
We will provide comprehensive guidance and support throughout this process. For specific dates that may impact you during this period, please contact your account team.
New Masking Indicator Reporting in Messaging Interaction API
LivePerson are pleased to announce the integration of the " Masking Indicators" feature into the Messaging History API (MIA). This enhancement enables brands to track and analyze profanity, transcripts, and historic masked content across messaging interactions, fostering safer and more compliant communication experiences.
What’s New
Messaging History API (MIA) Enhancements
A new "masking indicator" content section is now available in MIA, enabling visibility into profanity, transcript and historic masking activity across conversations and messages.
New Fields:
- number_of_conversations_with_profanity – Total count of conversations where profanity-only masking was applied.
- number_of_messages_with_profanity – Total number of messages where profanity-only masking occurred.
- profanity_usage_timestamp – Timestamp of when profanity masking was triggered.
Data Levels:
- Agent-Level: Profanity data per agent
- Skill-Level: Profanity data per skill
- Consumer-Level: Profanity data per end-user
JSON:
"maskingIndicators": {
"profanity": true,
"transcript": false,
"historic": false,
"creditcard": false
}
Why It Matters
- Compliance & Moderation: Maintain brand reputation and meet policy standards by tracking where profanity and other masking filters have been enforced.
- Operational Insight: Analyze trends in masking usage across agents, skills, or consumer segments.
- Transparency: Enable data-driven auditing of profanity handling across digital conversations.
Enablement
No configuration is required. The updates are now available to all brands using MIA and Data Transporter.