Add crm telemetry#6695
Conversation
Signed-off-by: Karakatiza666 <bulakh.96@gmail.com>
…nceptualhq Signed-off-by: Karakatiza666 <bulakh.96@gmail.com>
| #[derive(Serialize, ToSchema)] | ||
| pub(crate) struct Configuration { | ||
| /// Telemetry key. | ||
| pub telemetry: String, |
There was a problem hiding this comment.
tnis is public facing IIRC we should just keep the name telemetry as is
we dont know if anyone parses this and relies on this key to be there, low risk but can be avoided
There was a problem hiding this comment.
@gz this is used only for web-console telemetry so realistically only used by us. I would like to update it to keep naming more meaningful and consistent with other providers, since again nothing else should be impacted. What I didn't touch for now are pipeline-manager options so that our deployments are not affected
mythical-fred
left a comment
There was a problem hiding this comment.
LGTM — solid gating, good tests.
| rel="noreferrer" | ||
| onclick={() => | ||
| captureEvent('calendly_opened', { | ||
| url: 'https://calendly.com/d/cqnj-p63-mbq/feldera-demo' |
There was a problem hiding this comment.
Nit: this Calendly URL is now hardcoded here and also in BookADemo.svelte (where it was extracted to a const). Consider sharing a single constant so there is one place to update if it ever changes.
Add hooks for Product Fruits (user guiding) and ConceptualHQ (conversion measurement telemetry), added conversion-related tracking for scheduling a demo through Calendly and trying canned demos.
In the API I renamed 'telemetry' to 'posthog' which is its actual contents. pipeline-manager and web-console update in lockstep so that's not a problem; the configuration option is still called 'telemetry' so existing deployments wouldn't change.