Learn how integrations work in Vev, the hierarchy they follow, and how to configure them at the hosting, folder, or project level.
Integrating third-party tools such as Google Analytics, Google Tag Manager, and many more involves sharing data with external service providers.
Important note: Ensure you have a connected custom domain — integrations cannot be used without one.
How Integrations Work in Vev
Vev applies integrations using a top-down hierarchy. This means:
Hosting-level integrations apply to your entire website and cascade down to all folders and projects.
Folder-level integrations apply only to the projects within that folder.
Project-level integrations apply only to the individual project.
Example of the Hierarchy
If you add a Google Analytics tracking code at the hosting level:
Every folder and project under that hosting will automatically use the same tracking code.
If you want a different tracking ID for a specific folder or project, you can override the hosting level settings locally. This customization will not override or remove your hosting-level setup — it will simply apply to the selected folder or project.
Managing Hosting-Level Integrations
Hosting-level integrations affect your entire domain and are the most efficient way to apply global tools.
Steps to Configure a Hosting-Level Integration
Access the Hosting Settings
Go to your Vev dashboard.
Click your avatar in the top-left panel and click "Account settings" for the respective account.
Select Hosting, then choose the hosting instance you want to configure.
In the left panel, click Integrations.
On the left side, select Browse all to view available integrations.
Install the Integration
Find the integration you want (e.g., Google Analytics).
Click on it and select Install.
Configure the Settings
Enter your required credentials or tracking information.
Save your configuration.
Publish your project.
Best Practices for Integrations in Vev
Use hosting-level integrations whenever possible for simplicity and consistency.
Apply folder-level or project-level overrides only when you need unique tracking or behavior.
Review third-party privacy policies to stay compliant with regulations.