For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • Getting Started
    • Overview
    • Best practices
  • Sightline Cyberfraud Defense
    • About Sightline Cyberfraud Defense
    • Getting Started
    • What's different in Sightline Cyberfraud Defense
    • Sensor changelog
    • About the Overview Dashboard
        • Set Custom Parameters
        • Data Classification Enrichment
        • Score Reporting
    • Glossary
  • AgenticTrust
    • Getting started with AgenticTrust
    • AI Agents Monitoring Dashboard
    • AI Visitors Overview Dashboard
    • Manage AI Agent Permissions
    • Agentic Activity Priority
    • Agent Trust Levels
  • Account Defender
    • Account Defender Overview
    • Use Cases
    • Prerequisites
    • Getting Started with Account Defender
    • Optimizing Account Defender Detection
    • Validating Account Defender Integration
    • Risk Triggers
    • About Network Events
    • Troubleshooting
  • Bot Defender
    • Bot Defender Overview
    • Detection
    • Bot Defender Policy Settings
    • Footprint
  • Credential Intelligence
    • Credential Intelligence Overview
    • How to Access the Breached Flag
    • Credential Intelligence FAQ
    • Credential Intelligence Dashboard
  • Code Defender
    • Code Defender Introduction
    • Getting Started with Code Defender
    • Code Defender Glossary
    • Website Risk Analyzer
  • Platform
    • Account settings
    • Manage users
    • Role permissions
    • Enforcer configurations
    • Page Type Mapping
  • Client-Side Integration
    • JavaScript tag
    • Improving first page performance
    • Use of cookies & web storage
    • Advanced client integration
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Prerequisites
  • Create custom parameters in Sightline’s Settings
  • Create custom parameters in the Sensor
Sightline Cyberfraud DefenseData SettingsData Enrichment

Set Custom Parameters

Was this page helpful?
Previous

Data classification enrichment

Next
Built with

Custom Parameters are custom values you can set yourself to further enrich data the HUMAN Sensor or Enforcer send. For example, you might choose to include a user ID or a session ID. You can use these parameters throughout Sightline to further customize and manage your policy rules, mitigation, and more.

You can set custom parameters in the following ways:

  • Sightline settings: Create and manage custom parameters directly from the HUMAN console.
  • Sensor: Define custom parameters in the Sensor JavaScript snippet.
  • Enforcers: Define custom parameters in the Enforcer’s configuration. See your specific Enforcer’s configuration documentation for more details.

If you set custom parameters in at least two places and they don’t match with each other, then HUMAN will prioritize custom parameters in the following order:

  1. Enforcer
  2. Sensor
  3. Sightline settings

You can have up to 10 custom parameters per application at a time.

Prerequisites

  • If you’re adding custom parameters in Sightline Settings, you need the appropriate role permissions to create and manage them. By default, this is an Admin role.
  • If you’re adding custom parameters in the Sensor, you need proper access to update the JavaScript snippet you added during your onboarding.

Create custom parameters in Sightline’s Settings

  1. Navigate to Sightline Cyberfraud Defense > Settings > Data > Data Enrichment and click the Custom Parameters tab.
  2. Choose the Application name and Application ID you want to create a custom parameter for.
  3. Click Add custom parameter.
  4. In the custom parameter row that appears, enter a Display name.
  5. If you’d like to use a query string, click the checkbox to enable it. Then, enter a query string param.
  6. Repeat Steps 3-5 for any additional parameters you want to create.
  7. Click Save Changes.

Create custom parameters in the Sensor

  1. Navigate to the Sensor JavaScript snippet you added to your domain.
  2. For each custom parameter you want to add to this domain, add window._pxParamN = "<paramN_value>", where N is the custom parameter number. See the example below.
1<script type="text/javascript">
2 (function(){
3 window._pxAppId = APP_ID;
4 // Custom parameters
5 window._pxParam1 = getCookie('my_cookie'); // extract the value of the custom parameter my_cookie
6 var p = document.getElementsByTagName('script')[0],
7 s = document.createElement('script');
8 s.async = 1;
9 s.src = '//client.perimeterx.net/APP_ID/main.min.js';
10 p.parentNode.insertBefore(s,p);
11 }());
12</script>