This guide covers the key decisions and configurations involved in setting up Vev for your organisation, and links to detailed documentation for each topic. Bookmark this page — it's your single reference for everything technical.

Vev is a production tool, not a hosting platform. When your team publishes, the finished files are delivered to wherever you need them — your servers, your CMS, or your CI/CD pipeline. You can also publish directly to a custom domain using Vev's built-in Standard Hosting. For enterprise teams that need full control over their publishing process, we recommend webhook deployment.

Your hosting choice determines how you set up analytics. This is configured in the same area of the platform as your hosting.

Vev Standard Hosting: You configure analytics integrations directly inside Vev — no code required. Follow the guide to add your GA4, GTM, Hotjar, Meta Pixel, or other tracking tools:

You can also control where your tracking integrations are applied — at the account level (applies to everything), at the team or folder level, or on individual projects. This is useful when different teams or projects need different tracking IDs.

Any other hosting option (webhook, embed, export): Vev does not control the page your content is served on, so in-app analytics integrations are not available. Instead, you implement a listening script on your side to capture tracking events from Vev content:

You can restrict access to your live, published pages so only authenticated users can view them. This uses your organisation's identity provider and is configured as part of your hosting setup.

Set up your account structure — add your team members, assign the right roles, and organise your workspace. Vev uses a hierarchy of account → teams → folders → projects, and understanding this early makes everything else smoother.

Vev supports SAML-based Single Sign-On so your team authenticates through your existing identity provider — Okta, Azure AD, Google Workspace, OneLogin, ADFS, Auth0, JumpCloud, and others. SSO configuration is typically handled in a single session during onboarding with your Product Specialist.

For a full overview, see the Account Management collection.

The Vev API gives your development team programmatic control over the platform — create projects, manage pages, trigger publishing, and organise workspaces from code. Use it to integrate Vev into your existing workflows and deployment pipelines.