> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Salesforce Sales Cloud: Version Release Notes
> What's new in the current Invoca for Salesforce Sales Cloud package, how to upgrade, and a summary of major past releases.
The newest version can always be installed from Invoca's AppExchange listing. To check your installed version, go to Setup > Installed Packages and search "Invoca Enterprise."
## Version 5.8 (September 2025): e164 phone formats and EU conversion reporting
Three main enhancements:
* Closed-loop conversion reporting is now supported on the Invoca EU platform — choose your platform region in Invoca Admin > Conversion Reporting settings (default is North America).
* Matching now supports e164 phone number formats (including country codes), in addition to local formats, for both initial matching and matchback.
* The character limit for selecting Lead Statuses and Opportunity Stages to report back to Invoca increased from 255 to 510 characters each.
Install links:
```
Production 5.8: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKk0000004fBX
Sandbox 5.8: http://test.salesforce.com/packaging/installPackage.apexp?p0=04tKk0000004fBX
```
## Upgrading to version 5.8
1. **Screenshot your current Invoca Admin settings first**, especially if upgrading from versions 1.0–5.4 — those settings will need to be reconfigured (5.5+ carries settings over automatically).
2. **Install in your sandbox first** — ideally a full-copy sandbox. Once you upgrade to 5.8, you can't revert to a prior version.
3. **Configure your Invoca Admin settings** — reconfigure fully if coming from 1.0–5.4; otherwise just verify the existing settings carried over. Newer versions can match to more objects (Contacts, Leads, Accounts/Person Accounts, Opportunities, and Cases) than older versions supported — select Leads, Accounts, and Opportunities if you want to maximize closed-loop conversion reporting.
4. **Connect Invoca to your sandbox org** — set up a new Salesforce Sales Cloud connect app tile (keeping your production tile intact) and authorize with your sandbox org.
5. **Complete test calls** and confirm data lands correctly — including a full Lead-to-Opportunity conversion flow if you use closed-loop reporting, and a Case flow if you match to Cases. Filter the Transaction Details report for Post Call Event types to spot data coming from Salesforce.
6. **Install in production** once your sandbox testing looks good, using the Production link above.
7. **Reconfigure your Invoca Admin settings** in production.
8. **Re-authorize the connect app connection** in Invoca — especially important if upgrading from 3.x or earlier. Deactivate the existing integration, then reconnect via "+ New Connect App," choosing Salesforce Sales Cloud.
9. **Monitor** to confirm everything continues flowing, matching, and reporting correctly. If data stops after an upgrade, re-authorizing the connection (as in step 8) usually resolves it.
## Summary of major past releases
| Version | Date | Highlights |
| :---------- | :--------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 5.7 – 5.7.3 | Nov 2024 | Matchback logic now runs on Phone-field updates, not just record creation; conversion reporting now fires on initial match rather than requiring a later status change; added support for automated batch updates to Lead Status/Opportunity Stage; added Picklist-type field mapping; fixed AdWords Matchtype/IVR Duration field bugs |
| 5.6 | June 2024 | Reimagined Invoca Admin UI; added Category, Short Text, and Long Text/URL Marketing Data field slots; added field mapping on matchback and Call Log updates; added enable/disable controls for matchback logic and Tasks per object; added support for batched transactions |
| 5.5 – 5.5.4 | March 2023 | Major matching overhaul: moved from SOQL (Salesforce Object Query Language) to SOSL (Salesforce Object Search Language), which searches all Phone-type fields without requiring an exact match; added matching to Accounts/Person Accounts and Cases; matches to Opportunities via the related Account; removed reliance on custom "stripped phone" fields and their install-time batch processes; expanded custom matching and field mapping to all object types; improved matchback support for North American country codes |
| 4.8 | Feb 2021 | Added Salesforce Shield Encryption compatibility (deterministic encryption required on fields used for matching); replaced the custom TextPhone field with FormattedPhone |
| 4.2 | Aug 2019 | Added control over which Opportunity Stages report Revenue back to Invoca, avoiding inflated revenue across multiple Stage-based Signals for the same call |
| 4.1 – 4.1.1 | 2018–2019 | Added a "skip matching" option for custom matching workflows; brought the Invoca Console to Lightning (via the utility bar); added support for multiple Lead Statuses/Opportunity Stages reporting as Signals, including while a call is still in progress |
| 4.0 | May 2018 | Conversions reported from Salesforce now post to Invoca as Signals (previously "Reported Conversions"), enabling automatic sharing with other Invoca integrations like Google Ads and Facebook; added Custom Data field mapping on Signals |
**Note**
Versions below 5.2 use Salesforce APIs that were retired in the Salesforce Summer '25 release — if you're still on one of those versions, upgrade immediately to avoid disruption.
### A note on Shield Encryption (introduced in 4.8)
If you use Shield Encryption, matching only works correctly with deterministic encryption on fields used for matching, and destroying your stored encryption key will break matching. Object owners can confirm which specific fields support encryption without compromising default matching — check with your Salesforce admin or Invoca Support for the current validated field list for your object types.
## Where to go next