01. Configure a Microsite Workflow

Build and Configure a Microsite

Intermediate

The Inbound Microsite is a powerful way to interact with your Target Audience. A microsite is comprised of one or more web pages (each of which can display content) and capture data from your contacts.

Prerequisites:

Before getting started, you should have completed the following task:

Domain Setup How?

Instructions:

Overview

About Microsite Pages: There are three types of Microsite page types: Blank, Login, and Add Contact. We'll describe each in a bit more detail.

1. Blank Page

• This page type can hold HTML content, including a form. Use this page type whenever you want to display content, and/or capture information from your Contacts.

2. Login Page

• This page is used to secure a microsite when personalized URLs are used. If any pages within your microsite are configured to require a login (an option in Settings), this page will be displayed. Any form fields on the page will be matched against the values that exist for the Contact in the database. If all the field values match what's in the database, the Contact will be allowed to move to the next connected page.

3. Add Contact Page

• When form fields are added to this page, the values provided by a Contact are used to add a new Contact to the database. A common use for this page type is in a "Send to Friend" scenario, where you want to enable a Contact to add their friend(s) to the database. This page type can also be used for data entry purposes, where you want to enable data entry for new contacts.

4. About Microsite Forms

• If you want to include a form on your Microsite pages, place an opening form tag before your form fields, and close your form with a closing form tag.
• Now, let's say you have an input field. Any field name that matches the name of any existing Contact Field will be updated. In this example, since name=firstname, and ##firstname## is a standard Contact Field, the Contact's first name will be updated.
• Any non-matching field names are stored as "Form Field Responses" and available for use throughout your Program. You can access these variables at any time by clicking on the "Variables" button, and selecting the "FormFieldResponse" variable on the right.

Use external URL-based content

Build URL-based Content

Overview Link HTML Pages to an External Document

HTML that is retrieved from a page hosted outside of MindFire Studio can be used in microsite pages, emails, and other apps. This gives an. extra flexibility in hosting and maintaining HTML pages for their campaigns.

Requirements:

• Remote content must be accessible through a web URL
• The external page must NOT contain any relative paths in the HTML
• Any changes to a form on an external page must be published in the Studio for validation - otherwise, new form data will not be recorded in the database

Instructions:

Overview

• Create an element or microsite page as usual
• In the HTML tab, instead of inserting the page's HTML, select "URL" and enter the URL of the page you want to use

• Content for the page is accessed/imported when the Scheduled Event executes - for example, if an email is scheduled to be sent a week from now, any changes to the external page between now and next week will appear in the email when it is sent

Configure a Microsite Workflow

Here's how you can configure your Microsite workflow so that a Guest and Personalized URL see different content:

1.  Start by entering your Inbound Workflow

2. Add a blank page (I will refer to this page as "Handoff")

• This page will act as a blind handoff page which you will set up later

3. Add 2 more pages

• One being your PURL, one your GURL
• Connect both of these to Handoff so that Handoff is now the parent page with the other 2 pages branching off of it into their own workflows
• You can version the content of these pages at this time if you like

4. Open the Handoff page

• In the Settings tab, Select "Show this page first" and "Do not display this page; only run page Flow conditions"
• In the Flow tab, you should see your 2 connected pages
  Set one of the pages to be the default page seen - in this case, use the GURL page as the default
• Select your PURL page
• In the Standard Filter below, Add a rule
  - Select "purl" in the Field column
  - Select "NotEqual" as the Operator
  - Leave the Value field blank
  - This rule means that if the purl field is not empty, it will show us this page instead of the default GURL page

5. Now, depending on if someone types a PURL or a GURL, they should see their respective workflows.