Form Blocking Tests

Test identity detection blocking rules - forms that should NOT trigger pp events

What These Tests Cover

Forms can be blocked from identity detection by: form_id, structural_hash, or location_pattern. These tests verify that blocked forms do NOT emit pp events, while similar non-blocked forms DO emit events.

Path-Based Blocking Tests

These pages test blocking rules that match URL paths:

/internal/* (Blocked) /admin/** (Blocked) /careers/*/apply (Blocked) /support/* + Hash (Blocked)

ID-Based Blocking

Admin Login Form BLOCKED

Rule: ID = "admin-login-form"

This form has id="admin-login-form" which matches the blocking rule.

Expected: NO pp event - form is blocked by ID

User Login Form ALLOWED

ID: "user-login-form" (not blocked)

This form has id="user-login-form" which does NOT match any blocking rule.

Expected: pp event SHOULD fire - form is not blocked

Internal Employee Survey BLOCKED

Rule: ID = "hs_form_internal_survey"

This form has id="hs_form_internal_survey" simulating a blocked HubSpot form.

Expected: NO pp event - form is blocked by HubSpot ID

Contact Us Form ALLOWED

ID: "hs_form_contact_us" (not blocked)

This form has id="hs_form_contact_us" which is NOT in the blocklist.

Expected: pp event SHOULD fire - this HubSpot form is not blocked

Control Forms (Always Allowed)

Newsletter Signup ALLOWED

ID: "newsletter-form" (no matching rules)

A simple newsletter form that should always capture identity.

Expected: pp event SHOULD fire - control form

Request Demo ALLOWED

ID: "demo-request-form" (no matching rules)

A demo request form that should always capture identity.

Expected: pp event SHOULD fire - control form
[Ready] Form Blocking Tests Loaded