All Collections
Scenarios
Groups
How do I create a custom group?
How do I create a custom group?

Using your data to create tailor-made scenarios

Madeleine White avatar
Written by Madeleine White
Updated over a week ago

Poool Dashboard offers the possibility to use your own data in a simple way in order to use segments different from Poool's native segmentation (based on user engagement).

🚨 Custom group creation implies your technical team's intervention.

Create a custom group

To create a custom group, within your context, click on 'Create a group'.

A window opens to propose to create a group.
You can then define the 'Group name' ('Old subscriber in our example below) and 'Group slug' (old-subscriber in our example).

The name of the group is purely informative, while the slug (or custom group identifier) will serve you in the configuration.

💡 A slug is a normalization (without accent, space, capitalization or special character) of a set of words or a sentence.

For example "The Poool team is super nice" would become "the-poool-team-is-super-nice" 😉

Once validated, the group will appear in the list.

Trigger a custom group

The first prerequisite is to provide the data that will allow Poool to identify whether the user is part of the custom group or not. This information must be available in a variable. This can be anything: if a user is an old subscriber (as seen above), if they are registered, connected, a football fan ...

Once you have this information, you will need to integrate it with one condition:

📌 Script poool - previous version (poool Legacy)

if(mycondition is true){
poool("config", "custom_segment", "my-custom-segment-slug");
}

📌 Script poool - new version

if(mycondition is true){
access.config('custom_segment', 'test-segment');
audit.config('custom_segment', 'test-segment');
}

From this moment on, every time a user is part of this condition, they will no longer be put in the native segments but into the custom group that you have been created.

If you disable the custom group, users will be redistributed directly to the native engagement segmentation (volatile, occasional, regular, fans).

Contact us if you have any questions!

Did this answer your question?