Customer email + custom properties

Direct Respan gateway example that populates Customer email / name / ID, filterable metadata, native custom properties, and model / token / cost on the request log.

Platform

API keys (optional)

Not persisted. This field is used first; otherwise routes use RESPAN_API_KEY from Vercel or .env.local.

Customer email + custom properties

Direct Respan gateway request with top-level customer_params, metadata, and properties. Populates customer columns, filterable metadata, native custom properties, and keeps model / tokens / cost intact.

Customer email

Sent as customer_params.email.

Customer name

Sent as customer_params.name.

Customer ID

Sent as customer_params.customer_identifier.

User message

What to verify in Respan

Logs view: model shows gpt-4o-mini with non-zero cost and tokens.
Log columns: Customer email, Customer name, and Customer ID are populated.
Log detail: metadata includes feature and plan_tier.
Log detail: properties includes account_region, billing_segment, seats, and renewal_risk.