[moritzmoritz21]

Hey everyone!

I worked the last weeks on a problem I wanted to solve and came up building this (so far) small tool.

In the backlog are quite a few features I want to add to it.

The idea behind moanalytics.com is to replace the well-known google sheet companies are using to organise their tracking events for a product. Tracking events always have some parameters which are written down in these sheets.

Additionally I am working as a software engineer and there is always a manual process to copy&paste the events from the sheet in the actual product. This is solved now since I added an export for the events.

Please try it out and I am happy about any feedback :)

[CaveTech]

Random Advice, but I'm in Ad Tech and build tracking and attribution platforms. I couldn't figure out what the product was supposed to be doing from the landing page. Reading your comment makes this more clear. I'd advise you to take another stab and the LP copy, and maybe put more practical examples (using real tags/event names for instance?) which make make it easier to understand at first look.

[shostack]

Any chance you can share what company you're at?

I've built these spreadsheets in a Marketing Operations capacity for my marketing teams and our engineering/product/data science counterparts that helped with implementation. I've also done this agency-side.

I can see some value here as a nice UI around it, particularly if there's various roles and permissions I can set for who does what. Also, props to OP for showing screenshots large enough to see what's actually going on in the product.

I'd echo your suggestion about actual events. These should probably be funnel-related events and not random product activity.

Another thing I'd like to see is some sort of version control and changelog/commit message functionality. Having access to the current events and their context is one thing. Having context around what changed and why is another layer of value that is critical for teams that may not be closely interacting on making these changes.

That's really getting into the workflow aspects which include things like notifications and alerts, as well as piping into analytics tools to monitor for things when an event stops reporting data (which may indicate something broke).

CaveTech, are you aware of any other tools on the market that try to productize this common use of spreadsheets like this?

[moritzmoritz21]

To dive in the questions ...

> Another thing I'd like to see is some sort of version control and changelog/commit message functionality. Having access to the current events and their context is one thing. Having context around what changed and why is another layer of value that is critical for teams that may not be closely interacting on making these changes.

versioning I am currently working on. So you are able to go back in history and see what events were tracked for each version.

> I'd echo your suggestion about actual events. These should probably be funnel-related events and not random product activity.

Can you give me an example here? :) I am an engineer and may not see the "other side" of the events.

[shostack]

It varies by setup. Just do a few Google Image Searches for funnel event tracking or read some tutorials on setting up Google Analytics conversion tracking events and you'll get a sense of the categories, actions, values, and labels people often use.

[moritzmoritz21]

Thanks! I added it to my list and see how this can be done :)

[moritzmoritz21]

Thanks for the feedback! Building the landing page was really one of the trickiest parts for me.

I will try to make the product more clear on the landing page :)

[shermozle]

You need to explain the problem you're solving first, not how the product works. Is it a product that collects events? Even with your explanation above, I still can't tell.

Use this for inspiration: https://imgur.com/a/TH8I5rs

[moritzmoritz21]

thanks for the feedback!

No the product is placed in the development flow before the implementation of the events. It is for organisation of the events you want to track.

[jldugger]

> The idea behind moanalytics.com is to replace the well-known google sheet companies are using to organise their tracking events for a product.

I... don't know what google sheet you are referring to. Google analytics?

[moritzmoritz21]

Well at least in my previous companies and the current one we always had one big excel/google/n sheet where all events were organised with their name e.g. "Profile loaded" and the associated parameters "user name", "user id".

And there were sometimes big discussions and unclear documentary about the events.

[jldugger]

So this is a schema tool for javascript events?

[moritzmoritz21]

I want to provide a platform where the tech team/product manager can organise all the events.

Where the tracking is tacking place is not determinate. It can be Amplitude, Google Analytics, Firebase, ..

So yeah you can somehow call it "schema tool" to build a template for your tracking.