> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/building-interactive-demos/best-practices-and-launching/before-you-launch-check-list.md). # Before you Launch Check-List #### 1. Have I Set Up My Integrations? * **Seamless Integration:** Make sure you've connected Tourial to your marketing automation platform (MAP). Confirm that your Tourial forms are linked to your MAP forms and that you've whitelabeled your Tourial account to receive detailed, contact-level engagement data. #### 2. Can I Track My CTAs and Attribute the Leads Back to Tourial? * **Lead Flow Test:** Run a test lead through a Tourial form to ensure it enters your marketing automation platform correctly. * **Attribution:** Clearly label these leads as "Tourial" to differentiate them from other website demo leads, ensuring accurate tracking and reporting. #### 3. Have I Configured My CTAs? * **Best Practice:** Your tour should include CTAs in at least two key areas: the end of the tour and the persistent nav bar. * In the outro screen, use a modal for your CTA. * In the persistent nav bar, consider adding a "restart tour" button and a "book a demo" CTA to keep engagement levels high. #### 4. Have I Set Up Social Sharing Tags for the Title and Body Text? * **Social Media Preview:** To make your tour stand out when shared on platforms like LinkedIn or Slack, set up social sharing tags in your tour settings. This will generate a text snippet that shows a headline and description, enticing viewers to click through to your content. #### 5. Is My Tour Mobile-Optimized? * **Mobile Preview:** If you haven’t enabled "mobile responsive" in your tour settings, your tour won't be optimized for mobile devices. Turn on this feature in your tour settings, then preview your tour in the mobile viewer in-app and make any necessary adjustments. * **Pro Tip:** You may need to rearrange some tools or shorten the tour to enhance mobile engagement. #### 6. Have I Checked the Tour on All Frame Sizes? * **Responsive Design:** Tours dynamically adjust to fit the viewer's browser window. Use the frame size tool in Tourial to preview your tour across different sizes, ensuring it looks great on any screen. #### 7. Have I Tested an Embed? * **Embed Testing:** Each Tourial tour generates a unique landing page and embed code, making it easy to share across platforms. If you're embedding the tour on your website, test the embed code on a staging page to ensure everything displays perfectly. * **Our Recommendation:** While third-party embeds can work, we strongly recommend using the Tourial embed code for performance and stability. Finally, while most content in your tours can be updated on the fly without needing to re-embed, there are a few fundamental elements that, if changed, will alter the embed code of your tour and require re-embedding. These include: * Turning mobile responsiveness on or off. * Turning the persistent nav bar on or off. * Changing the white label status of your tours. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.navless.ai/building-interactive-demos/best-practices-and-launching/before-you-launch-check-list.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.