How to Set Up Flint Microsites

Last updated: May 20, 2026

Setup Flint Microsites

Flint microsites are hosted within Flint, separate from your existing website (e.g., Webflow). To make pages accessible from your own domain, URL forwarding is configured so visitors reach Flint pages seamlessly. Follow the steps below to get your pages set up and published:

  1. Work with the Flint team to determine your preferred URL structure. Pages can be served as a subdomain (e.g., try.yourcompany.com/page-name) or as a subdirectory (e.g., yourcompany.com/lp/page-name), where the subpath (e.g., lp) can be customized to your preference.

  2. Coordinate with your web team to set up domain forwarding so that Flint-hosted pages are accessible from your chosen domain.

  3. Build your page in Flint. You can import an existing page from your website as a visual reference. Note that Flint performs a one-time import of a page — to bring in additional pages, provide Flint with visual references of the URL. See the import pages guide for details.

  4. Once your page is ready, mark it as Ready in Flint and then click Publish to make it live. Pages that are marked as Hidden will return a 404 error until they are published.

    Image of a list showing two hidden pages, each labeled Hidden with a rounded badge.
  5. Connect Flint to your Google Tag Manager or Google Analytics account to track page views and visitor activity on your Flint pages alongside your existing analytics setup.

Usage

Once your Flint pages are live, here are a few things to keep in mind:

  • Analytics: Flint integrates with Google Tag Manager and Google Analytics, giving you visibility into page views on Flint pages. Note that Flint's analytics are separate from your main website analytics (e.g., Webflow), so be sure to account for this when reviewing goal tracking.

  • Page management: You can view all published and draft pages from within the Flint dashboard. Pages in draft state are not publicly accessible until published. To unpublish a page, mark it as Hidden — it will return a 404 until republished.

  • Team access: Team members can be invited to Flint directly. Reach out to the Flint team to send invites to additional users who need access to manage or review pages.

  • Page URLs: Active Flint pages follow the URL structure configured during setup. For example, pages might be accessible at paths such as lp.yourcompany.com/page-name or yourcompany.com/lp/page-name.