From 6fab0b58fd7695b5ec432fa20a20ea51332b8aa4 Mon Sep 17 00:00:00 2001 From: Marko Saric Date: Wed, 22 Apr 2026 15:20:28 +0200 Subject: [PATCH 1/2] fixes --- docs/custom-props/for-custom-events.md | 8 +------- docs/custom-props/for-pageviews.md | 8 -------- 2 files changed, 1 insertion(+), 15 deletions(-) diff --git a/docs/custom-props/for-custom-events.md b/docs/custom-props/for-custom-events.md index 4a6bb043..ffaca2d9 100644 --- a/docs/custom-props/for-custom-events.md +++ b/docs/custom-props/for-custom-events.md @@ -2,8 +2,6 @@ title: Attach custom properties to custom events --- -## Send custom properties with custom events - When you track a custom event, you can include property key-value pairs alongside it. This lets you capture additional context about the event, for example which pricing plan a visitor selected when clicking a sign-up button, or which content variation they were shown. ### Using HTML class attributes @@ -23,7 +21,7 @@ To represent a space in a property value, use a `+` sign. Space characters are n You can add up to 30 properties per event by separating each class with a space. -## Using the JavaScript method +### Using the JavaScript method If you're triggering events manually with JavaScript, pass properties as a second argument: @@ -31,8 +29,6 @@ If you're triggering events manually with JavaScript, pass properties as a secon plausible('Sign Up', {props: {plan: 'pro', variation: 'homepage-cta'}}) ``` ---- - ## Create property-filtered goals When you [create a goal from a custom event](goal-conversions.md) in your site settings, you can optionally attach up to three property constraints to that goal definition. @@ -44,8 +40,6 @@ This is distinct from simply sending properties with your events: - **Sending a property with an event** records raw data. You can filter and analyze it in the dashboard after the fact. - **Attaching a property to a goal** makes the property part of the goal's definition. The goal only counts when that specific property value is present. It becomes a discrete conversion metric, not a filtered view of existing data. ---- - ## Use property-filtered goals in funnels Funnels in Plausible are built from goals, not raw events. Each funnel step must map to a defined goal. diff --git a/docs/custom-props/for-pageviews.md b/docs/custom-props/for-pageviews.md index 878864e5..01b312f7 100644 --- a/docs/custom-props/for-pageviews.md +++ b/docs/custom-props/for-pageviews.md @@ -26,14 +26,8 @@ plausible.init({ You're now tracking custom properties alongside pageviews. -
- - - ## Advanced: Dynamically setting custom properties - - To include dynamic data for custom properties, set `customProperties` to be a function. This function will be called for every event. For example: @@ -53,5 +47,3 @@ plausible.init({ } }) ``` - -
From 2cd33a22b1a3d5052f7d5031d4cb32ea140f65fb Mon Sep 17 00:00:00 2001 From: Marko Saric Date: Wed, 22 Apr 2026 15:23:45 +0200 Subject: [PATCH 2/2] fix --- docs/compare-stats.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/compare-stats.md b/docs/compare-stats.md index 5ba15083..6030be24 100644 --- a/docs/compare-stats.md +++ b/docs/compare-stats.md @@ -24,9 +24,9 @@ You can also change the chart interval, [segment your audience](filters-segments - Choose your comparison option from the drop-down. -
-