{"action":"closed","issue":{"url":"https://api.github.com/repos/seatgeek/sixpack/issues/161","labels_url":"https://api.github.com/repos/seatgeek/sixpack/issues/161/labels{/name}","comments_url":"https://api.github.com/repos/seatgeek/sixpack/issues/161/comments","events_url":"https://api.github.com/repos/seatgeek/sixpack/issues/161/events","html_url":"https://github.com/seatgeek/sixpack/issues/161","id":55758284,"number":161,"title":"Deterministic participation based on a custom parameter","user":{"login":"clarkbk","id":1349496,"avatar_url":"https://avatars.githubusercontent.com/u/1349496?v=3","gravatar_id":"","url":"https://api.github.com/users/clarkbk","html_url":"https://github.com/clarkbk","followers_url":"https://api.github.com/users/clarkbk/followers","following_url":"https://api.github.com/users/clarkbk/following{/other_user}","gists_url":"https://api.github.com/users/clarkbk/gists{/gist_id}","starred_url":"https://api.github.com/users/clarkbk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/clarkbk/subscriptions","organizations_url":"https://api.github.com/users/clarkbk/orgs","repos_url":"https://api.github.com/users/clarkbk/repos","events_url":"https://api.github.com/users/clarkbk/events{/privacy}","received_events_url":"https://api.github.com/users/clarkbk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-01-28T13:51:45Z","updated_at":"2015-01-29T14:58:30Z","closed_at":"2015-01-29T14:58:30Z","body":"**Disclaimer:** Might be a dumb idea, but here goes.  I'll start with my intended use case:\r\n\r\nI want to A/B test title tag formats for a particular page type, because SEO.  It isn't suitable to set up a Sixpack experiment that determines participation on a per-client level, because I will want to measure whether the title tag change effects SERP ranks and therefore traffic.  In order for that to be possible, I need a guarantee that Google & other crawlbots will all be getting the same variant of the page.\r\n\r\nWhat if a Sixpack experiment could be configured in a deterministic way based using an extra parameter, taken from the context of the experiment?  For example, I could include in the `/participate` call a custom parameter that contains the page ID (say, a performer ID, in SeatGeek's case).  Sixpack would do some participating magic and always return the same variant for the given page ID.  My experiment would now be consistent between pages (instead of between clients).\r\n\r\nIs this a bad/impossible/frivolous idea?"}}