Playbooks
Email one playtest's players
Segment on one roster’s tag and send to exactly those people.
Segment a campaign with player data
Narrow a tag further with playtest and Steam signals.
Which groups become tags
Every group in your studio, whatever created it, with two exceptions: the hidden roster that holds your whole directory, and the imported roster your audience fills. The first is everyone, so a tag for it would say nothing. The second is the audience itself.
A new group links itself on the next sync. You do not have to come back here after every playtest.
Reading the Tags table
Search by tag name, filter by status, and sort on the tag, the member count, or either date. Linked starts hidden and comes back from the Columns menu.
Each row’s overflow menu carries Pause syncing. Pausing leaves the tag in place on the contacts that already have it and stops Userplay touching it again. Resume syncing puts it back in the reconcile.
Renaming and removing a group
Both are handled for you, on the next reconcile.
Because a rename retires the old tag, a Mailchimp segment built on the old name stops matching. Point the segment at the new name after you rename something you have been segmenting on.
Tags coming back the other way
If your direction pulls, tagging a contact in Mailchimp can add them to the matching group in Userplay. That only works for custom groups. Playtest, survey, and waitlist rosters fill from the thing that owns them, and there is no sequence of tag edits in Mailchimp that should put someone on a playtest. Tagging a contact with one of those names changes nothing on this side.Related articles
Contact sync
The fields that travel alongside these tags.
Mailchimp integration
Connecting, pausing, and the way out.
Player groups
The rosters these tags mirror, and which ones you manage yourself.
Creating a group
Build a custom group, and get a tag with it.