Velocity script to vary the From Address based on segmentation

[Patrick_Vincler]

Hi everyone,

I've got a beans and bacon question for this amazing community here. The beans - segmentation. The bacon - Velocity scripting.

What I'm trying to do:

Use a token in the From Address field, to vary our sender email address. Do this by condition of segmentation that is referenced in the script token.

My testing methodology:

Purely by sending an email though the campaign. No test emails sends or previews.

What I've covered already:

Have ticked the check box in right hand panel for the variable. (Segmentation_Clubs_1003)

My Code:

#if($lead.Segmentation_Clubs_1003 == "Client1")
    info@client1.com
#elseif($lead.Segmentation_Clubs_1003 == "Client2")
    info@client2.com
#elseif($lead.Segmentation_Clubs_1003 == "Client3")
    info@client3.com
#elseif($lead.Segmentation_Clubs_1003 == "Client4")
    info@client4.com
#elseif($lead.Segmentation_Clubs_1003 == "Client5")
    info@clent5.com
#elseif($lead.Segmentation_Clubs_1003 == "Client6")
    info@client6.com
#elseif($lead.Segmentation_Clubs_1003 == "Clent7")
    info@client7.com
#else
    info@standard.com
#end

Results:

Email delivers but only displays the default from address (info@standard.com)

Any insight is much appreciated! Thank you!

[Jay_Jiang]

Any reason why you wouldn't just use the built in Marketo dynamic content to change the email's from address?

[SanfordWhiteman]

One reason is that you have to redo the dynamic content for every email, but the Velocity token can be shared by all email assets.

[Patrick_Vincler]

That's correct. We need to add new values to this from time-to-time, and the solution will be applied to hundreds of active and new emails. A single scripting token would only need to be updated, rather than hundreds of emails each time.

[SanfordWhiteman · Accepted solution]

Do it the collection-first way, it's both clearer and shorter:

#set( $senderByClub = {
  "Client1" : "info@client1.com",
  "Client2" : "info@client2.com",
  "Client3" : "info@client3.com",
  "Client4" : "info@client4.com"
} )
#set( $defaultSender = "info@standard.com" )
${display.alt($senderByClub[$lead.Segmentation_Clubs_1003],$defaultSender)}

The way you're doing it isn't wrong per se (although the use of == can get you into trouble and I recommend .equals() instead). But use the code above and see if it still fails.

Also, pls highlight code using the Advanced Editor:

[Patrick_Vincler]

I'm getting a soft bounce when using this method.

[SanfordWhiteman]

That's tested code (with a Seg from one of my instances) so that's surprising.

Output just the Segment value and see what happens.

[Patrick_Vincler]

I removed the default values, and the output is the actual last line of code: $(display.alt($senderByClub[$lead.Segmentation_Clubs1003])}

With the default values, is its ${display.alt($senderByClub[$lead.Segmentation_Clubs_1003],$defaultSender)}

The code doesn't appear to be processing. Hmmm

[SanfordWhiteman]

Like I said, show the output of the segment value only.

Showing VTL code doesn't mean it isn't processing. The raw code is also the expected output on a null value without the silencing (!) operator.

[Patrick_Vincler]

I was finally able to get success with the following iteration. How 'equals' was notated seems to have been the key to solving the issue. Thanks Sanford Whiteman​ for the tips! Much appreciated.

#if($lead.Segmentation_Clubs_1003.equals("Client1"))
    info@client1.com
#elseif($lead.Segmentation_Clubs_1003.equals("Client2"))
        info@client2.com
#elseif($lead.Segmentation_Clubs_1003.equals("Client3"))
      info@client3.com
#else
    info@standard.com
#end

[SanfordWhiteman]

Good to hear, Patrick. == in VTL is much stranger than people realize.