Header enrichment

August 6, 2026
5 out of 5
Header Enrichment (HE) is a technology that allows a mobile carrier to add subscriber information to HTTP requests passing through its network. These additional HTTP headers let web services identify users without asking them to enter a phone number or other details.

How Header Enrichment Works

When a subscriber opens a website or mobile app over the carrier’s network, the HTTP request passes through network elements that can analyze and modify traffic. This function is typically performed by DPI platforms such as the Stingray traffic control and analysis platform by VAS Experts, proxy servers, or specialized service gateways.

While processing the request, the system can add one or more HTTP headers containing subscriber information, for example:

  • A unique user identifier
  • Phone number (MSISDN)
  • Session ID
  • Plan or connection type details
  • Home network information

The web service then receives this additional data and can automatically log the user in or offer personalized services.

What Data Can Be Passed

The set of headers depends on the carrier’s requirements and the specific service.

Header Purpose
MSISDN Passes the subscriber’s phone number
Subscriber ID Unique user identifier
Session ID Current session identifier
Operator ID Mobile carrier identifier
Device Information Device or connection type details

In practice, carriers rarely pass phone numbers in plain text. More often, they use temporary identifiers or tokens that identify the user without exposing personal data.

Where Header Enrichment Is Used

The technology is used in services that need to identify users quickly without extra sign-up steps.

Main use cases:

  • Mobile subscription sign-ups
  • Phone number–based authentication
  • Digital content payments
  • Mobile banking services
  • Carrier partner programs
  • Web app personalization

In many countries, the technology is used together with Single Sign-On (SSO), so users are automatically identified when they connect over the mobile network.

Benefits and Limitations

Benefits Limitations
Fast login without entering a phone number Works only over the mobile carrier’s network
Better user experience Requires user consent as mandated by law
Service personalization Not supported with VPNs or some proxies
Integration with carrier platforms Limited by the carrier’s security policies

Header Enrichment Security

Passing additional information requires strict compliance with personal data protection requirements.

Today’s carriers rely on several security mechanisms:

  • Passing data only over secure HTTPS connections
  • Replacing phone numbers with pseudonyms or tokens
  • Restricting which services can access the additional headers
  • Logging use of the technology
  • Applying user consent management mechanisms

Processing this kind of data is governed by the GDPR and other regulations, depending on the country.

The Role of DPI in Header Enrichment

To implement HE, a carrier needs to analyze HTTP and HTTPS traffic, determine user session parameters, and apply request-handling policies. These tasks are often handled by DPI (Deep Packet Inspection) and policy enforcement systems (PCRF/PCEF).

VAS Experts solutions make it possible to analyze mobile subscriber traffic, manage service policies, and integrate with carriers’ service platforms.

Learn more about our mobile network solutions on the dedicated page.

Technical FAQ

What is Header Enrichment in simple terms?

Header Enrichment is a technology in which the carrier automatically adds subscriber data to HTTP requests. This lets a web service identify the user without asking for a phone number or username.

What data is passed through Header Enrichment?

Depending on the carrier’s settings, this may include the subscriber ID, phone number (MSISDN), session ID, network information, or a temporary token. Modern networks favor anonymized identifiers.

Does Header Enrichment work over Wi-Fi?

Usually not. The technology is designed to work on the carrier’s mobile network. When connecting via Wi-Fi, a VPN, or a third-party proxy, the additional headers are typically not added.

How secure is Header Enrichment?

When implemented correctly, the technology meets modern security requirements. Data is transmitted over secure connections, and personal information can be replaced with temporary identifiers or tokens.