dev: expand tracking

[Soare-Robert-Daniel]

Summary

• Update the last onboarding step
  • Make tracking opt-in when the user subscribes with their email.
  • Add tracking notice in the email subscription.
  • Send the selected choice at the first step along with the email subscription event.
• New usage data
  • Track the first import created.
  • Track the first import run.
  • Track the counts of import runs.
  • Add it to the 'feedzy_rss_feeds_logger_data'
  • Trigger the data send on uninstall to make sure we capture the first import creation/run.
• Track the creation/deletion of Feedzy Classic, Loop, and RSS with increment/decrement event for reporting the retention and usage.

Note

The first time track usage will be available only for newer users after the release. Condition: install time lower than 24 hours.

Will affect visual aspect of the product

Yes

Screenshots

Improved boarding message with opt-in tracking

Metabase events for Block Usage

Metabase visualization for categories of user time between first import settings creation and first run.

Note

The time is registered only if the import run timestamp is lower than creation, which means older users who have daily crons running in the background will be unlikely to be counted. Part of For projects running to avoid data from older users where we don't have the first new import click, we can enable this for projects that were created after the deployment.

Test instructions

1. Install the plugin with telemetry active (either in Onboardin via email or in Settings > Enable Telemetry)
2. Make a new import and run it, then deactivate the plugin.
3. Check in Metabase to see if it was registered.

Check before Pull Request is ready:

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

Closes https://github.com/Codeinwp/feedzy-rss-feeds-pro/issues/847
Closes https://github.com/Codeinwp/feedzy-rss-feeds-pro/issues/846

[Copilot]

Pull Request Overview

This PR expands telemetry tracking by making it opt-in in the onboarding wizard, adding new usage events, and ensuring collected data is sent on uninstall.

• Add block-usage tracking in the Gutenberg editor and wire it into the telemetry system.
• Update the setup wizard UI to include an opt-in tracking notice and revised button text.
• Implement backend hooks to record import creation/run timestamps and counts, with data sent on deactivation.

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
js/FeedzyLoop/tracking.js	Add block usage monitoring and analytics event emission.
js/FeedzyLoop/index.js	Import the new tracking module.
includes/views/css/style-wizard.css	Refactor wizard stylesheet and add styles for the new opt-in UI.
includes/layouts/setup-wizard.php	Inject opt-in tracking markup and update wizard button labels.
includes/feedzy-rss-feeds-deactivator.php	Trigger telemetry data send on plugin deactivation.
includes/admin/feedzy-rss-feeds-usage.php	Introduce a Feedzy_Rss_Feeds_Usage class to store and compute stats.
includes/admin/feedzy-rss-feeds-import.php	Hook usage tracking into import creation and run flows.
includes/admin/feedzy-rss-feeds-admin.php	Track import creation via post meta and set telemetry flag on opt-in.
includes/abstract/feedzy-rss-feeds-admin-abstract.php	Merge usage stats into the admin usage data output.

Comments suppressed due to low confidence (2)

includes/admin/feedzy-rss-feeds-usage.php:1

• New usage tracking methods (track_rss_import, track_import_creation, etc.) have been added. Consider adding unit or integration tests to cover these methods and validate their behavior over time.

<?php

js/FeedzyLoop/tracking.js:103

• The subscribe function from @wordpress/data typically accepts only the listener callback and does not take a store parameter. Verify the API signature or use store.subscribe directly, or call subscribe(() => updateBlockCounts()) without the second argument.

		const unsubscribe = subscribe(updateBlockCounts, blockEditorStore);

[pirate-bot]

Plugin build for 4e78ca1 is ready 🛎️!

• Download build

Note

You can preview the changes in the Playground

[abaicus]

Looks good @Soare-Robert-Daniel. Just a small nitpick.

[abaicus]

I think we can early-return here so we reduce nesting.

[pirate-bot]

🎉 This PR is included in version 5.0.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀