-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Pendo Track events #6140
base: develop
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6140 +/- ##
=============================================
+ Coverage 30.42% 30.99% +0.57%
- Complexity 4826 4875 +49
=============================================
Files 290 296 +6
Lines 21329 21495 +166
=============================================
+ Hits 6489 6663 +174
+ Misses 14840 14832 -8 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3e92aa5
to
dd01619
Compare
|
I've added guards against requiring missing files during rollout in 436d377. There are no external consumers of these files, so nothing to guard on the usage side. |
Description
Provide telemetry for Pendo "Track events." These events are conceptually similar to Automattic Tracks events, but have a different payload structure. See an explanation of "Event types" on this page.
Usage is almost identical to that of Automattic Tracks. This PR introduces a generic
Telemetry
class that will send events to both Automattic Tracks and Pendo. Going forward, we will update our plugins to use theTelemetry
class.In general, I've tried to follow the implementation pattern provided by the existing Tracks implementation and the generic Telemetry base classes and interfaces. I did make some minor changes to the abstract class
Telemetry_Event
and the extendingTracks_Event
class in order to improve the abstraction and reduce code duplication.New constants will need to be provided in order to configure this functionality automatically:
VIP_PENDO_TRACK_INTEGRATION_KEY
: The integration API key used to authenticate with Pendo and send Track events. This key can only be used to write (append) events to Pendo's API.VIP_SF_ACCOUNT_ID
: The account ID added to event payloads and used to correlate Pendo events.Note
Client-side Pendo Page/Feature events has moved to #6150
Pre-review checklist
Please make sure the items below have been covered before requesting a review:
Pre-deploy checklist
Steps to Test
Telemetry
class and record events.