Hi all,
Our team uses snippets with personalization tokens quite a bit in the quotes that they build. In the legacy quote builder, the personalization tokens in the snippets would display the actual property data making it possible to for the rep to see and edit the data as desired before publishing or previewing the quote.
In the new quote builder, when we use snippets with personalization tokens the tokens do not display the data but just the name of the token property. This means that in order to see the token data, we have to look at it in quote preview. Is there a way to make this work as in the legacy tool or plans to fix this?
Thank you,
Jenny
1 Accepted solution
Hey @Jenny26!
Unfortunately I believe the new quote builder does not currently resolve personalization tokens inside snippets while editing. Tokens only render in preview or after publishing. There’s no configuration to change this today, but using preview, pre-populating properties, and quote-level properties are the best available workarounds.
If you need more details about workarounds let me know!
ZUID.
Goirkekanaaldijk 12
5046 AT Tilburg
Nederland
Hey @Jenny26!
Unfortunately I believe the new quote builder does not currently resolve personalization tokens inside snippets while editing. Tokens only render in preview or after publishing. There’s no configuration to change this today, but using preview, pre-populating properties, and quote-level properties are the best available workarounds.
If you need more details about workarounds let me know!
ZUID.
Goirkekanaaldijk 12
5046 AT Tilburg
Nederland
Hi @Jenny26
Thanks for calling this out — I can see how losing in-editor token resolution makes quote building a lot harder for reps.
I’d like to invite a few Community members who are subject matter experts in the new Quote builder / Commerce Hub and snippet behavior to join this conversation.
@karstenkoehler @trevordjones @Lucila-Andimol — hope you’re all having a great week! Have you seen this change where snippets with personalization tokens no longer render the actual property values in the new quote editor (only the token name), and is there any supported way to restore the legacy behavior? Also curious if this is a known limitation/bug with any roadmap notes.
Any insight would be greatly appreciated.
Best,
Victor
|
Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth. Learn More |
