Unlike personalisation where you can use any code, the S3/Webex connector uses the Webex scripting language.
The segmentation features in Taxi for Email allow modules within an email to be aimed at particular audiences from within our email editor. Filtering to see what recipients in different groups will receive, can be performed in real-time while building the email.
Segment sets and single segments are defined in the segmentation section of your Taxi account. These enable you to set up rules to control which content is sent to which groups of people in your data. They are then applied to any of the modules in your EDS to give you complete control of the specific content that’s sent to your customers.
This segmentation is mapped by the connector to handlebar conditional code snippets, and this code is run when the email is sent. This ensures each recipient gets the content selected for them.
Once segments are defined it is possible to use them in the Taxi editor and to preview content for each segment.
Finally, to be able to export code through the connector, the code for segments must be added. This code is set per connector. This means you can use different conditions or variable names between environments, and thus you can work with different data structures and formats if needed.
Code for segments is entered through the segmentation settings.
When you export from Taxi, the if statements will look like this:
#if_10 $(gender) == 'female' #
#elseif_10 $(gender) == 'male' #
Segmentation in Webex needs the number in the if statement for it to work.
When you have multiple if statements in an email they need to have different numbers and each one needs to be higher than the last.
Taxi automatically adds these in when exporting. For example, if there was an if statement after the one above it would be like this:
#if_11 $(gender) == 'female' #
#elseif_11 $(gender) == 'male' #