Skip to main content
By default, the AppSignal integrations will track request session data for web applications in supported libraries. You can set custom request session data on a transaction or span. Modifying the session data will overwrite the data set by the AppSignal instrumentations. All request session data is filtered by our integrations before being sent to our servers.
🔐 Do not send Personal Identifiable Information (PII) to AppSignal. Filter PII (e.g., names, emails) and use an ID, hash, or pseudonymized identifier instead.

Use Link Templates to link them back in your app.
See the table below for a list of accepted root values per language. Each nested object can contain values that result in valid JSON (strings, integers, floats, booleans, nulls, etc.).
LanguageAccepted root values
RubyArrays, Hashes
JavaScriptArrays, Objects
ElixirLists, Maps
PythonLists, Maps
GoJSON serialized string
JavaJSON serialized string
PHPArrays, Objects
# Call `add_session_data` multiple times to set more session data
Appsignal.add_session_data(
  :user_id => "123",
  :menu => { :type => "hamburger" }
)
Appsignal.add_session_data(:menu => { :state => "closed" })
Appsignal.add_session_data(:menu => { :state => "open" })
# Session data:
# {
#   :user_id => "123",
#   :menu => { :state => "open" }
# }
For certain languages, additional setup is required. Please follow the instructions for these languages: session_data

​
Limitations

If the application sets session data multiple times, the Ruby gem will merge values at the root level. For other integrations, only the last set value is stored.