Hi everyone,I usually live in the analytics world, but I also manage our team’s Workfront space as the central hub for requests across Workspace, Data Collection, BI, and SQL. Because we sit alongside other project management systems, having one place for intake has been a big help, and I am here to...

I run into this a lot and curious to see how others handle it. Even when the numbers are accurate, stakeholders will often question funnel drop-offs or channel attribution. It feels less about the math and more about how much confidence people have in the way the data is configured and/or presented....

DescriptionThe Site Data Reference (SDR) is constantly evolving as new analytics needs come up. Right now, every change is handled manually — reviewing requests, mapping fields, and updating the schema one by one. It works, but it’s slow and makes it hard to keep different divisions aligned.Why is t...

Good call on stripping query strings and hashes — that does help reduce noise! Where we run into trouble is when those params hold the key info (article IDs, form IDs, campaign tags). Stakeholders still ask for URL-level reporting that shows them.I like the idea of replacing dynamic path elements wi...

Thanks for the perspective, as always. We’re usually dealing with a few million URLs in a month. On heavier traffic months, about 10–15% fall into Low Traffic. The main pain is stakeholder dashboards where people want the full URL list instead of just page names or roll-ups.We do use Data Warehouse ...

We’ve run into some of these same challenges. On the identity side, a lot of our stitching problems came from the web/CRM connection. We’ve got multiple Marketo instances and CRMs pushing into AEP, so duplicates were almost guaranteed. Tightening up ECID capture and making sure form IDs were consist...