You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can only control session recording based on URL and event pattern programmatically.
Describe the solution you'd like
Start recording when a URL is visited, this is configured using Glob patterns via project config.
Start recording when certain events are captured, this is configured via project config.
Describe alternatives you've considered
Start recording when a feature flag is active is possible, see this section and this one of the docs (requires cost control enabled).
Start recording when a URL is visited is possible programmatically, see this section of the docs.
Start recording when an event is triggered is possible programmatically, see this section of the docs.
Additional context
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered:
Recording when specific UTM params are passed would be super helpful for tracking the behavior of users that come in from a particular advertising campaign.
Is your feature request related to a problem?
https://posthoghelp.zendesk.com/agent/tickets/9754
https://posthog.com/questions/question-113
You can only control session recording based on URL and event pattern programmatically.
Describe the solution you'd like
Start recording when a URL is visited, this is configured using Glob patterns via project config.
Start recording when certain events are captured, this is configured via project config.
Describe alternatives you've considered
Start recording when a feature flag is active is possible, see this section and this one of the docs (requires cost control enabled).
Start recording when a URL is visited is possible programmatically, see this section of the docs.
Start recording when an event is triggered is possible programmatically, see this section of the docs.
Additional context
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: