Option A: Advanced use (your own site or app)
In the Growth Score panel, Add Event, Event type Custom, set name, description, points per event, Tracking method Advanced use.
Save the event. The UI shows a JavaScript snippet that uses your site AJAX endpoint to record one occurrence.
Copy that snippet and call it when the action happens (e.g. on form submit, button click, or after a successful API call in your app).
Use case: Newsletter signup button, Lead submitted form, Download started. Any event on a page that can run JavaScript and reach your WordPress admin-ajax or REST endpoint.
Option B: REST API
You can record an occurrence for an existing growth event by calling the FleekDash REST API with authentication.
Endpoint: POST /wp-json/fleekdash/v1/growth-meter/events/{id}/record
Body (optional): { "custom_points": 10 } to override points for that single occurrence if your backend supports it.
Auth: Same as other FleekDash REST endpoints. For server-to-server you need a valid auth method your site supports.
First, get the event ID: call GET /wp-json/fleekdash/v1/growth-meter/events and find the event by event_type or name. Then POST to .../events/{id}/record to add one occurrence. The Growth Score will update according to that event configured points (or custom_points if applied).
Use case: CRM webhook, Zapier, external app, or cron job that POSTs to FleekDash when something happens outside WordPress.
Option C: PHP (inside WordPress)
From theme, plugin, or any PHP code on the same WordPress install use:
do_action('fleekdash_track_site_event', 'your_event_type', []);
The event type must exist and be active in Growth Meter (e.g. a Custom event with a unique event_type). This increments the occurrence and updates the score.
Use case: Custom form handler, membership plugin, or internal automation that runs inside WordPress.
Option D: Webhook (planned)
The Growth Score UI mentions Webhook as a tracking method for Custom events. When available, you will get an endpoint URL to send HTTP POST requests from external systems. Until then, use REST API (Option B) or Advanced use (Option A).
In Step 5 we will summarize benefits and use cases.