SOLVED
Explaination:
This might have something to do with the "rendering order" of tokens and snippets as the page gets built out. I've done some testing w/ LP stuff in the past to try and load stylesheets via snippet using a different combo of variable and tokens and had a mixed bag of success, but similarly not as elegant as I had hoped for at the end of the day.
This got my curiosity going though and and I setup a test situation where I tried to use a string variable + token to accomplish something similar. I don't know that this is too much different than just going into the editor and choosing a different token, but maybe it'll be some food for thought?
From what I could tell in my testing it seems like the Snippets get rendered first and then the variables and then the tokens, which kind of makes sense b/c if you have tokens inside your snippets, you'd want the HTML of the snippet (including the token) to be in there before the tokens were translated.
.... into the weeds with some troubleshooting and testing:
I first tried using a string variable instead of a token in the defaultSnippetId="" and that didn't work 😕
Next, I setup a string variable on the template to plug in the token I'd want (it says Snippet ID, but that's really more like "Token ID" in this example)
<meta class="mktoString" id="Snippet-ID" mktoName="Snippet ID" default="001"/>
Then for the HTML for the snippet container, I just didn't set a default snippet there and instead used a token which included the string variable ${Snippet-ID} so that I had a handle to call different tokens inside the snippet container.
<div class="mktoSnippet" id="test-Snippet" mktoName="test snippet">
{{my. Snippet ID test - content ${Snippet-ID} }}
</div>
This ends up looking like {{my. Snippet ID test - content 001}} or {{my. Snippet ID test - content 002}} in the Email Editor depending on what you set the value of the string variable to (001 or 002).
To setup the tokens, I just put a text string in there that read:
"This is content of the my Snippet ID - content ______" (001 or 002) so I could tell the difference between the two when they rendered.
To my surprise, this is what showed up in the Email Preview -- the value (contents) of the {{my. Snippet ID - content 002}} token!
Use case:
Now, using the EM editor, you could change the value of the "Snippet ID" sting variable from 001 to 002 to load a new token in there. It's not a snippet but if you had several global tokens (rather than snippets) setup, you could use them in a somewhat similar fashion by updating them on a high-level folder and having them cascade thru all the pages, then using the sting variable in each email to select a token (faux-snippet) to use on that page.
I think I'll still want to play with this a bit to see if populating something inside an actual snippet would work any differently - right now this is really more a use case of "change a token by using a string variable". Maybe at least it helps to show the render order of things for Variables, Tokens and Snippets.
I tried to tokenize the value in the string variable here within the EM editor (002 became {{my. Token ID}}) but it didn't work to have a token nested inside a token - it just output "}}"
Findings:
1. I learned that you can use string variables inside of tokens -- this must mean that variables are rendered before the tokens.
2. I learned that you can use a string variable inside of snippet -- this must mean that the snippets are rendered before the variables.
3. I tried plugging the variable right into the defaultSnippetID="____" and it showed up blank -- this must mean that the editable containers are rendered before the variables AND the tokens are translated (which kinda make sense).
4. Tokens inside of tokens don't work even if they're passed thru a variable first.
In another test, I used the sting variable inside of a snippet and that seemed to work:
String Variable tag
<meta class="mktoString" id="Snippet-ID" mktoName="Snippet ID" default="141"/>
Snippet (Id = 141) HTML
<div>Snippet ID = ${Snippet-ID}</div>
<div>Use a variable to populate snippet ID above</div>
Output
<div>Snippet ID = 141</div>
<div>Use a variable to populate snippet ID above</div>
I'd be interested in reading thru some kind of documentations about the render order of things like variables, editable containers and tokens on a page to get a sense for how to manage the hand-off or pass things like this thru to make them more elegant. Let me know if you end up coming across anything like that on your search or if this might have help lead to some kind of alternative solution that you got to work.
I'm not satisfied that I've made the most sense of this, so I'll probably revisit this and let you know if I'm able to get anything working to actually swap out Snippets in some way that's more elegant.
I tried this every way I could imagine it working and could not get it to work. Default parameter, ID as contents of the div tag, etc. Here's a screengrab of the documentation we're referring to:
I even tried setting the snippet in an email from the template, then saving that email as a template. It converts the snippet into plain old HTML and makes it no longer a snippet.
Justin Cooperman - I really need this ASAP as well. I can train around it temporarily, but I'd prefer to have the solution working as intended.
.png)
- Copyright © 2025 Adobe. All rights reserved.
- Privacy
- Community Guidelines
- Terms of use
- Do not sell my personal information
Adchoices