Salesforce will be rolling out an update to how they process Nested Variables within Subject Lines which has meant we’ve had to make some updates to the way our Marketing Cloud connector handles these on export.
You can read more about the changes Salesforce are making here.
There are three new settings under the SFMC Connector within Taxi, “Always insert the subject line as AmpScript to be evaluated”, “Subject line evaluation function” and “Allow concatenation of variables in subject line”
Always insert the subject line as AmpScript to be evaluated
If set to yes (default option) this toggles whether Taxi will set the Subject Line in an Ampscript variable at the bottom of your HTML called @Subjectline which will be pulled into the Subject Line Field in Salesforce.
If set to no, Taxi will pass the Subject Line to Salesforce as a string where possible*. This may work for the time being, but the update that Salesforce is making will cause issues with this method if you are using personalisation in your Subject Line like in the below example.
*Please note that Taxi will always set your Subject Line as a variable when using Segmentation.
Subject Line evaluation function
This option allows you to choose between using the v() or TreatAsContent() function in Salesforce when the Subject line is set as a variable.
If you opt to use the v() function, you will need to allow concatenation of variables in the subject line once Salesforce’s update goes live.
Please read more about the changes Salesforce are making here to understand which function works best for you.
Allow concatenation of variables in subject line
This option lets you choose whether to use the concat function in Salesforce when the Subject Line is set as a variable and personalization is being used.