Skip to main content

On behalf of a customer, 

     When creating an Email Template, we can add a Button, where we can then add a Link Token. This allows for link tokenization of the button in Journey Orchestrator, so that recipients will be able to click the button and have a unique link based on condition.

     However, when this same Email Template is used in a Playbook Task, we are not allowed to use this token within the Button. This is not a supported token type with Email Assist 2.0, as stated in the documentation. (Send Emails from Cockpit - Gainsight Inc.)

Email Template:

Email Task:

     From an Admin perspective, it would be highly desirable for this token type to be supported in Email Assist 2.0. Additionally, could the Email Templates documentation (Create Journey Orchestrator Email Templates - Gainsight Inc.) please be updated to more clearly reflect where this functionality can, or cannot, be used?

+1 the need for this.

We didn’t realise there was a limitation until we have gone to send an email, because why would there be?

I would really like to know the reasoning behind this limitation.

Reply


Terms & ConditionsCookie settings