CVE Testing and Launch

Learn how to test and launch your CVE

You're almost there! Your tours content, content cards, campaign message and data are set up. Now, let's go through testing to get to launch.

Testing Overview

Before launching your CVE, make sure to test your tours and Adoption Kit. When you are ready to start testing, notify our team by clicking the "Publish" button for your tours. At this point, your tours should be completed, content cards should be activated, and if applicable, your campaigns should be created.

Once the published button is selected, you will receive an approval form along with your QR code, community link and text-in keyword from your CSM prompting you to start testing. You should test your tour content, communication methods, and content cards. Use this form to denote blockers for launch or to approve the launch with your signature. If there are technical issues that your team cannot fix, reach out to your CSM.

For any subsequent updates you make to your tours or Adoption Kit, no formal form needs to be filled out.

Tour Testing

Before indicating that you would like to publish your tours, it is a best practice to preview your tour content. To preview your tours, follow the steps below and use the update feature in the top right-hand corner of the tours page.

Use the "Open Preview" feature as often as you would like as you add, edit and iterate your content. Once the preview is opened, click on "Update Preview" and wait for the new preview to be generated.

Once your tour is published, use your approval form to guide your testing. You will need to have the Full Measure Tours app downloaded on your phone:

When testing the Full Measure Tours app, users should have iOS 13.2 or later and 7.0 and up for Android. Older versions will result in the app not performing as expected.

Tour Testing Best Practices:

Test on the web (both on desktop and mobile using tours.fullmeasure.io) and on the Full Measure Tours app with a mobile device
For mobile testing, test on Apple and Android devices, if possible
Test both on and off-campus
Complete both personalized and curated tours, if applicable
If particular about the order of locations and content headings, double check they convey as denoted in the platform

Adoption Kit Testing

Communication methods and content cards used in the Adoption Kit will differ from school to school, however, most tests should include:

Campaigns - tested autonomously by institution
1. Follow the campaign testing instructions
Text-in keyword
Community link
QR code
Review of content cards

Adoption Kit Testing Best Practices:

Test each communication method to ensure it directs toward the correct place
Check that each content card's content conveys as expected and desired
All links in content cards direct correctly
Social media designs work on each platform, if applicable
Confirm any additional tags/custom fields are working
- A note on tags and testing:
  
  Test recipients will see basic tags when receiving a test message: first name, last name, mobile phone number, contact ID, and email.
  
  If any custom tags were used, such as <<Student_Major>>, it would show in the content card and/or campaign message as: "your major" and not fill the major in for the test. If you would like to see custom tags during the testing process, please upload yourself as a contact and then include that contact in a test audience file.

CVE Post-Launch 🚀

After launching your CVE, meet with your CSM regularly to review engagement, adoption, and best practices.

Engagement Data Overview

Tours Data Overview

Additionally for tours, use our post-launch adoption recommendations to iterate on your tour and get the most of our partnership.

If a campaign is utilized, review engagement and follow up with accordingly. Use our Analyzing Student Engagement articles to help you.

You did it! You launched your Campus Visit Experience 🥳