Hi Jenn DiMaria,
Local tokens will still work in global emails, so long as the email is sent by a smart campaign that is local to the program. You get the best of both worlds this way.
The structure I generally recommend is
- Global form in Design Studio
- Global fulfillment emails (e.g., "Thanks for downloading" and alerts etc. ) in Design Studio
- Individual program to represent the asset being downloaded for attribution purposes
- Local landing page
- Local smart campaign triggering off global form + local landing page constraint sending the emails
This keeps common elements centralized and easy to update while allowing you to take advantage of tokenization at the local level.
Justin Norris | Perkuto
Hey Jenn - we provide similar alerts today. We actually keep a single alert email centrally stored in an operational email folder in DS; and use a central series of "campaign response" trigger campaigns (based on the global campaign that the content aligns to) - rather than keep these in the individual programs:
All of our programs with gated content request a campaign in one of these four routing campaigns:
And then the alert is sent to the appropriate country marketing lead:
Here's the framework of the alert:
And a sample alert (there's no link to the PDF file, but there is a link to the landing page where the PDF file was downloaded):
In case anyone's interested, we ended up pre-pending the PDF's URL with a redirect landing page (thanks to Courtney Grimes for the head's up about this). What that does it record the PDF as a webpage visit, allowing you to trigger off "Visits Web Page" and record the PDF's URL in a temp field using trigger tokens. We're still perfecting it for our purposes, but it's working really well, and we only have to deal with one global alert email.