GitLab Analyze:Product Analytics Team Meetings, 5 Jan 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: File-based funnel definitions

Description

Max (BE engineer) talks about pivoting to YAML-defined funnels for product analytics.

A

Hey folks, my name is Max wolf, I'm, a senior back-end engineer on the product, analytics team and I want to talk about what we're doing next, with funnel analysis and how we're going to start building it. So in the previous video I recorded just before, Christmas, which I'll link in the description I talked about how we can set it back to record objects to Define funnels and steps in those funnels, uh and then Sam RPM quite rightly pointed out.

A

Actually the best way to look at this would be similar to the way we're going to do dashboards, which is to Define them in yaml and make sure that they are subject to code review or any other checks or compliance requirements, um but for any other project within that organization would require so pivoted slightly now.

A

So, instead of using active record and building up new database tables, now we're going to be using yaml files instead, so I'll show my screen and let's work through that So within the dot, gitlab sort of meta project within a meta folder within a project and we've got our product analytics and then dashboards. As we've. Seen from previous demos, I've created a new uh directory called funnels, which will store all of our funnels for that project.

A

So it doesn't look very similar to the Json that we pass into Cube, essentially so name how long um or the maximum amount of time is between these steps that we can that we count as a conversion and then a definition of those steps.

A

um Each step should have a name just some sort of unique identifier to have a Target to the thing that that step requires. So, in the case of a page view, that page should be loaded uh we're only targeting pages right now, but we've designed this in such a way. That means that it can be expanded later so, for this completed purchase funnel to be converted within 3 600 seconds.

A

We should visit page one.html and we should visit page2.html and if we look oh sorry, wrong, I need to share my whole desktop, not just that I just took one there. We go um so in the API now similar to before uh for each of the yaml files. We load a different um funnel, and these two are almost identical, except in my test data. This one returns uh converted funnels and this one returns not um from there as well.

A

Nothing's changed from the the way we Define funnels, we're still using the dynamic, funnel schema that we looked at in the previous video.

A

This should now allow us to Define as many funnels from the project as we like. If there's code owner rules, compliance pipelines, CI steps have to be completed, then they'll, obviously all take effect as normal and we've done away with all the database stuff still hitting the same problem. I was hitting just before the Christmas break, which was that funnels with more than two steps that are currently work. That appears to be an issue with uh the SQL query itself, rather than anything more fundamental.

A

So that's what I'm working on today, um yeah thanks for watching.