Summary

Docaroo provides out-of-the-box a series of integrations. The purpose of the integrations is to make available in a no-code or low-code mode some important features such as monitoring the performance of the site, collecting feedback, assessing the way in which the users are interacting with the site and more. Using these integrations offers a full image about the site and provides valuable information about how to improve it.

However, it is not mandatory to use the integrations, thus each integration can be independently enabled and configured or disabled. Integrations are configured using the environment variables and/or the configuration files.

Config files

Config options

Env variables

Integrations

Docaroo provides out-of-the-box a series of integrations with other platforms as listed below. The main purpose is to enhance the functionalities of the site and to provide means to monitor and measure the performance as well as to collect feedback from the users or advanced search features.

Use integrations

Use the integrations only in the case you really need to monitor/measure performance or you want advanced search or you need to collect feedback or you need to communicate somehow with your users through various forms. If not the case, you may simple disable them all or only some of them as further instructed. Everything will work fine even without integrations.

As general rule, the integrations are provided in no code/low code way. However, the framework on which Docaroo is built provides the options to extend the functionalities and enhance integrations in a traditional way … writing code.

Show 5 10 25 50

Platform	Purpose	Comments	No-Code	Low-Code	Advanced	Config file(s)	Code extensions
Google Analytics	collect site usage info	usually it collects GTM data too; recommended to be integrated with HubSpot to consolidate site interactions data	🟣			buildConfig.yml
Google Tag Manager	feature interactions	define custom tags and use hooks to trigger GTM tag updates; see also GTM documentation	🟣	🟣		buildConfig.yml	Hooks
HubSpot	feedback	create and use a feedback form	🟣		🟣	buildConfig.yml; siteConfig.yml	Custom code
New Relic	log; monitor	use hooks to log relevant actions and their results; monitoring works no-code	🟣	🟣		env	Hooks
GitHub	embed external content	use the pre-built Liquid tags to embed content from public and private repositories	🟣			env; buildConfig.yml
Algolia	search in site	Algolia DocSearch provided by default; Index updates provided for Algolia Search (no UI experience yet)	🟣		🟣	env; buildConfig.yml	Custom code

As general rule and except GA/GTM integration which does not depend at all on a Google paid plan or similar because Analytics and Tag Manager are free to use, all the other integrations can work well on the related platform free plans. In fact, for small/medium sites, the free plans of the integrated platforms are enough for regular operations. However, if the site gains more users and the traffic grows (which we all want 😁), paid plans for the integrated platforms should be considered.

While Algolia and HubSpot are less sensitive to this aspect (having a paid plan depends more on what additional features your business requires rather than on those features necessary for integration), New Relic may need a superior plan due its data retention and data ingestion limits in the free plan and Github may require a paid plan to increase the API limits.