September 2025 - Send2CRM Essentials v1.18
In this release: More control for organizations with many websites.
Summary
Sep 12, 2025 The v1.18 release of Send2CRM Essentials introduces powerful website-specific rules that enable tailored form mappings, customer segmentation, and automation sequences for multi-site organizations.
New form origin mapping capabilities allow the tracking of submission sources directly in Salesforce, while enhanced debugging tools provide website-specific troubleshooting for non-administrator users.
The release also strengthens email security compliance and resolves long URL handling issues.
Once upgraded, if you are also using the analytics and personalization capabilities of Send2CRM, please upgrade to September 2025 - Send2CRM Analytics v1.20.
To continue sending emails from Salesforce when an error occurs, confirm that there is a verified organization-wide email address that the integration user profile is allowed to use.
New Features
Added website-specific rules that let you create different form mappings, customer segmentation, and automation sequences for each of your websites. To implement website-specific rules:
For additional information, refer to Automation Conditions. |
Added ability to map Form Origin and Identifiers, to allow storing the source of form submissions. To store form source information:
For additional information, refer to Field Mappings. |
Improvements to existing features
Improved Website Debug functionality to offer website-specific debugging, and to operate for users without system administrator permissions. |
Improved the Mapping Wizard to display all mappings and their execution sequence for each form, helping technical users avoid duplicate records and understand data flow dependencies. See Mapping Object. |
Strengthened email sending mechanism to align with Salesforce security requirements. Email error notifications are only sent using a verified company email addresses that the integration user's profile is allowed to use. |
Bug fixes
Fixed an issue where pages with URLs over 255 characters would prevent page view data from syncing to Salesforce, causing gaps in customer journey tracking. |
Fixed an issue where errors saving visitor and related objects in Salesforce do not appear in debug logs, making it difficult to troubleshoot problems with visitor updates. |