Skip to main content
Use app attribution to separate usage from different products, environments, or customer-facing experiences. Attribution appears in app analytics and request audits without changing the inference response.

Add attribution headers

Send a stable app ID on every request. Add a name, URL, and up to three categories when you want richer dashboard grouping.
Use the same X-App-Id for every request from the same application. Phaseo uses it as the stable identity when a URL is unavailable.

Use the TypeScript SDK

Supported headers

HTTP-Referer is attribution metadata; it does not need to match the browser’s automatic Referer header. Set it explicitly in server-side integrations when you want one canonical app URL.

Categories

Choose up to three values:
  • chat
  • developer-tools
  • research
  • productivity
  • education
  • commerce
  • media
  • finance
  • other
Values are case-insensitive. Phaseo ignores unknown values, removes duplicates, and keeps the first three valid categories. Categories received on later requests are merged with categories already saved for the app; they do not remove dashboard selections. You can also edit categories in Gateway → Settings → Apps. Use the dashboard when classification is managed centrally rather than by application code.

Attribution guidelines

  • Keep IDs stable across deployments so usage remains grouped.
  • Use separate IDs for applications that need separate cost or usage reporting.
  • Do not put customer IDs, email addresses, or other personal data in attribution headers.
  • Treat the URL as public metadata when the app may appear in shared or public app views.
Last modified on August 23, 2026