Ok, I think we're getting there. I definitely feel solid about the hidden form field possibilities and restrictions.
For the trigger campaign option, I have a couple more questions (thank you so much for all your time by the way!!!):
1. Clarification: If I schedule a trigger campaign, I can build just one for all of my programs, correct?
2. If I build a trigger campaign, do I need to include the hidden field on each form? (I understand that there is a step I don't need to do if I do the trigger campaign, but I'm not clear if that means that I simply don't have to set the default value or if I can leave the field off of the form entirely.)
3. I haven't worked with trigger tokens before, so this may be a really dumb question: Is {{trigger.name}} always in reference to a form title?
4. Pending the answer to #3, do I need to set anything on the trigger token to specify that I want the form title?
You're welcome!
1. Yes, one campaign, once activated, would work for any form fill out in your instance, no matter where the form lives, in Design Studio or an program.
2 No, you wouldn't need the custom field on your forms because the trigger campaign would capture the name of the form and populate the field after fill out.
3. The {{trigger.name}} token will populate with whatever the name of the asset is that triggered the campaign. If it's a Filled Out Form trigger, then yes, it will be the name of the form. If you're using that token in a campaign with a Visited Web Page trigger though, then the token would populate with the name of the webpage that was visited. The token takes its value from the trigger, and it will always be the name of the asset (i.e. form name, website, etc)