Announcing the open collection of Adobe Analytics best practices

Imagine a situation like this: You are facing a new challenge when using or implementing Adobe Analytics. What do you do? If you are like me, you first check out the documentation to make sure you’ve understood the available features correctly. Then, you start researching blog posts and articles around your topic to see if and how anyone has solved this before. If you are still unsure, you might ask some people on Twitter, LinkedIn, or the Measure Chat. As a last resort, you might even reach out to Client Care and ask for help.

It’s easy to see why this approach is not ideal. First, it’s not easy to know if the way you approach a task is still the best way or if new solutions exist. Depending on which pages you found when researching, you might end up with an outdated solution or contradicting approaches by different authors (just think of my post about Props and what Jan Exner would tell you about that). On top of that, it’s not easy to find the best source again in the future, since blogs and posts can be moved, renamed, or deleted. A common semi-solution is to keep a list of blogs, help pages, or Twitter threads for future reference, but it doesn’t protect against all those issues. So, what can we do?

Community to the rescue!

I always really like the idea of creating awesome things as a community and being open to contributions. This is why I created the Open Adobe Analytics Components Repository on Github last year, where I publish all the Calculated Metrics and Segments from my posts. And now I have created another public repository, but this time with a much broader focus: I want to aggregate as many of my own best practices around Adobe Analytics as I can, and get as many people as possible to contribute their own experiences.

While creating this new project on Github allows everyone to contribute and discuss ideas, I wanted to make it as simple as possible to find the content and read through it. Luckily, Github can do this as well by enabling Github Pages on a repository. So while you would go to for casually reading the SEO-friendly content, you could visit for the raw repository and discussion around the content.

Please, feel invited to create new content and issue a pull request for your branch. But even if you don’t want to put your own best practice in, you can still contribute in a lot of different ways:

  • Start a discussion around an existing page
  • Request a certain topic to be included
  • Bring other people in and ask for their opinion
  • Ask the author of your favorite blog to submit their experiences with a topic
  • Add further details or screenshots to existing pages
  • If there are pages that could be more concise, consider rewriting them and propose a different wording
  • Check for spelling errors
  • If you are good at designing Github Pages, you can contribute a unique theme

So, why not head over to and take a look around? Is there anything you would like in there? Create an issue or start a discussion! Let’s make this awesome together. See you on Github!