The Computational Democracy Project



  • Sometimes, the owner of a conversation has some existing linkage to the identity of their participants, ie., they are sending out an email campaign or people are participating behind a login wall where the conversation is embedded
  • A note: using xid assumes that the owner has the token, this is different from creating single use urls
  • xid works in the embedded case — ie., the owner has added the embed code to a page on their own web property
  • Once the conversation has been embedded on a third party webpage, that page can, however it likes, via JavaScript or via templating for instance, add the data attribute data-xid="test"
  • The xid value for each participant will be available on the participation record in the export
  • Example

    • A common workflow for using xid involves a table of demographic data available from a polling provider
    • Participants are sent an email and invited to participate
    • Then, when the participant clicks through the email to a custom url, custom JavaScript written by whoever is controlling the third party website on which polis is embedded grabs a token out of the url and adds it to the data-xid="someTokenFromTheURLBarThatIdentifiesTheUser"
  • Embed code parameter that allows login-less participation by known users
  • Usage: data-xid="guid" or data-xid="5647434556754623" or less anonymously and not recommended data-xid=""

The Computational Democracy Project

© 2021 The Computational Democracy Project, a 501c3 nonprofit.


© 2021 The Computational Democracy Project, a 501c3 nonprofit.