Conditions

A more intuitive flow of building and understanding conditions
background
In the Site Tags application, conditions are used to trigger and control specific site tags for clients. These conditions are carefully constructed and applied to ensure tags function as intended, offering tailored solutions for each client.
What were solving for
Epsilon aims to enable the broader integration team to build and set conditions. Currently, only expert users can do this in the Site Tags application, largely because the features have been pieced together over the years. While functional, the result is a lack of intuitiveness and a poor user experience, making it difficult for non-experts to navigate.
Process
We began by meeting with engineers to understand the 'why' and 'how' of creating conditions for site tags. It quickly became evident that the process demanded extensive expertise to recall values and mapping options. We saw an opportunity to introduce a more guided, step-by-step flow that would not only simplify condition setup but also help associate engineers learn the process as they go.
  • Conditions were previously built exclusively by experienced engineers with deep knowledge of parameters and evaluations.
    ‍
  • Freeform inputs provided no guidance on available options, often resulting in errors during the save process.
    ‍
  • Existing conditions were difficult to interpret when editing a transformation or command created by another engineer.
solution
We developed a modal flow consisting of cards and dynamic inputs. As users configured conditions, they were presented only with options that aligned with their previous selections. I designed each step to prioritize common or frequently used values while allowing flexibility for customization. It was also essential that conditions be easily understandable on the transformation and command screens, so users could effortlessly review or adjust a condition when returning to edit or verify an event.
No items found.