Skip to content

fixes #699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
metmarkosaric merged 1 commit into from
Apr 22, 2026
Merged

fixes #699

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions docs/custom-props/for-custom-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -23,16 +21,14 @@ 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:

```js
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.
Expand All @@ -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.
Expand Down
8 changes: 0 additions & 8 deletions docs/custom-props/for-pageviews.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,14 +26,8 @@ plausible.init({

You're now tracking custom properties alongside pageviews.

<details>

<summary>

## Advanced: Dynamically setting custom properties

</summary>

To include dynamic data for custom properties, set `customProperties` to be a function. This function will be called for every event.

For example:
Expand All @@ -53,5 +47,3 @@ plausible.init({
}
})
```

</details>
Loading