This content has been marked as final. Show 2 replies
If these are all in the Design Studio, then this isn't following a basic best practice of keeping the landing page local to the program that uses is. I would suggest (at a minimum), moving these landing pages into their appropriate programs in Marketing Activities. For example, a registration page and confirmation page for Webinar A would be kept in a folder in the Webinar A program that tracks registrants, attendees, no-shows, etc.
The design studio should basically be where example landing pages live, which are then cloned into individual programs. This approach helps keep the system more organized.
To add to Jackie's comments, by keeping the landing pages in their respective programs, you can utilize tokens which will auto-populate the information that you're referring to in the landing and confirmation pages. You can also use a hidden field on forms with a string attached to the URL if, for example, you currently have two different URLs that point to identical pages and you just need to know where they came from.1 of 1 people found this helpful
We have our template landing pages in the design studio, but in the Marketing Activities, we also have template programs (standard programs, we've just labeled them as templates so that we know they are content-free) which contain a landing page, thank you page, flow campaigns, progression campaigns, the tokens with a descriptor of how they must be filled out, etc. To create a new event, we just clone the template event, update the tokens and anything else specific to the event, and then we're set. Much faster, more efficient, and less chance for error in my opinion!