Optional Suffixing for Custom Variables in Smartlead.ai Integration

I’d like to provide some feedback regarding the Smartlead.ai integration, specifically around the handling of custom variables. Unfortunately, this is currently the main blocker preventing us from using the integration.

We understand and fully support the need for certain system-generated variables (like videoUrl or thumbnailEmbed) to include a suffix for namespacing or conflict avoidance. However, for user-defined custom variables, this behavior creates integration issues on our end.

For example:

• We use a salutation variable that is intentionally standardized across campaigns. It’s okay if it gets overridden. Having that prefixed means that we need to update all emails when duplicating the campagin to change the variable name.

• We also use a crm_lead_id variable that must retain a consistent name without a suffix, as it’s required for seamless syncing with our CRM.
  

The current behavior of automatically suffixing all variables breaks this compatibility and prevents us from using the Smartlead integration effectively.

Another small annoyance is when having multiple campaigns and each campaign has all custom variables suffixed, a CSV export will have a lot of unnecessary columns for a lead which all show the same data.

Request:

We’d love to see an option that allows users to decide whether or not to apply suffixes to non-system (i.e., non-Pitchlane-specific) variables. E.g. a separate selection with variables which won’t get suffixed. This would maintain the protection for internal variables, while giving users the flexibility needed for smooth integration with external systems like CRMs.

We’re excited about the potential of using Smartlead.ai with Pitchlane and would greatly appreciate if this change could be considered. It would make a big difference for us and likely for others with similar integration needs.