Solved! Go to Solution.
You can just preview an email with the ICS token added to get the non-unique link for use. When viewing the preview you simply hover over the link to see the link which also allows you to "Copy Link Address". So it's annoying, but a viable workaround. Looks like Marketo generates a unique ID for the ICS token which the URL path references in addition to the value added to the "Title" of the token.
Example
https://subdomain.domain.com/rs/XXX-XXX-XXX/#####/[tokentitle].ics
Where
- XXX-XXX-XXX represents your instances Munchkin ID
- ##### represents the tokens unique ID
I assumed the title was irrelevant but it is required to access the ics file (likely as an extra security measure so people with one event invite can't just guess ID's to see every event).
Honestly, I've been debating switching to AddThisEvent for my Save the Dates.
You can track clicks to the link and it makes it mind-numbingly easy to not only apply the link to whatever (an image), but also allows the end user to add the calendar event to their desired software. I, for one, am tired of vendors sending me .ics files and needing to upload them individually to my company's Google calendar.
The only downside is you can't add tokens to the calendar invite. Depending on the type of event you're hosting, this may or may not be a big deal (it isn't always for me).
Is there any hope that this will get fixed?
You can just preview an email with the ICS token added to get the non-unique link for use. When viewing the preview you simply hover over the link to see the link which also allows you to "Copy Link Address". So it's annoying, but a viable workaround. Looks like Marketo generates a unique ID for the ICS token which the URL path references in addition to the value added to the "Title" of the token.
Example
https://subdomain.domain.com/rs/XXX-XXX-XXX/#####/[tokentitle].ics
Where
- XXX-XXX-XXX represents your instances Munchkin ID
- ##### represents the tokens unique ID
I assumed the title was irrelevant but it is required to access the ics file (likely as an extra security measure so people with one event invite can't just guess ID's to see every event).
This is the way that I would do it. You can even store the calendar link in a token (no https://) if you want to easily add it to multiple emails within an event program, or use the link in the text version of your email.
Nice one, Keith!
Haha Dan Stevens I was just reading this thinking that I use that same method