Custom survey footers

Surveys footers have default content and appearance. In v7 designs, the footer includes the Powered by Medallia logo, copyright declaration and renders properly on light and dark backgrounds.

Default footer for v7 designs.

The most common customization activity is to change the links in the footer. The default links are:

Link textLink
Survey Support

https://surveysupport.medallia.com/

Other Contact Infohttps://www.medallia.com/contact
Privacy Policyhttps://www.medallia.com/privacy

Custom footers are linked to the Unit group of the Unit associated with the survey. This allows different Unit groups to have different footers. This procedure is the same whether you are customizing the footer for all Unit groups, or creating custom footers for specific Unit groups.

Before defining custom footers, first create a special Data field named customfooter:
  1. Identify or create an AltSet with these characteristics:
    • Content Kind — Translatable.
    • Form Kind — Short text.
  2. Add a Data field with customfooter as both the Name and Keyname. When multiple companies share the instance, add this to ROOT as there can be only once definition per instance.
    • Name — customfooter.
    • Key — customfooter.
    • Alternative Set — The one identified above.
  3. For each survey that will include the custom footer:

    1. Open the survey on Surveys.

    2. From the Survey editor, click the content menu on the survey structure pane and choose Edit survey settings. This replaces the survey structure pane with the Survey settings pane.

    3. Click Show advanced settings and, under Other settings, select Show custom footer on every page.

    4. Click Save.

  4. From Company > Units > Groups Admin, define the custom footers on the Unit groups admin screen in the customfooter field you defined above. Any valid HTML is acceptable. Put the code in the highest Unit group applicable to the customization, either the top for all of the company's surveys, or an a parent for just that group's units.

    Important: When entering the HTML in the field, input it as one long line of text. The following examples have line-breaks to make them easier to read.

For v7 designs

This footer includes the Powered by Medallia logo and renders properly on light and dark backgrounds.

<div class="layout_footer">
	<i class="medallicons_medallicons layout_medalliaLogo">"</i>
	<div class="layout_legalLinks">
		<span class="copyright">Copyright © 2017</span>
		<a target="_blank" href="[INSERT SURVEY SUPPORT LINK]">Survey Support</a>
		<a href="[INSERT OTHER CONTACT INFO LINK]" target="_blank" rel="external">Other Contact Info</a>
		<a href="[INSERT PRIVACY POLICY LINK]" target="_blank" rel="external">Privacy Policy</a>
	</div>
</div>

For v6 and earlier designs

In this example, the Orion company has its own privacy policy page; the rest are the Experience Cloud default:

<ul class="legal-links" style="font-size: 12px;text-align: center;list-style: none;">
	<li class="copyright">Copyright © 2017</li>
	<li><a href="mailto:surveysupport_orion.e98adf@express.medallia.com" target="_blank" style="color:#0000ff;">Survey Support</a></li>
	<li><a href="http://www.medallia.com/contact" rel="external" style="color:#000000;">Other Contact Info</a></li>
	<li><a href="http://www.orion.com/about/privacy.html" rel="external" style="color:#000000;">Privacy Policy</a></li>
	<li><a href="http://survey.medallia.com/static/cookie-policy/index.html" rel="external" style="color:#000000;">Medallia Cookie Policy</a></li>
</ul>
Tip: If a Unit group is referenced by surveys that use both v6 and v7 designs, then its custom footer must have generic CSS that can work for both v6 and v7. Otherwise, restrict the Unit groups with which the different versioned surveys can be used to avoid overlaps.

Tips and best practices

  • Use a date field to display the copyright year instead of writing it manually and having to update it every year. Create an Event field for the current year and set it when creating the Invitation email, then reference that E-field in the custom footer. The field must be piped-in using the [=e-field] format.

  • You can pipe in other fields to dynamically display information on the custom footer.

  • To add a parameter to the custom footer, pipe in the field mapped to the parameter using the [=e_field] format. For more information, see Parameters screen.

  • Translate custom footers on the Translations screen, under the Category Hierarchy. When translating custom footers, check the Unit group translation status appears as OK as well.