You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that sixpack doesn't register more than one conversion for the same client_id.
What if I have 2 landing pages, and I want user A to see landing page number 1 and user B to see landing page number 2 ALWAYS. How can I track how many times the button was pressed for each user?
The text was updated successfully, but these errors were encountered:
I'm interested in this as well. Is supporting multiple conversions per user a planned feature on the roadmap? Seeing how the Redis backend is currently used with sets and sadd for recording conversions, it would potentially be a breaking change. Guessing would require something like either moving from Redis sets to hashes, or using hashes in addition to sets.
If there's interest, I'd be happy to help work on it. @josegonzalez are you the right person to ask about this?
Hello everyone,
It seems that sixpack doesn't register more than one conversion for the same client_id.
What if I have 2 landing pages, and I want user A to see landing page number 1 and user B to see landing page number 2 ALWAYS. How can I track how many times the button was pressed for each user?
The text was updated successfully, but these errors were encountered: