Applies to Conducttr.

Registration is used here to mean how the audience identifies itself with a particular partition.

IMPORTANT NOTE: once a team has been created in a certain partition, all audience who join that team are automatically added to that partition too. The author does not need to use an additional Client Partition action.

If the audience belongs to a team in another partition then a new audience record is created in the new partition. Although in the real life that same person is now in two or more partitions, Conducttr will treat each record as a unique audience member. That is, the audience member could have 50 points in partition A and 10 points in partition B – this is because the Conducttr does not view these records as the same person.

With regards to audience merging (ie. Multiple records for the same person merged into a single record) this only happens within the same partition.

Depending on the nature of the project and the commercial model, authors have the following options:

Single sign-up widget - the audience must enter their partition name. Conducttr will check that partition exists and will add the audience to that partition. In this case, you the author will create the partition and give each client their partition name.

Multiple sign-up widgets - each widget is pre-coded with the client partition id. Hence each client must be given their own sign-up page or sign-up widget code for embedding at their site.

Single message trigger - the client name must be parsed from the incoming message and a Client Partition action using the parsed variable used to add the audience to the correct partition

Multiple message triggers - each client is given his own sign-up phrase which is used to trigger the correct trigger. A client partition action is then used with the partition determined by a pre-configured client ID

API trigger - the API will send the audience information and the client partition id. Or.. the API can send some other identifier which is used in a condition attached to the API trigger. The API trigger must use a Client Partition action.

The image below shows the Team sign-up widget. You can select a specific partition or ask the audience to enter it.

This image shows the similar settings for the Solo sign-up widget.