I do have one more question. Is there any possibility we can get the event.title to show in the Subject Line of an email?
Great! Everything is working. Thank you guys!
If I have a deigned Add to Calendar section in my email for Google, Outlook and IOS. Is there’s a way to change their invite links according to the event the user has signed up for? So right now the email updates the title, when and where but if I have a Add to Calendar section with 3 separate columns saying Google, Outlook and IOS. Is there’s a way to generate their invitation links dynamically?
something like below
You can have additional parameters with the apt ics values (each for google/apple/outlook) for each of the HUG event in the velocity map and use that in the calendar section of the email based on the HUG event type. Assuming you would have your original token with all the data above this token - you can have a token that can display the calendar section and dynamically add the apt ics links based on the HUG event type referencing the respective ics links from the original token. You can also have a separate array locally defined in the velocity token - but IMO having all the info in a single array at one place in your original token wouldn’t hurt.
Thanks!
@freeza ,
Add all the parameters for the event into the keymap (the way you added title).
Then use a link to agical (read all about it here https://blog.teknkl.com/introducing-agical-io-the-smarter-ics-file-generator/). Essentially this is an extension of the logic used to create the zoom link.
I'm pretty certain you don't need a specific add to iOS option. You just need GCAL (google) and ICS (everything else).
Cheers
Jo
If I have to send Reminder Emails for all of these events. Do I have to create Separate Smart Campaigns or else can I do everything in 1 Smart Campaign?
Since Each event is in different date.
There are a few ways to skin that cat.
One would be to have a single smart campaign with all registrants in the audience, and wait steps to send each email on the right date (with a constraint to make sure the person was in that event).
The other is to set up <x> campaigns, one for each event, that is scheduled to fire <y> days before the event in question.
I'd probably go for the latter. It's much clearer what is going on.