Counting signups is not enough. The more interesting question is what made someone decide to sign up.
This pass connected auth completion back to the surfaces that prompted it: header, profile, saving, and provider contact. Those moments mean different things. A save prompt suggests collection intent. A contact form suggests much stronger adoption intent.
I wanted the analytics to preserve that context instead of flattening everything into "user signed up."
The design value here is strategic more than visual. Once the data is cleaner, we can tell whether auth gates are helping, hurting, or simply appearing in the wrong places.
It gives the team a better way to ask: where does Wags earn enough trust for someone to create an account?