Skip to content
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.

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

Swetrix should analyze search terms #144

Open
joepio opened this issue Sep 28, 2023 · 6 comments
Open

Swetrix should analyze search terms #144

joepio opened this issue Sep 28, 2023 · 6 comments
Assignees

Comments

@joepio
Copy link
Member

joepio commented Sep 28, 2023

Currently only the first page open is counted. Should check out the swetrix SDK

@joepio
Copy link
Member Author

joepio commented Oct 17, 2023

can't see an option to do this, I asked the swetrix team (see above)

joepio added a commit that referenced this issue Oct 18, 2023
@joepio
Copy link
Member Author

joepio commented Oct 18, 2023

They fixed it in 2.4.0

@joepio
Copy link
Member Author

joepio commented Oct 18, 2023

We now have full search queries but bad UX

Image

@joepio
Copy link
Member Author

joepio commented Oct 18, 2023

Swetrix can also log other events, like so:

swetrix.track({ ev: 'SEARCH', meta: { url: window.location } })

I'm not quite sure whether this means I should just create regular JS events and name these "SEARCH" or whether I should call .track every time it happens?

@Blaumaus
Copy link

Blaumaus commented Oct 18, 2023

We now have full search queries but bad UX

Image

Hey, sorry for the UX, because we added the search params recently there was not really a need to decode the URL params before. We will fix this tomorrow so it won't be a problem on our side anymore.

EDIT: That issue has been fixed.

Swetrix can also log other events, like so:

swetrix.track({ ev: 'SEARCH', meta: { url: window.location } })

I'm not quite sure whether this means I should just create regular JS events and name these "SEARCH" or whether I should call .track every time it happens?

You call .track() each time you want to submit a custom event. A custom event can have some metadata appended to it which may be accessed in dashboard.
I.e. in the dashboard under 'Custom events' panel you will see a list of custom events (e.g. SEARCH, SIGNUP, etc.).

If you click on the expanding arrows button located on the top-right corner of that tab, a modal window with a list of events will open.
It looks like that: https://twitter.com/swetrix/status/1713023603409608781

In that window you will be able to see metadata per event, including the conversion of that specific metadata to a total number of unique visitors.

At the moment, we do not support (in other words - filtering) segmentation based on custom event metadata, but this is something that will be added this week.

So maybe for your specific use case it should be good to consider using metadata enriched custom events.

@joepio
Copy link
Member Author

joepio commented Oct 18, 2023

This is next level awesome customer support. You're actually reading my issues in my repo and building the feature I need? Whoa

joepio added a commit that referenced this issue Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants