Code inclusion and exclusion conditions

Code inclusion/exclusion conditions let you control exactly where and when an integration's code runs on your knowledge base site. Instead of running a script across your entire site, you can target or exclude specific IP addresses, workspaces, or languages. This is useful for filtering out internal traffic from analytics, restricting a widget to a specific workspace, or limiting data collection to certain languages.

You can configure these conditions when adding or editing any integration in Document360.

Condition types

You can set conditions based on three criteria:

• IP address: allow or restrict the script for specific IP addresses or IP ranges.
• Workspace: show or hide the script for specific workspaces.
• Language: show or hide the script for specific languages.

When you add more than one condition, you can apply logic to control how they combine:

• AND: all conditions must be true for the script to run.
• OR: any one condition being true is enough for the script to run.

How to configure conditions

IP address condition

Use IP address conditions to allow or restrict the integration script based on the user's IP address. This is useful for excluding internal team traffic from analytics data.

1. On the Edit integration panel, in the Select Condition Type field, choose IP Address.
2. From the Include or Exclude dropdown, select Show or Hide depending on whether you want to include or exclude matching IPs.
3. In the IP type field, choose Exact to target a single IP address, or Range to target a block of addresses.
4. In the IP address field, enter the IP address or range.

Example: To collect analytics data only from internal users, choose Exact and enter your office IP. To cover a range of internal addresses, choose Range and define the start and end of the IP range.

Workspace condition

Use workspace conditions to show or hide the integration script on specific workspaces in your knowledge base.

1. On the Edit integration panel, in the Select Condition Type field, choose Workspace.
2. From the Include or Exclude dropdown, select Show or Hide depending on whether you want the script to run on or be excluded from the selected workspaces.
3. In the Select workspaces field, choose the workspaces to include or exclude. You can add multiple conditions for different workspaces as needed.

Language condition

Use language conditions to show or hide the integration script for specific languages on your knowledge base site.

1. On the Edit integration panel, in the Select Condition Type field, choose Language.
2. From the Include or Exclude dropdown, select Show or Hide depending on whether you want the script to run for or be excluded from the selected languages.
3. In the Select languages field, choose the languages to include or exclude. You can add multiple conditions for different languages as needed.

Best practices

• Exclude internal IP addresses from analytics integrations. If your team regularly visits the knowledge base, add an IP exclusion condition to prevent internal traffic from skewing your analytics data.
• Use workspace conditions when you have product-specific knowledge bases. If different workspaces serve different audiences, you can limit a chat widget or tracking script to only the workspaces where it is relevant.
• Use language conditions for region-specific tools. If you use a tool that is only licensed or relevant for certain regions, use a language condition to limit where it runs.
• Use AND logic when you need to narrow scope precisely. For example, to track only internal users on a specific workspace, combine an IP condition and a workspace condition with AND logic.
• Use OR logic when you want broader coverage. If a script should run for users from either of two workspaces, combine them with OR logic so it runs when either condition is met.

FAQ