Meta tags:
description= Embed third-party tools in your Document360 knowledge base using Custom HTML. Add chatbots, analytics, and more without native integrations.;
Headings (most frequently used words):
custom, html, documentation, index, why, use, before, you, begin, add, manage, snippet, best, practices, faq, document360, top, features, support, contact, us,
Text of the page (most frequently used words):
the (61), for (38), custom (37), html (29), and (23), your (22), integrations (21), page (20), code (16), #snippet (15), add (14), document360 (13), analytics (12), site (12), this (12), that (12), you (11), knowledge (10), base (10), icon (10), use (10), script (10), article (9), native (9), body (9), scripts (9), integration (8), third (8), party (8), tools (8), not (8), only (8), content (8), can (8), widgets (7), icons (7), workspaces (7), tool (7), feedback (6), extensions (6), inclusion (6), exclusion (6), conditions (6), after (6), stylesheet (6), elements (6), example (6), every (6), runs (6), chat (6), manage (6), widget (6), tracking (6), click (6), support (5), any (5), load (5), all (5), project (5), workspace (5), each (5), such (5), before (5), snippets (5), one (5), 2026 (5), documentation (4), portal (4), javascript (4), material (4), font (4), reference (4), span (4), edit (4), specific (4), need (4), with (4), chatbot (4), provider (4), they (4), multiple (4), should (4), end (4), where (4), open (4), have (4), about (3), api (3), features (3), customization (3), added (3), when (3), are (3), level (3), check (3), see (3), url (3), based (3), different (3), paste (3), into (3), header (3), adding (3), separate (3), entry (3), most (3), below (3), readers (3), across (3), feature (3), want (3), run (3), possible (3), description (3), from (3), ask (3), policy (2), our (2), team (2), com (2), contact (2), drive (2), workflow (2), platform (2), top (2), private (2), hosting (2), request (2), css (2), other (2), articles (2), next (2), within (2), library (2), but (2), class (2), needed (2), wide (2), link (2), tag (2), remove (2), them (2), why (2), configuration (2), behavior (2), exists (2), instead (2), without (2), place (2), position (2), best (2), appears (2), installed (2), list (2), many (2), applied (2), limit (2), which (2), pages (2), include (2), individual (2), embedding (2), languages (2), control (2), early (2), identify (2), delete (2), hover (2), over (2), update (2), overview (2), editor (2), start (2), connections (2), access (2), embed (2), doesn (2), service (2), claude (2), chatgpt (2), view (2), markdown (2), copy (2), llms (2), ctrl (2), search (2), glossary (2), october (2), docs (2), review (2), file (2), index (2), soc2, cookie, privacy, trust, center, terms, careers, culture, 3000, rating, status, seo, ticket, deflector, assistant, enterprise, readiness, security, migration, demo, resources, pricing, customers, tags, related, previous, yes, was, helpful, still, display, correctly, confirming, loaded, markup, inspect, may, overriding, styling, happens, contains, also, literal, alone, additional, treated, real, rendered, fix, keep, inside, string, appearing, fonts, applies, setup, supported, currently, offer, differentiate, chatbots, mixpanel, hotjar, amplitude, initializes, loads, what, approach, toggled, off, independently, how, placed, ensures, slow, down, filter, language, details, faq, itself, visible, just, will, render, actual, appear, simpler, less, error, prone, than, manual, first, certain, addresses, scope, new, tab, verify, loading, expected, announcing, test, like, heatmap, recorders, session, often, initialize, capture, accurate, data, placement, placing, means, keeps, fast, entries, descriptive, label, makes, easy, clear, practices, confirmation, prompt, save, changes, insertion, now, active, field, choose, insert, common, choice, libraries, above, head, enter, live, under, navigate, left, navigation, bar, ready, typically, provided, installation, must, admin, begin, per, note, needing, buttons, using, pixels, event, advertising, marketing, platforms, niche, cover, range, has, fills, gap, lets, directly, while, offers, popular, there, everything, else, pixel, button, dedicated, way, prev, summary, plain, text, print, listen, focus, minute, read, published, jun, updated, aug, powered, press, community, self, troubleshooting, help, november, release, notes, integrate, manager, domain, import, export, reminder, collaboration, tasks, interactive, decision, trees, fields, management, templates, variables, advanced, single, sign, role, key, creators, eddy, track, set, roles, permissions, invite, users, customize, publish, create, quick, discover, available, exploring, further, fetch, complete, https, txt,
Text of the page (random words):
custom html documentation index fetch the complete documentation index at https docs document360 com llms txt use this file to discover all available pages before exploring further quick start create an article review article publish article customize site invite users set up roles permissions track analytics eddy ai features for creators for readers for integrations key features multiple workspaces languages role based access control single sign on private hosting advanced editor templates variables snippets glossary drive file management custom fields interactive decision trees collaboration tasks custom workflow review reminder import export project site customization custom domain integrations extensions analytics feedback manager api documentation integrate with document360 manage your api docs release notes november 2026 12 11 1 october 2026 12 10 2 october 2026 12 10 1 help troubleshooting self service support ask for a feature community glossary search ctrl k press ctrl k to open search powered by custom html updated on aug 31 2026 published on jun 25 2026 5 minute s read focus listen print copy page copy as markdown for llms view as markdown view the page as plain text open in chatgpt ask chatgpt about this page open in claude ask claude about this page article summary prev next custom html lets you embed any third party tool or script into your document360 knowledge base site by adding code directly to your page while document360 offers native integrations for many popular tools custom html is there for everything else any widget chatbot analytics script tracking pixel or custom button that doesn t have a dedicated integration can be added this way you manage custom html snippets from connections integrations in your knowledge base portal why use custom html the native integrations in document360 cover a wide range of tools but not every third party service has one custom html fills that gap use it when you want to add a third party tool that doesn t have a native document360 integration such as a custom chatbot a feedback widget or a niche analytics script embed tracking pixels or custom event scripts for advertising or marketing platforms add custom buttons or ui elements to your knowledge base site using html and javascript run multiple different scripts on your site without needing a separate native integration for each one note custom html is applied at the project level and runs across all workspaces it is not possible to add separate html or javascript for individual workspaces if you need workspace specific behavior for example different chatbot scripts per workspace check with your tool provider to see if they support url based configuration before you begin you must have admin access to your document360 knowledge base portal have your third party code snippet ready to paste this is typically provided by the tool you are embedding for example a script tag from your analytics platform or a widget installation code from a chat provider add custom html in the document360 portal navigate to connections integrations in the left navigation bar under custom html click add enter a description to identify this snippet for example live chat widget or analytics tracking script choose where to insert the code on your page in the header above head for scripts that need to load before the page content such as analytics tracking or font libraries at the start of body below body for scripts that should run as early as possible in the page body at the end of body below body for scripts that can load after the page content such as chat widgets or feedback tools this is the most common choice for third party widgets paste your code snippet into the code editor field click add your snippet is now active and appears in the installed integrations list on the integrations overview page manage custom html snippet to edit a snippet in the integrations overview page hover over the custom html entry and click the edit icon update the description insertion position or code as needed click update to save the changes to remove a snippet hover over the custom html entry and click the delete icon click delete in the confirmation prompt best practices add a clear description for every snippet if you manage multiple custom html entries for example one for a chat widget and one for a tracking script a descriptive label makes it easy to identify and manage each one use end body for most third party widgets placing scripts at the end of the body means they load after your page content which keeps your knowledge base site fast for readers use header placement for analytics and tracking scripts tools like heatmap recorders or session analytics often need to initialize as early as possible to capture accurate data test each snippet after adding it open your knowledge base site in a new tab and verify the tool or widget is loading as expected before announcing it to your team use code inclusion exclusion conditions to limit scope if a script should only run for certain ip addresses workspaces or languages use the code inclusion and exclusion conditions feature to control where it runs check with your provider for native integrations first if a native document360 integration exists for the tool you want to add use that instead native integrations are simpler to manage and less error prone than manual code snippets when embedding a font or icon library for example material icons include only the stylesheet link reference in your custom html snippet do not include individual icon elements such as span class material icons in the snippet itself custom html runs on every page across the project so any visible html content in the snippet not just the stylesheet reference will render on every page add the actual icon elements only within the specific article content where you want them to appear faq can i add custom html to specific workspaces only no custom html is applied at the project level and runs across all workspaces to limit which pages a script runs on use the code inclusion exclusion conditions feature to filter by workspace or language see code inclusion and exclusion conditions for details where should i place scripts for chat widgets or feedback tools most chat widgets and feedback tools should be placed at the end of body below body this ensures they load after the page content and do not slow down your knowledge base site for readers how many custom html snippets can i add you can add multiple custom html snippets each appears as a separate entry in the installed integrations list and can be toggled on or off independently what is the best approach for adding an analytics script if a native integration exists for your analytics tool such as mixpanel hotjar or amplitude use that instead for tools without a native integration paste the script into custom html and place it in the header position so it initializes before page content loads can i add different third party chatbots for each workspace no custom html runs at the project level so it applies to all workspaces this setup is not supported in document360 currently check with your chatbot provider to see if they offer url based configuration that can differentiate behavior by workspace url why is a string of icons appearing at the top of every page after i added a custom html snippet for icon fonts this happens when the custom html snippet contains not only the icon library s stylesheet reference but also literal icon elements for example span class material icons edit span the stylesheet reference alone is only needed to load the font any additional html elements in the snippet are treated as real page content and rendered on every page site wide to fix this edit the integration to keep only the stylesheet link tag and remove all icon span elements add icons only inside the specific articles that need them if icons still do not display correctly after confirming that the stylesheet is loaded and the icon markup is added within the article inspect the page for any custom css or javascript that may be overriding the material icons font styling was this article helpful yes no previous article integrations next article code inclusion and exclusion conditions related articles integrations integrations extensions widgets other integrations extensions integrations code inclusion and exclusion conditions integrations extensions widgets other integrations extensions integrations custom css site customization custom code custom javascript site customization custom code tags third party tools document360 integration custom html document360 customers pricing resources request a demo migration request security private hosting enterprise readiness top features knowledge base portal knowledge base site knowledge base assistant integrations and extensions platform api analytics workflow ticket deflector drive seo support documentation support status feedback contact us contact us support document360 com rating 4 7 3000 about us our team our culture careers terms trust center privacy policy cookie policy soc2
|
