Here are some key Leadspace releases and highlights for Q2 of 2025. If you have any questions or feedback on any of this features, please contact Leadspace Support.
New Regex Value Mapping Functionality
Leadspace has added Regex functionality to the list of operators we can use to build out customized value mapping for our customers. Regex allows us to prepend or append a set of characters to an output value.
For example. Leadspace scrubs https:// from all of the website and domain data we output for person and company enrichment. However, your system may require the site protocol to be prepended to your URLs, so we can add this via a Regex mapping for your company:
Before: www.leadspace.com
After: https://www.leadspace.com
Please refer to the Value Mapping article for more information.
Studio Suppression Validation
Leadspace Studio employs a file size limit of 10Mb for suppression files used for Person Discovery, Company Discovery, and Lookalike segments. Previously, this limit only applied when using a file upload during the suppression process. We have now added validation to ensure that existing segments including ingested segments adhere to this size limitation.
Before: When creating Discovery or Lookalike segments, users could choose existing segments or ingested segments that were larger than 10Mb to use for suppression. This could cause segments to fail altogether or complete as 'Partial Success'.
After: All methods of suppression; file upload and using existing segments now adhere to the 10Mb limit. This ensures that segments process fully and efficiently.
Improved Error Handling
This is an internal, stability improvement. We identified a small percentage of 'Invalid Input' records that were returning error code 500 'Internal Error' instead of the expected error code 400 'Invalid Response'. Now, all Invalid Input errors should return as 400 as expected.
For more information about proper inputs for successful enrichment, please refer to Leadspace Enrichment Requirements.
New 'LS Status Reason' field for CRM and MAP integrations
We added a new field called 'LS Status Reason' for customers that use our Leadspace for Salesforce, Hubspot, Eloqua, and/or Marketo integrations.
This field is best used in conjunction with the 'LS Status' field which is a required field in these systems; specifically when LS Status = Invalid Input, meaning that the input data you sent for enrichment is either incomplete, missing, or includes double-byte characters. The LS Status Reason field will provide a description of why the record was returned 'Invalid Input' so your teams can review and address accordingly.
For example, you may see that a segment of records was returned as 'Invalid Input' because the LS Status Reason returned the message 'At least one double-byte character in the input'. You could then segment these records out using this status and either remove them from your system, or use a translation service to translate the data then send back to Leadspace.
Updated Documentation on this feature will be release soon!
Original Input Email Output on Invalid Input Response
To add to the LS Status Reason field that can help customers decide how to treat Invalid Input records, we have also updated the response for records that return Invalid Input. For lead and contact enrichments, we have added the Original Input Email address to the response to give insight into which record returned invalid.
Before: Invalid Input would return error code 400/1200 (depending on system) and would return no data other than the response status.
After: For person enrichments, Invalid Input now returns the Original Input Email you sent to us in the response. This can be especially beneficial for customers using Eloqua, Marketo, or Hubspot because your system or Custom Data Objects (CDOs) may require email address to write to the CDO.