You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While implementing event tracking and stripping out a lot of data from events today, I noticed I was getting 400 Bad Request errors when sending events like this:
I had assumed that only the website prop was required, as that is the only one marked as such in the Docs for the tracker function. It seems however, that the url prop is required as well, as adding that would make the server accept the request.
If that is the correct behaviour and the url prop is indeed needed to track events, it should be marked as required in the docs.
Thank you for keeping up the development of Umami.
Database
MySQL
Relevant log output
Which Umami version are you using? (if relevant)
v2.16.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered:
Describe the Bug
Hi there!
While implementing event tracking and stripping out a lot of data from events today, I noticed I was getting 400 Bad Request errors when sending events like this:
window.umami.track((props) => ({ name: 'My Event', website: props.website }));
I had assumed that only the
website
prop was required, as that is the only one marked as such in the Docs for the tracker function. It seems however, that theurl
prop is required as well, as adding that would make the server accept the request.If that is the correct behaviour and the
url
prop is indeed needed to track events, it should be marked as required in the docs.Thank you for keeping up the development of Umami.
Database
MySQL
Relevant log output
Which Umami version are you using? (if relevant)
v2.16.1
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: