Custom headers allow you to add custom HTTP headers and User-Agent overrides to your Audits and Journeys.
What Are Custom Headers?
Custom headers are user-defined HTTP headers that are automatically included in HTTP requests and responses made by ObservePoint during Audits and Journeys.
Why Use Custom Headers?
Secure Access to Pre-Production Sites: Add a secret authentication header to simulate access from an internal user.
Simulate Real-World Behavior: Toggle product availability for testing purposes, switch user types, or activate beta/preview features.
URL-Based Targeting: Send headers only to relevant domains, URL paths, etc. Target pages or other technologies, like analytics, trackers, etc.
No Regex Needed: Use simple patterns with wildcards.
Reusable Configurations: Set once, apply everywhere.
To get started, go to Configuration --> Custom Headers, and click Create Custom Header Set.
How It Works
1. Create a Custom Header Set
From the Configurations section in the main navigation, create a Custom Header Set. Each header set can include:
A Name to identify it
One or more Custom Headers (name-value pairs, like
X-Debug-Mode: true)Select whether it applies to Requests or Responses
✅ These header sets are reusable across all Audits and Journeys, or only those you choose.
2. Define URL Filters
With URL filters, you can choose which network requests ObservePoint will apply the headers.
URL filters are flexible:
Accepts domains and paths:
example.com/productsAllows
*wildcard matching:example.com/teams/*/profileor*to match all URLsDoes not support full regular expressions
Handles
http/httpsand subdomain matching automatically
Examples:
example.com/cart/checkoutexample.com/*/b/ss/*
Subdomain Handling
You can choose whether headers apply to subdomains:
✅ Allow all subdomains → If you enter
example.com, the headers will be applied toexample.comand any subdomain ofexample.comlikeblog.example.com⛔ Not checked → Headers will only be applied to
example.com, and none of its subdomains
3. Apply to Audits & Journeys
You can apply a header set to any Audit or Journey, or, optionally, you can apply it to all Audits and Journeys (which will also automatically assign it to Audits and Journeys you create in the future).
You can disable a header set by removing it from all Audits and Journeys, without losing your header set configuration.
Frequently Asked Questions
Can I specify custom request and response headers?
Yes. Both request and response headers are supported. Certain header names are not allowed for security reasons. If you try to use one of these restricted headers, ObservePoint won't let you save the header set.
Can I make headers apply to all new data sources without having to manually specify them on each data source?
Yes, you can configure header sets to be automatically applied to all Audits and Journeys. Then, any new Audit or Journey which you create will automatically send your custom headers.
Can I configure multiple headers for the same request URL?
Yes, you can configure multiple headers for the same URL pattern. Each custom header operates independently.
Are custom headers applied to redirects?
Yes. Custom headers apply to the initial request and any subsequent requests that match the configured URL patterns.
Do custom headers apply only on page load, or all network requests?
No, Custom headers apply to all network requests that match your specified rules, including page loads and any request that happens after page load, such as image loads, tracker calls, analytics requests, remarketing requests, form submissions, etc. All request methods are supported, including GET, POST, PUT, DELETE, etc.
Use Cases
Access staging environments without VPN
Simulate logged-in or premium users
Trigger debug or feature flags
Ensure product appears in stock for testing