Add Telemetry metrics for Experiments

[john-thomas-dotcms]

Parent Issue

No response

Task

We need to add Telemetry metrics for all new features. For Experiments, we should track:

• Experiments feature flag enabled (true/false)
• Count of Experiments in each state:
  • Count of pages with Draft Experiments
  • Count of pages with Scheduled Experiments
  • Count of pages with Running Experiments
  • Count of pages with Ended Experiments
  • Count of pages with Archived Experiments
• Count of variants in Experiments in each state (among all pages):
  • Count of variants in all Draft Experiments
  • Count of variants in all Scheduled Experiments
  • Count of variants in all Running Experiments
  • Count of variants in all Ended Experiments
  • Count of variants in all Archived Experiments
• Count of each goal in all configured Experiments
  • Count of Experiments with Bounce Rate goal
  • Count of Experiments with Exit Rate goal
  • Count of Experiments with URL Parameter goal
  • Count of Experiments with Reach Page goal
• Activity
  • Count of Experiments edited in the past 30 days
    • This means the experiment config, not the variants
  • Count of variants edited in the past 30 days
    • Only if this is relatively easy to track; if not, we should skip it

Proposed Objective

Same as Parent Issue

Proposed Priority

Priority 2 - Important

Acceptance Criteria

1. Each of the metrics is accurately recorded in the telemetry database.
2. Each of the metrics is accurate when retrieved via the API.
3. Each metric is accurate when pages with Experiments live on different sites in the dotCMS instance.

Note: Activity metrics on a Push Publishing receiver can reflect all Experiments which have been pushed to the receiver from another environment, even if the changes were made on the other environment. We do not have to track changes made on the receiver separate from those made on the sender.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response