change: [M3-8129] - Temporarily disable form event analytics

[mjac0bs]

Description 📝

With our first implementation of form events (#10392) , there were some additional changes required that were not known in the initial implementation of code for the form event analytics. The working form events were reviewed by Front End and UX, but missing a complete MADS QA after added to the UI. (In the future, we will work this step into our review process for new/more complex analytics events to ensure this doesn't happen again.)

A MADS review of the changes was done after the PR was already merged, and changes requested are listed in the ticket tied to this subtask (M3-8126). While we work to clarify and confirm final changes, we need to stop the form analytics in develop from being released to prod. This subtask disables those events for now, since the release branch will be cut soon.

Changes 🔄

• Comments out the _satellite.track direct call rule that fires the form analytics events to prevent form analytics data from being sent to Adobe.

Target release date 🗓️

05/28

How to test 🧪

Prerequisites

(How to setup test environment)

• Follow the instructions in the developer's guide to enable Adobe event logging in the browser console.

Verification steps

(How to verify changes)

• Trigger any of the events shown in the preview table in change: [M3-7923] - Add analytics form tracking for Linode Create flow (v1) #10392 and confirm that they are NOT firing. You should see ONLY page view and custom events fired, no form events.

As an Author I have considered 🤔

Check all that apply

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 81.62%
Current Coverage: 81.62%