Audience segmentation
cyndi@nickelled.com avatar
Written by cyndi@nickelled.com
Updated over a week ago

Nickelled lets you show different content based on your user's account details. There are two key components to setting up the user segmentation with Nickelled Flows:

1. Send the user attributes to Nickelled

As part of the installation you'll have installed our javascript snippet, which requires a unique user identifier.

However, inside the javascript snippet (for traditional websites), or via the NickelledLaunchers.setUser function (for single page applications), you can pass additional attributes and data to Nickelled.

Pass us any attributes by which you want to use to segment your users. For example, if you also wanted to set a userType, a jobRole, a 'paid' flag and an interaction count, you might modify the userData snippet as follows:

    NickelledLaunchers.userData = {
appId: 'APP-ID',
userId: 123,
userType: 'Admin',
jobRole: 'Marketing',
paid: true,
interactions: 50
};

Nickelled will process this information when it's received and we will store the attribute names that are sent (e.g. userType, jobRole, paid and interactions).

After we've received them these attributes will then be used for the next step, configuring the audience segmentation.

We do not store the associated values we receive โ€“ so we do not know personal information about your customer's accounts.

2. Configuring audience segmentation

Now that Nickelled has some user attributes from your application, you'll be able to configure when the flow should show.

If you don't want to segment the audience (since the flow should be shown to everyone) then you can leave this section blank.

Another thing to note is that the user will need to match all of the segmentation criteria. If you want "OR" logic then you can easily duplicate a flow and set the second segment for that flow.

The rules are simple but powerful and will allow you to show relevant flows for scenarios like:

  • Show this announcement to all unpaid users

  • Show explaining a feature but only when the user has the feature available

  • Show different onboarding material for Basic and Admin users

Did this answer your question?