Skip to content

Commit c26e5e1

Browse files
Merge pull request #699 from plausible/prop-fixes
fixes
2 parents 9c3cc66 + 6fab0b5 commit c26e5e1

2 files changed

Lines changed: 1 addition & 15 deletions

File tree

docs/custom-props/for-custom-events.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: Attach custom properties to custom events
33
---
44

5-
## Send custom properties with custom events
6-
75
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.
86

97
### Using HTML class attributes
@@ -23,16 +21,14 @@ To represent a space in a property value, use a `+` sign. Space characters are n
2321

2422
You can add up to 30 properties per event by separating each class with a space.
2523

26-
## Using the JavaScript method
24+
### Using the JavaScript method
2725

2826
If you're triggering events manually with JavaScript, pass properties as a second argument:
2927

3028
```js
3129
plausible('Sign Up', {props: {plan: 'pro', variation: 'homepage-cta'}})
3230
```
3331

34-
---
35-
3632
## Create property-filtered goals
3733

3834
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:
4440
- **Sending a property with an event** records raw data. You can filter and analyze it in the dashboard after the fact.
4541
- **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.
4642

47-
---
48-
4943
## Use property-filtered goals in funnels
5044

5145
Funnels in Plausible are built from goals, not raw events. Each funnel step must map to a defined goal.

docs/custom-props/for-pageviews.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,8 @@ plausible.init({
2626

2727
You're now tracking custom properties alongside pageviews.
2828

29-
<details>
30-
31-
<summary>
32-
3329
## Advanced: Dynamically setting custom properties
3430

35-
</summary>
36-
3731
To include dynamic data for custom properties, set `customProperties` to be a function. This function will be called for every event.
3832

3933
For example:
@@ -53,5 +47,3 @@ plausible.init({
5347
}
5448
})
5549
```
56-
57-
</details>

0 commit comments

Comments
 (0)