Measurement and interpretation · FIELD GUIDE
Plausible custom events: fix a received event with no goal count
Compare the emitted event name with the configured goal, including spaces and capitalization.
What the evidence can establish
In Plausible, emitting a custom event and configuring a matching goal are separate steps. The documentation requires the goal name to match the event name, including capitalization. CSS event classes add a specific trap: a plus sign represents a space in the emitted name. Inspect the actual name before changing the transport or adding another tracker.
Hypothetical configuration: plausible-event-name=Button+Click emits Button Click. A goal named Button+Click is a different string. Correcting the goal does not justify claiming that earlier events were backfilled; the documented troubleshooting flow asks for a new event after the goal is created.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- A plus sign in the event CSS class represents a space in the emitted name. Source 1
- c2 · Explanation and verification steps
- Custom events require a configured goal to show conversion numbers. Source 1
- c3 · Explanation and verification steps
- The goal name must match the emitted name character for character, including capitalization. Source 1
- c4 · Explanation and verification steps
- Plausible does not backfill past events when the goal is created later. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- Inspect the deployed element and its event class. Confirm that the content system preserved the required format.
- Trigger one authorized test action and inspect the emitted event name. Do not include personal data in the test label.
- Compare that exact string with the custom-event goal. Check spaces, capitalization and any property filters that narrow the goal.
- After correcting or creating the goal, trigger a new test action. Record the action time and the goal result separately from older events.
How to check the result
A passing check pairs one known post-configuration action with the correct emitted name and matching goal view. Preserve a screenshot or redacted event record showing the exact spelling used.
Limits of this conclusion
A matching name does not rule out all collection problems. This guide addresses goal configuration; the test still needs evidence that the event was actually sent and accepted.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-02T12:15:09.077556+00:00
Location: Add a CSS class name to the element you want to track on your site / b10; Create a custom event goal in your Plausible account / b35; Does the goal name match exactly? / b55; Has the event fired at least once after you created the goal? / b57
Saved source fingerprint
4a8b29279566febeddcc182cb2a3f1faf3f8b6fe4cfe052dab7987c1eaf95e74