Email Global variables with dynamic segmentation

[Disha_Goyal6]

Hi @SanfordWhiteman,  I’m currently working with UTM parameters and assigning values using global variables in email editor 2.0. However, the client reported an issue where this approach doesn’t work when dynamic content (segmentation) is used. After doing some research and testing, I found that global variables are indeed not compatible with dynamic content.

Could you please suggest a workaround or an alternative approach to address this issue?

[SanfordWhiteman · Accepted solution]

To use a global ${mktoVariable} in Dynamic Content:

1. first output the ${mktoVariable} in-between 2 Velocity {{my.tokens}} with
   #define($mktoVariable_VTL)
   and
   #end
   respectively
2. create a 3rd Velocity {{my.token}} that simply outputs
   ${mktoVariable_VTL}
3. use that 3rd Velocity token in Dynamic Content

This is a very advanced use of Velocity in Marketo. Be sure you understand how Velocity scope & order-of-operations work before supporting it in a production environment.

[Disha_Goyal6]

Hi @SanfordWhiteman, how we will ge the value of modular email global variables in velocity token?

[SanfordWhiteman]

What do you mean by “modular email global”? A global variable and a module-scoped variable are different.

[Disha_Goyal6]

Hi @SanfordWhiteman, I am asking about these values that defined in global variable of email editr 2.0. 

These variables are not working with segmentation. So I did research but it is not supporting. I need a workaround if there is any.

[SanfordWhiteman]

But I described how to do that above?

[Disha_Goyal6]

Hi @SanfordWhiteman, I was applying the same method and added all the tokens in email. Iit is showing the variable as it is. No value is coming.

[SanfordWhiteman]

Would need a detailed set of screenshots showing what you attempted.

[Disha_Goyal6]

Hi @SanfordWhiteman, here is the screenshot of the velocity script tokens:

Added like this in Editor

Showing this output

I am not so proficient in Velocity script and I took help from chatgpt to implement the same.

[SanfordWhiteman]

---

I am not so proficient in Velocity script and I took help from chatgpt to implement the same.

---

Well, that’s not going to work. ChatGPT is giving you broken code (as it usually does for Velocity tokens, not to mention infinite other areas). That’s why I mentioned you really have to understand Velocity to support this setup.

Again, the requirement is to output the ${mktoVariable} in-between Velocity {{my.tokens}}. It doesn’t go inside any Velocity token. If this still isn’t making sense it’s likely that you shouldn’t be putting this into prod.