Use this skill when a plugin wants to record product usage, LMS actions, purchase milestones, profile events, or any other contact activity into FluentCRM's event timeline and Pro automation conditions.
\nEvent tracking is core FluentCRM code, but it is disabled by default behind the experimental setting:
\nuse FluentCrm\\App\\Services\\Helper;\n\nif (!function_exists('FluentCrmApi') || !Helper::isExperimentalEnabled('event_tracking')) {\n return;\n}\nFluentCrmApi('event_tracker')->track() returns WP_Error('not_enabled', ...) when the flag is off. Always handle WP_Error.
The API key is event_tracker:
$event = FluentCrmApi('event_tracker')->track([\n 'subscriber_id' => (int) $contactId, // preferred when known\n 'provider' => 'my-plugin',\n 'event_key' => 'course_completed',\n 'title' => 'Course completed',\n 'value' => (string) $courseId,\n], true);\n\nif (is_wp_error($event)) {\n return;\n}\nSubscriber resolution order in Tracker::track():
subscriber object, when suppliedsubscriber_idemailuser_id converted to the WP user's emailfluentcrm_get_current_contact()Required fields are event_key and title. Both are truncated to 192 characters and sanitized. provider defaults to custom; value is sanitized as textarea text.
Second argument controls storage behavior:
\nFluentCrmApi('event_tracker')->track($data, true); // repeatable/default\nFluentCrmApi('event_tracker')->track($data, false); // append a new row every time\nWith $repeatable = true, FluentCRM looks up an existing row by (subscriber_id, event_key, title), updates value, increments counter, saves, and fires fluent_crm/event_tracked.
With $repeatable = false, it creates a new fc_event_tracking row every time and fires the same action.
There is no unique DB key for the repeatable lookup in 3.1.13; the counter is application-level, not an atomic financial counter. Use it for automation/activity state, not exact billing/accounting.
\nEventTrackingHandler also registers:
do_action('fluent_crm/track_event_activity', $data, $repeatable);\nThat delegates to FluentCrmApi('event_tracker')->track(), but do_action() discards the return value. Use the API method directly when you need the created EventTracker or WP_Error.
Every successful track fires:
\nadd_action('fluent_crm/event_tracked', function ($event, $subscriber) {\n // $event is FluentCrm\\App\\Models\\EventTracker\n // $subscriber is FluentCrm\\App\\Models\\Subscriber\n}, 10, 2);\nFluentCampaign Pro's \"Tracking Event Recorded\" trigger listens to this exact hook with actionArgNum = 2.
Pro trigger: FluentCampaign\\App\\Services\\Funnel\\Triggers\\TrackingEventRecordedTrigger
triggerName = fluent_crm/event_trackedstatus = subscribedevent_keyminimum_event_count against EventTracker.counterfluent_crm/event_tracking_condition_groupssource_trigger_name = fluent_crm/event_tracked and source_ref_id = $event->idPro action: FluentCampaign\\App\\Services\\Funnel\\Actions\\AddEventTrackerAction
add_contact_event_trackerfluent_crm/parse_campaign_email_textFluentCrmApi('event_tracker')->track($eventAtts, is_unique === yes)If you build a custom trigger/action around event tracking, still follow fluentcrm-funnel-trigger and fluentcrm-funnel-action for lifecycle and status rules.
EventTrackingHandler registers the advanced contact filter provider:
fluentcrm_contacts_filter_event_tracking\nSupported filter properties in 3.1.13:
\nevent_tracking_keyevent_tracking_titleevent_tracking_valueevent_tracking_key_countThe built-in option key for selectors is event_tracking_keys. It returns unique event_key values from fc_event_tracking as [{id, title}].
Do not register your own fluentcrm_ajax_options_event_tracking_keys filter unless you intentionally override/extend the built-in source. The core handler registers it with one accepted argument, while custom option filters usually use the 3-argument pattern described in fluentcrm-rest-options.
Event values are visible in the contact timeline widget and can feed automation conditions. Do not store access tokens, personal secrets, raw request bodies, or unbounded JSON blobs in value.
Good event shape:
\n[\n 'provider' => 'lw-lms',\n 'event_key' => 'lesson_completed',\n 'title' => 'Lesson completed',\n 'value' => (string) $lessonId,\n]\nBad event shape:
\n[\n 'event_key' => 'webhook_payload',\n 'title' => 'Webhook payload',\n 'value' => wp_json_encode($_POST), // too large, may contain secrets\n]\nWP_Error('not_enabled') as a model.subscriber_id. Use user_id for WP users, or resolve the FluentCRM contact first.fluent_crm/event_tracked, not fluentcrm_event_tracked.event_key. Keep event_key stable ASCII-like machine keys; put human text in title.fluentcrm-funnel-trigger for custom event-driven automation triggers.fluentcrm-funnel-action for custom automation actions that write tracked events.fluentcrm-smartcodes-segments when event values appear in SmartCodes or Pro dynamic segments.fluent-crm/app/Api/config.phpfluent-crm/app/Api/Classes/Tracker.phpfluent-crm/app/Models/EventTracker.phpfluent-crm/app/Models/Subscriber.phpfluent-crm/app/Hooks/Handlers/EventTrackingHandler.phpfluent-crm/app/Hooks/Handlers/Integrations.phpfluent-crm/app/Services/Helper.phpfluent-crm/database/migrations/SubscriberEventTracking.phpfluentcampaign-pro/app/Services/Funnel/Triggers/TrackingEventRecordedTrigger.phpfluentcampaign-pro/app/Services/Funnel/Actions/AddEventTrackerAction.phpfluentcampaign-pro/app/Services/Funnel/Conditions/FunnelConditionHelper.php