{
  "acceptance": "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.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A plus sign in the event CSS class represents a space in the emitted name."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Custom events require a configured goal to show conversion numbers."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The goal name must match the emitted name character for character, including capitalization."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Plausible does not backfill past events when the goal is created later."
    }
  ],
  "description": "Compare the emitted event name with the configured goal, including spaces and capitalization.",
  "diagram": [
    "Inspect the event class",
    "Read the emitted name",
    "Match the configured goal",
    "Trigger a new test action"
  ],
  "draft_hash": "d16ebad207639b74fce8a27ea1534d663eebb2e84052cfceb57490035ffb0121",
  "evidence": {
    "observed_at": "2026-11-02T12:15:09.077556+00:00",
    "period": {
      "end": "2026-11-02T12:15:09.077556+00:00",
      "start": "2026-11-02T12:15:09.077556+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Confirm the deployed CSS event-name syntax.",
    "A plus sign in the class becomes a space in the name.",
    "Check exact spelling, spaces and capitalization.",
    "Newly created goals do not backfill earlier events."
  ],
  "figure_title": "Plausible custom events: fix a received event with no goal count",
  "group": "Measurement and interpretation",
  "human_review_claim": false,
  "intent": "plausible-event-name-goal-matching",
  "interpretation": "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.",
  "keyword_volume": "Not obtained",
  "limits": "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.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/plausible-event-name-goal-matching/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A custom event is sent but its expected conversion count does not appear.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T07:25:04.154392+00:00",
  "reader": "Site owners and analysts investigating a custom event is sent but its expected conversion count does not appear.",
  "related": [
    "server-confirmed-analytics-events"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/server-confirmed-analytics-events/",
      "title": "Measure completed actions separately from clicks"
    }
  ],
  "research_document_ids": [
    "a55ca2f24b54a9568edc97c065db4fce"
  ],
  "slug": "plausible-event-name-goal-matching",
  "source_signature": "a8076f1d269f589cbff14c3069f32f7edf06e0f40903a2fa79f930c3c289a7b9",
  "sources": [
    {
      "hash": "4a8b29279566febeddcc182cb2a3f1faf3f8b6fe4cfe052dab7987c1eaf95e74",
      "locator": "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",
      "observed_at": "2026-11-02T12:15:09.077556+00:00",
      "title": "Custom event tracking",
      "url": "https://plausible.io/docs/custom-event-goals"
    }
  ],
  "sources_required": [],
  "steps": [
    "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."
  ],
  "title": "Plausible custom events: fix a received event with no goal count",
  "worked_example": "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."
}