Overview
Talkative’s chat widget loads dynamically and serves versioned assets from our CDN. When Osano is configured to block scripts that are not explicitly declared, this can prevent the widget from loading correctly.
This guide explains:
- Why multiple script versions appear
- Why version numbers change
- What must be allow-listed in Osano
- What to watch out for when maintaining compliance
How the Talkative Widget Loads
When you install Talkative, you add a single import script to your page.
That initial script:
- Sends the current page URL as a query parameter.
- Retrieves the correct configuration for that page.
- Dynamically loads the appropriate runtime assets depending on:
- Widget configuration
- Engagement phase
- Enabled features (chat, engage, active monitoring, etc.)
Example assets loaded during a session:
https://talkative-cdn.com/ecsv2/0.52.2/talkative-core.js
https://talkative-cdn.com/ecsv2/0.52.2/talkative-active.js
https://talkative-cdn.com/ecsv2/0.52.2/talkative-chat.js
https://talkative-cdn.com/ecsv2/0.52.2/talkative-wrap.js
https://talkative-cdn.com/ecsv2/0.53.2/talkative-engage.jsAll of these are classified as ESSENTIAL scripts.
You may see scripts not mentioned above - the scripts which load depend on your active toolset and capabilities - talkative may introduce new modules as versions change.
Why Version Numbers Change
You may notice versions such as:
0.43.8
0.43.9
0.52.0
0.52.1
0.52.2
0.53.2
These version numbers are intentional and central to our deployment model.
We automatically:
- Patch for bug fixes
- Patch for security updates
- Deploy performance improvements
- Drop support for outdated minor versions when required
This ensures customers receive fixes immediately without needing to manually update embed code.
Because the version number forms part of the script URL, each release produces a new asset path.
If Osano is configured to allow only specific versioned URLs, it will block new releases and the widget will fail to load.
Why This Causes Issues with Osano
Osano requires scripts to be categorised and, in many cases, explicitly defined.
However:
- Talkative loads scripts dynamically.
- Script URLs contain version numbers.
- Versions change automatically.
- Osano does not support wildcard matching in some configurations.
This can cause Osano to treat new versions as unapproved scripts, resulting in:
- The widget not appearing
- Partial loads (core loads, chat doesn’t)
- Engagement features failing
- Console errors due to blocked assets
Required Configuration in Osano
1. Classify Talkative as Essential
All Talkative CDN assets must be marked as:
Essential / Strictly Necessary
The widget provides live communication functionality and does not rely on marketing or analytics categorisation.
2. Allow by Domain, Not by Version
You must configure Osano to allow scripts by domain, not by full versioned URL.
Allow:
https://talkative-cdn.comDo not allow individual paths such as:
https://talkative-cdn.com/ecsv2/0.52.1/talkative-core.jsThis will break on the next release.
3. Do Not Pin to Specific Versions
Avoid:
- Hard-coding version numbers
- Approving only currently visible assets
- Requiring manual review for every new version
Our release model is designed for continuous delivery of fixes. Blocking new versions can result in:
- Security exposure
- Inconsistent behaviour
- Loss of support for deprecated versions
What to Expect Over Time
You should expect:
- Patch version increments frequently (e.g., 0.52.1 → 0.52.2)
- Minor version increments occasionally (e.g., 0.52.x → 0.53.x)
- Older minor versions eventually being removed from CDN support
This is normal and by design.
No action should be required if Osano is correctly configured to allow the domain.
Troubleshooting Checklist
If the widget stops loading:
- Open browser DevTools.
- Check the Network tab for blocked requests to:
talkative-cdn.com- Check the Console for consent-related blocking errors.
- Confirm in Osano:
- Talkative is marked Essential
- The domain is allow-listed
- No version-specific rules exist
If assets from talkative-cdn.com are being blocked due to version changes, Osano configuration needs updating.
Why Versioning Is Critical
Our versioned asset model ensures:
- Immediate delivery of security fixes
- Rapid bug resolution
- Stable rollouts
- Backward compatibility management
- Controlled deprecation of outdated builds
Removing version numbers or freezing versions would prevent us from maintaining security and reliability standards.
For this reason, versioned URLs are not optional and must not be constrained in consent tooling.
Summary
To ensure continued compliance and uninterrupted service:
- Mark Talkative scripts as Essential
- Allow by domain
- Do not restrict by version number
- Do not require re-approval for each release
If configured correctly, Osano will remain compliant while allowing Talkative to deliver ongoing security and quality improvements without disruption.
If you need assistance validating your configuration, please contact Talkative Support and include screenshots of your Osano script configuration settings.