Segmenting Options
Use your Contact List and contact information to target and filter contacts into Segments. Wooxy segmentation options are extensive, so you can choose a single condition or combine up to several conditions with positive and negative relations to target the right contacts for each Campaign. In this article, you’ll find all the available segmentation criteria.
Before we proceed, let’s take a moment to understand the concept of segmenting.
Segmenting refers to categorizing your subscribers into distinct groups based on specific criteria or characteristics.
Through variables, you can set up conditions for your Segment Group by using customer-specific information like geographic and demographic data, age, gender, behavior, preferences, purchase history, actions taken on your website, etc.
So, take the time to analyze your subscriber base, identify key segments, and develop tailored strategies to maximize the impact of your Campaigns.
Things to know before you start:
- To set the conditions in a Group, you can use only existing contact variables you have defined beforehand.
- There are two types of variables that can be used in the Contact List on the Wooxy platform: string variable (ENUM_STRING – variable value is text type. No specific format required) and date variable (ENUM_DATE – variable value is a date type. Required format ‘YYYY-MM-DD’).
- Segments are based on user data you provide to Wooxy via API, add manually, or by file import. In addition to data provided by customers, Wooxy collects behavioral user data which also can be used for segmentation.
- Within each group, you can create any number of conditions, but all conditions must be on the same level and all linked together using “AND” or “OR” operators.
- The number of conditions in a Group is unlimited.
- You can set as many Groups of conditions as you want.
- The changing of the And\Or operators can occur inside each Group separately, regardless of the external add-ons of Groups.
- Please note that you need to wait for the Segment to be recalculated. This is often related to the size of the Contact List or recalculation queues.
- If a Segment is not included in Automation, it is not updated automatically. You need to do it manually either on the segment lists page or within the Segment itself.
- If a Segment is included in Automation, the system will periodically recalculate the Segment. Also, before sending communication, the system will automatically recheck contacts for compliance with conditions and send the communication only to those contacts.
- The Segment does not display the exact number of contacts. Contacts can be added or removed from the Segment every second. The segment lists page shows the current number of contacts at the time of the Segment recalculation indicated there.
- If you have added new contacts to the Contact List or updated their values, you still need to manually recalculate the Segment. If the contacts meet the Segment conditions but do not appear in it, try adding one test contact and check its addition to the Segment. If it fails, please report it to us immediately – we will investigate.
- If a contact is not activated in the Contact List, then it will not be included in the Segment even if it meets all its conditions.
- IMPORTANT: Be careful with the communication sending via Campaigns based on scheduled, drafted, or paused launch types. The total recipient count of your Segment will not be finalized until your Campaign is sent.
Operators Glossary
When you create a Segment, you choose an “operator”, which is usually the second choice and is something like “equal” or “is not equal.” Different conditions display different operators for different types of variables. Here’s the list of the ones you might see:
String variable
| Operators Available | Action | Description/Expecting result |
| Equal | Type in the text | The contact’s data exactly matches the text you input. |
| Not equal | Type in the text | The contact’s data does not match the text you input. Any contacts that exactly match the text you entered will not be included in the Segment. |
| Greater than | Type in the text | The contact’s data is larger than the number or text you input. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Greater than or equal | Type in the text | The contact’s data is larger than or equal to the number or text you input. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Lower than | Type in the text | The contact’s data is smaller than the number or text you input. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Lower than or equal | Type in the text | The contact’s data is smaller than or equal to the number or text you input. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Contains | Type in the text | The contact’s data holds the text you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. |
| Not contains | Type in the text | The contact field data does not match the text you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. |
| Start with | Type in the text | The contact’s data starts with the text you input. |
| End with | Type in the text | The contact’s data ends with the text you input. |
| Is empty | N/A | The corresponding contact field is empty. |
| Is not empty | N/A | The corresponding contact field contains any value. |
Date variable
| Operators Available | Action | Description/Expecting result |
| Is current day | N/A | Only “MM-DD” data from the contact’s form field is compared. Year in this field data is ignored. |
| Today | N/A | The contact’s data must fully correspond to the date, including the year, month, and day (“YYYY-MM-DD”), which represents today’s date at the moment of the Segment recalculation. |
| Equal | Choose a date using the date picker | The corresponding contact field’s data exactly matches the date you pick. |
| Not equal | Choose a date using the date picker | The corresponding contact’s data doesn’t match the date you pick. Any contacts that exactly match the date you picked will not be included in the Segment. |
| Greater than | Choose a date using the date picker | The contact’s data is larger than the date you pick. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Greater than or equal | Choose a date using the date picker | The contact’s data is larger than or equal to the date you pick. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Lower than | Choose a date using the date picker | The contact’s data is smaller than the date you pick. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Lower than or equal | Choose a date using the date picker | The contact’s data is smaller than or equal to the date you pick. Filtering is based on lexicographic order, an arrangement of characters, words, or numbers in alphabetical order. It is similar to searching for a particular word in an actual dictionary. |
| Is empty | N/A | The corresponding contact field is empty. |
| Is not empty | N/A | The corresponding contact field contains any value. |
| Days before | Type in or select a number in the text field. | The contact’s date comes in the specified number of days you input. The operator considers the (YYYY-MM-DD) from the specified date variable value. |
| Days after | Type in or select a number in the text field. | The contact date passed the specified number of days you input. The operator considers the (YYYY-MM-DD) from the specified date variable value. |
| Days between | Type in or select two numbers in two text fields respectively. | The operator filters contacts based on an upcoming event date within a specified range. For example, if the event date is “15.08.24” and the range is set as 4 days before and 2 days after the event, the contacts will be included in the Segment from 11.08.24 to 17.08.24. The operator considers the (YYYY-MM-DD) from the specified date variable value. |
Variables
This group of filters contains custom global contact variables previously created in the corresponding section and custom Contact List’s variables that you created for a specific Contact List. The operators listed above can be used both for String format variables and for DateTime variables, respectively.
Contact fields
| Contact fields | Operators Available | Action | Description |
| Equal | Enter a value | The Segment will include contact with an email address specified in the condition. NOTE: There can be only one unique email address in one Сontact List. | |
| Not equal | Enter a value | The Segment includes contacts, whose email addresses don’t match the email address you input. The Segment will not include contact with the email address specified in the condition. NOTE: There can be only one unique email address in one Сontact List. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three email addresses: “acontact@example.com,” “contact@example.com,” and “user@example.com.” When arranged lexicographically, these addresses follow the sequence of “acontact@example.com,” “contact@example.com,” and “user@example.com.” Now, if you were to specify “contact@example.com” in the given field, the Segment will include not just the specified “contact@example.com” but also the subsequent “user@example.com.” This is because, in lexicographic order, the email address “user@example.com” appears after the specified email address. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three email addresses: “acontact@example.com,” “contact@example.com,” and “user@example.com.” When arranged lexicographically, these addresses follow the sequence of “acontact@example.com,” “contact@example.com,” and “user@example.com.” Now, if you were to specify “contact@example.com” in the given field, the Segment will include not just the specified “contact@example.com” but also the previous “acontact@example.com.” This is because, in lexicographic order, the email address “acontact@example.com” appears before the specified email address. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three email addresses: “acontact@example.com,” “contact@example.com,” and “user@example.com.” When arranged lexicographically, these addresses follow the sequence of “acontact@example.com,” “contact@example.com,” and “user@example.com.” Now, if you were to specify “contact@example.com” in the given field, the Segment will include the subsequent “user@example.com.” This is because, in lexicographic order, the email address “user@example.com” appears after the specified email address. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three email addresses: “acontact@example.com,” “contact@example.com,” and “user@example.com.” When arranged lexicographically, these addresses follow the sequence of “acontact@example.com,” “contact@example.com,” and “user@example.com.” Now, if you were to specify “contact@example.com” in the given field, the Segment will include the previous “acontact@example.com.” This is because, in lexicographic order, the email address “acontact@example.com” appears before the specified email address. | |
| Contains | Enter a value | The contact’s email address holds the text you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s email address field does not match the text you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| Start with | Enter a value | The contact’s email address starts with the text you input. | |
| End with | Enter a value | The contact’s email address ends with the text you input. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| name | Equal | Enter a value | The Segment will include contacts with names specified in the condition. |
| Not Equal | Enter a value | The Segment includes contacts, whose names don’t match the name you input. The Segment will not include contacts with names specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include not just the specified “David” but also the subsequent “Sarah.” This is because, in lexicographic order, the name “Sarah” appears after the specified name. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include not just the specified “David” but also the previous “Adam.” This is because, in lexicographic order, the name “Adam” appears before the specified name. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include the subsequent “Sarah.” This is because, in lexicographic order, the name “Sarah” appears after the specified name. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include the previous “Adam.” This is because, in lexicographic order, the name “Adam” appears before the specified name. | |
| Contains | Enter a value | The contact’s name holds the text you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s name field does not match the text you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| Start with | Enter a value | The contact’s name starts with the text you input. | |
| End with | Enter a value | The contact’s name ends with the text you input. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| firstName | Equal | Enter a value | The Segment will include contacts with the first name specified in the condition. |
| Not Equal | Enter a value | The Segment includes contacts, whose first names don’t match the first name you input. The Segment will not include contacts with the first names specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three first names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these first names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include not just the specified “David” but also the subsequent “Sarah.” This is because, in lexicographic order, the first name “Sarah” appears after the specified first name. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three first names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these first names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include not just the specified “David” but also the previous “Adam.” This is because, in lexicographic order, the first name “Adam” appears before the specified first name. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three first names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these first names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include the subsequent “Sarah.” This is because, in lexicographic order, the first name “Sarah” appears after the specified first name. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three first names: “Adam,” “David,” and “Sarah.” When arranged lexicographically, these first names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include the previous “Adam.” This is because, in lexicographic order, the first name “Adam” appears before the specified first name. | |
| Contains | Enter a value | The contact’s first name holds the text you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s first name field does not match the text you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| Start with | Enter a value | The contact’s first name starts with the text you input. | |
| End with | Enter a value | The contact’s first name ends with the text you input. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| lastName | Equal | Enter a value | The Segment will include contacts with last name specified in the condition. |
| Not Equal | Enter a value | The Segment includes contacts, whose last names don’t match the last name you input. The Segment will not include contacts with last names specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three last names: “Adams,” “Doe,” and “Smith.” When arranged lexicographically, these last names follow the sequence of “Adams,” “Doe,” and “Smith.” Now, if you were to specify “Doe” in the given field, the Segment will include not just the specified “Doe” but also the subsequent “Smith.” This is because, in lexicographic order, the last name “Smith” appears after the specified last name. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three last names: “Adams,” “Doe,” and “Smith.” When arranged lexicographically, these last names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include not just the specified “David” but also the previous “Adam.” This is because, in lexicographic order, the last name “Adam” appears before the specified last name. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three last names: “Adams,” “Doe,” and “Smith.” When arranged lexicographically, these last names follow the sequence of “Adams,” “Doe,” and “Smith.” Now, if you were to specify “Doe” in the given field, the Segment will include the subsequent “Smith.” This is because, in lexicographic order, the last name “Smith” appears after the specified last name. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three last names: “Adams,” “Doe,” and “Smith.” When arranged lexicographically, these last names follow the sequence of “Adam,” “David,” and “Sarah.” Now, if you were to specify “David” in the given field, the Segment will include the previous “Adam.” This is because, in lexicographic order, the last name “Adam” appears before the specified last name. | |
| Contains | Enter a value | The contact’s last name holds the text you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s last name field does not match the text you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| Start with | Enter a value | The contact’s last name starts with the text you input. | |
| End with | Enter a value | The contact’s last name ends with the text you input. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| phoneNumber | Equal | Enter a value | The Segment will include contact with a phone number specified in the condition. NOTE: There can be only one unique phone number in one Сontact List. |
| Not Equal | Enter a value | The Segment includes contacts, whose phone numbers don’t match the phone number you input. The Segment will not include contact with the phone number specified in the condition. NOTE: There can be only one unique phone number in one Сontact List. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Contains | Enter a value | The contact’s phone number holds the text or numbers you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s phone number field does not match the text or numbers you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| userId | Equal | Enter a value | The Segment will include contact with the user ID specified in the condition. NOTE: There can be only one unique userId in one Сontact List. |
| Not Equal | Enter a value | The Segment includes contacts, whose user IDs don’t match the userId you input. The Segment will not include contact with the userId specified in the condition. NOTE: There can be only one unique userId in one Сontact List. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three user IDs: “Contact1,” “Contact2,” and “Contact3.” When arranged lexicographically, these user IDs follow the sequence of “Contact1,” “Contact2,” and “Contact3.” Now, if you were to specify “Contact2” in the given field, the Segment will include not just the specified “Contact2” but also the subsequent “Contact3.” This is because, in lexicographic order, the userId “Contact3” appears after the specified userId. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three user IDs: “Contact1,” “Contact2,” and “Contact3.” When arranged lexicographically, these user IDs follow the sequence of “Contact1,” “Contact2,” and “Contact3.” Now, if you were to specify “Contact2” in the given field, the Segment will include not just the specified “Contact2” but also the previous “Contact1.” This is because, in lexicographic order, the userId “Contact1” appears before the specified userId. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three user IDs: “Contact1,” “Contact2,” and “Contact3.” When arranged lexicographically, these user IDs follow the sequence of “Contact1,” “Contact2,” and “Contact3.” Now, if you were to specify “Contact2” in the given field, the Segment will include the subsequent “Contact3.” This is because, in lexicographic order, the userId “Contact3” appears after the specified userId. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three user IDs: “Contact1,” “Contact2,” and “Contact3.” When arranged lexicographically, these user IDs follow the sequence of “Contact1,” “Contact2,” and “Contact3.” Now, if you were to specify “Contact2” in the given field, the Segment will include the previous “Contact1.” This is because, in lexicographic order, the userId “Contact1” appears before the specified userId. | |
| Contains | Enter a value | The contact’s userId holds the symbols you’ve entered. The Segment comprises contacts that align with the data you’ve entered. The data you provide may be a portion of the full contact information, but rest assured, contacts with matching fragments will also be included in the Segment. | |
| Not contains | Enter a value | The contact’s userId field does not match the symbols you input. The Segment includes contacts that do not correspond with the data you’ve entered. It’s important to note that even if the text you provide is only a fragment or a part of the full contact information, those contacts will still not be included in the Segment. | |
| Start with | Enter a value | The contact’s userId field starts with the text you input. | |
| End with | Enter a value | The contact’s userId field ends with the text you input. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| contactBirthday | Equal | Enter a value | The Segment will include contacts with birth date specified in the condition. |
| Not Equal | Enter a value | The Segment includes contacts, whose birth dates don’t match the date you input. The Segment will not include contacts with birth dates specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three birth dates: “1991-01-20,” “1995-02-20,” and “1999-03-20.” When arranged lexicographically, these dates follow the sequence of “1991-01-20,” “1995-02-20,” and “1999-03-20.” Now, if you were to specify “1995-02-20” in the given field, the Segment will include not just the specified “1995-02-20” but also the subsequent “1999-03-20.” This is because, in lexicographic order, the birth date “1999-03-20” appears after the specified date. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three birth dates: “1991-01-20,” “1995-02-20,” and “1999-03-20.” When arranged lexicographically, these dates follow the sequence of “1991-01-20,” “1995-02-20,” and “1999-03-20.” Now, if you were to specify “1995-02-20” in the given field, the Segment will include not just the specified “1995-02-20” but also the previous “1991-01-20.” This is because, in lexicographic order, the birth date “1991-01-20” appears before the specified date. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three birth dates: “1991-01-20,” “1995-02-20,” and “1999-03-20.” When arranged lexicographically, these dates follow the sequence of “1991-01-20,” “1995-02-20,” and “1999-03-20.” Now, if you were to specify “1995-02-20” in the given field, the Segment will include the subsequent “1999-03-20.” This is because, in lexicographic order, the birth date “1999-03-20” appears after the specified date. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three birth dates: “1991-01-20,” “1995-02-20,” and “1999-03-20.” When arranged lexicographically, these dates follow the sequence of “1991-01-20,” “1995-02-20,” and “1999-03-20.” Now, if you were to specify “1995-02-20” in the given field, the Segment will include the previous “1991-01-20.” This is because, in lexicographic order, the birth date “1991-01-20” appears before the specified date. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Is currentDay | N/A | This approach is specifically designed to focus on the day and the month only, excluding the year from the comparison process. In this procedure, the system only considers the “MM-DD” (month and day) data from the contactBirthday form field. | |
| Days before | Enter a value | The Segment includes contacts for an event that is coming up within a predetermined number of days. For instance, let’s consider today as March 5, 2024. If you set a condition in the Segment termed “2 days before the date,” it will filter out and include only those contacts whose dates in the specified variable align with this condition. The Segment will include the contacts whose birthdays in the variable fall on March 7, 2024. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Days after | Enter a value | The Segment includes contacts for an event that has passed. For instance, let’s consider creating a segment for March 5, 2024. If you set a condition in the Segment termed “2 days after the (event) date,” it will filter out and include only those contacts whose dates in the specified variable align with this condition. The Segment will include the contacts whose birthdays in the variable fell on March 3, 2024. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Days between | Enter a value | The operator filters contacts based on an upcoming event date within a specified range. For example, if the event date is “15.08.24” and the range is set as 4 days before and 2 days after the event, the contacts will be included in the Segment from 11.08.24 to 17.08.24. The operator considers a full date match (YYYY-MM-DD) from the selected variable value. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Today | N/A | The contact’s birthday must fully correspond (“YYYY-MM-DD”) to the date, which is today’s date at the moment of the Segment recalculation. | |
| avatarLink | Is empty | N/A | The corresponding contact’s field is empty. |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| createdAt | Equal | Enter a value | The Segment will include contacts with the creation date specified in the condition. |
| Not Equal | Enter a value | The Segment includes contacts, whose creation date doesn’t match the date you picked. The Segment will not include contacts with the creation date specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three creation dates: “2020-01-20,” “2023-02-20,” and “2024-03-20.” When arranged lexicographically, these dates follow the sequence of “2020-01-20,” “2023-02-20,” and “2024-03-20.” Now, if you were to specify “2023-02-20” in the given field, the Segment will include not just the specified “2023-02-20” but also the subsequent “2024-03-20.” This is because, in lexicographic order, the creation date “2024-03-20” appears after the specified date. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three creation dates: “2020-01-20,” “2023-02-20,” and “2024-03-20.” When arranged lexicographically, these dates follow the sequence of “2020-01-20,” “2023-02-20,” and “2024-03-20.” Now, if you were to specify “2023-02-20” in the given field, the Segment will include not just the specified “2023-02-20” but also the previous “2020-01-20.” This is because, in lexicographic order, the creation date “2020-01-20” appears before the specified date. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three creation dates: “2020-01-20,” “2023-02-20,” and “2024-03-20.” When arranged lexicographically, these dates follow the sequence of “2020-01-20,” “2023-02-20,” and “2024-03-20.” Now, if you were to specify “2023-02-20” in the given field, the Segment will include the subsequent “2024-03-20.” This is because, in lexicographic order, the creation date “2024-03-20” appears after the specified date. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three creation dates: “2020-01-20,” “2023-02-20,” and “2024-03-20.” When arranged lexicographically, these dates follow the sequence of “2020-01-20,” “2023-02-20,” and “2024-03-20.” Now, if you were to specify “2023-02-20” in the given field, the Segment will include the previous “2020-01-20.” This is because, in lexicographic order, the creation date “2020-01-20” appears before the specified date. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Is currentDay | N/A | This approach is specifically designed to focus on the day and the month only, excluding the year from the comparison process. In this procedure, the system only considers the “MM-DD” (month and day) data from the createdAt form field. | |
| Days before | Enter a value | The Segment includes contacts for an event that is coming up within a predetermined number of days. For instance, let’s consider today as March 5, 2024. If you set a condition in the Segment termed “2 days before the date,” it will filter out and include only those contacts whose dates in the specified variable align with this condition. The Segment will include the contacts whose creation dates in the variable fall on March 7, 2024. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Days after | Enter a value | The Segment includes contacts for an event that has passed. For instance, let’s consider creating a segment for March 5, 2024. If you set a condition in the Segment termed “2 days after the (event) date,” it will filter out and include only those contacts whose dates in the specified variable align with this condition. The Segment will include the contacts whose creation dates in the variable fell on March 3, 2024. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Days between | Enter a value | The operator filters contacts based on an upcoming event date within a specified range. For example, if the event date is “15.08.24” and the range is set as 4 days before and 2 days after the event, the contacts will be included in the Segment from 11.08.24 to 17.08.24. The operator considers a full date match (YYYY-MM-DD) from the selected variable value. NOTE: At the moment, the system considers “YYYY-MM-DD” (year, month, and day) data from the contact’s form field for comparison purposes. | |
| Today | N/A | The contact’s birthday must fully correspond (“YYYY-MM-DD”) to the date, which is today’s date at the moment of the Segment recalculation. |
Subscription
| Subscription | Operators available | Action | Channel | Description |
| channel | Subscribed | Select the channel | Filter subscribed contacts for the selected channel at the moment of Segment recalculation. You can select all channels but in this case, the Segment will include only those contacts who are subscribed to all selected channels. | |
| SMS | ||||
| Desktop Web Push | ||||
| Mobile Web Push | ||||
| Telegram | ||||
| Viber | ||||
| Unsubscribed | Select the channel | Filter unsubscribed contacts for the selected channel at the moment of Segment recalculation. You can select all channels but in this case, the Segment will include only those contacts who are unsubscribed to all selected channels. | ||
| SMS | ||||
| Desktop Web Push | ||||
| Mobile Web Push | ||||
| Telegram | ||||
| Viber |
Marketing
| Marketing | Operators available | Action | Description |
| source | Equal | Select one from the drop-down menu | Select the source that was previously registered in the Wooxy admin panel from the drop-down menu to filter the contacts associated with that source. |
| Not equal | Select one from the drop-down menu | Select the source that was previously registered in the Wooxy admin panel from the drop-down menu to filter the contacts that are not associated with that source. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| contactScore | Equal | Enter a value | The Segment will include contacts with the score specified in the condition. |
| Not equal | Enter a value | The Segment includes contacts, whose scores don’t match the number you input. The Segment will not include contacts with scores specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three scores: “10,” “50,” and “100.” When arranged lexicographically, these numbers follow the sequence of “10,” “50,” and “100.” Now, if you were to specify “50” in the given field, the Segment will include not just the specified “50” but also the subsequent “100.” This is because, in lexicographic order, the number “100” appears after the specified score. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three scores: “10,” “50,” and “100.” When arranged lexicographically, these numbers follow the sequence of “10,” “50,” and “100.” Now, if you were to specify “50” in the given field, the Segment will include not just the specified “50” but also the previous “10.” This is because, in lexicographic order, the number “10” appears before the specified score. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three scores: “10,” “50,” and “100.” When arranged lexicographically, these numbers follow the sequence of “10,” “50,” and “100.” Now, if you were to specify “50” in the given field, the Segment will include the subsequent “100.” This is because, in lexicographic order, the number “100” appears after the specified score. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three scores: “10,” “50,” and “100.” When arranged lexicographically, these numbers follow the sequence of “10,” “50,” and “100.” Now, if you were to specify “50” in the given field, the Segment will include the previous “10.” This is because, in lexicographic order, the number “10” appears before the specified score. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| cacValue | Equal | Enter a value | The Segment will include contacts with Customer Acquisition Value specified in the condition. |
| Not equal | Enter a value | The Segment includes contacts, whose Customer Acquisition Values don’t match the number you input. The Segment will not include contacts with Customer Acquisition Values specified in the condition. | |
| Greater than or equal | Enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three values: “0,55,” “1,” and “2.” When arranged lexicographically, these values follow the sequence of “0,55,” “1,” and “2.” Now, if you were to specify “1” in the given field, the Segment will include not just the specified “1” but also the subsequent “2.” This is because, in lexicographic order, the number “2” appears after the specified value. Thus, they are included in the filtered results. | |
| Lower than or equal | Enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three values: “0,55,” “1,” and “2.” When arranged lexicographically, these values follow the sequence of “0,55,” “1,” and “2.” Now, if you were to specify “1” in the given field, the Segment will include not just the specified “1” but also the previous “0,55.” This is because, in lexicographic order, the number “0,55” appears before the specified value. Thus, they are included in the filtered results. | |
| Greater than | Enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three values: “0,55,” “1,” and “2.” When arranged lexicographically, these values follow the sequence of “0,55,” “1,” and “2.” Now, if you were to specify “1” in the given field, the Segment will include the subsequent “2.” This is because, in lexicographic order, the number “2” appears after the specified value. | |
| Lower than | Enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three values: “0,55,” “1,” and “2.” When arranged lexicographically, these values follow the sequence of “0,55,” “1,” and “2.” Now, if you were to specify “1” in the given field, the Segment will include the previous “0,55.” This is because, in lexicographic order, the number “0,55” appears before the specified value. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. |
Demography
| Demography | Operators available | Action | Description |
| contactGender | Equal | Select a value | The Segment will include contacts with the gender specified in the condition. |
| Not equal | Select a value | The Segment includes contacts, whose genders don’t match the gender you input. The Segment will not include contacts with the gender specified in the condition. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
age (value is taken from the contactBirthday variable) | Equal | Select or enter a value | The Segment will include contacts with the age specified in the condition. |
| Not equal | Select or enter a value | The Segment includes contacts, whose ages don’t match the number you input. The Segment will not include contacts with the age specified in the condition. | |
| Greater than or equal | Select or enter a value | The contact field data is larger than or equal to the number or text you input. To better understand them, let’s consider three ages: “18,” “20,” and “30.” When arranged lexicographically, these numbers follow the sequence of “18,” “20,” and “30.” Now, if you were to specify “20” in the given field, the Segment will include not just the specified “20” but also the subsequent “30.” This is because, in lexicographic order, the number “30” appears after the specified age. Thus, they are included in the filtered results. | |
| Lower than or equal | Select or enter a value | The contact field data is lower than or equal to the number or text you input. To better understand them, let’s consider three ages: “18,” “20,” and “30.” When arranged lexicographically, these numbers follow the sequence of “18,” “20,” and “30.” Now, if you were to specify “20” in the given field, the Segment will include not just the specified “20” but also the previous “18.” This is because, in lexicographic order, the number “18” appears before the specified age. Thus, they are included in the filtered results. | |
| Greater than | Select or enter a value | The contact field data is larger than the number or text you input. To better understand them, let’s consider three ages: “18,” “20,” and “30.” When arranged lexicographically, these numbers follow the sequence of “18,” “20,” and “30.” Now, if you were to specify “20” in the given field, the Segment will include the subsequent “30.” This is because, in lexicographic order, the number “30” appears after the specified age. | |
| Lower than | Select or enter a value | The contact field data is lower than the number or text you input. To better understand them, let’s consider three ages: “18,” “20,” and “30.” When arranged lexicographically, these numbers follow the sequence of “18,” “20,” and “30.” Now, if you were to specify “20” in the given field, the Segment will include the previous “18.” This is because, in lexicographic order, the number “18” appears before the specified age. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| contactLanguage | Equal | Select a value | The Segment will include contacts with the language specified in the condition. |
| Not equal | Select a value | The Segment includes contacts, whose languages don’t match the number you input. The Segment will not include contacts with the language specified in the condition. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. |
Social networks
| Social networks | Operators available | Action | Description |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. | |
| tiktok | Is empty | N/A | The corresponding contact’s field is empty. |
| Is not empty | N/A | The corresponding contact’s field contains any value. |
Geography
| Geography | Operators available | Action | Description |
| timezone | Equal | Select a value | The Segment will include contacts with time zones specified in the condition. |
| Not equal | Select a value | The Segment includes contacts, whose time zones don’t match the time zone you pick. The Segment will not include contacts with time zones specified in the condition. | |
| Is empty | N/A | The corresponding contact’s field is empty. | |
| Is not empty | N/A | The corresponding contact’s field contains any value. |
Engagement
| Engagement | Channel | Parameters | Action | Description | |
Has Opened IMPORTANT: The contact will not be included in the Segment if the message was sent using any of the following methods:
| |||||
| Has Opened | Email, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts who have opened a specified Template. | |
| Campaign | Select Campaign | The Segment includes contacts who have opened a specified Campaign. | |||
| Any messages | Select period | Within the 1 day | The Segment comprises contacts who have opened at least one message from yesterday over a 24-hour span, extending to the current moment. | ||
| Within the 7 days | The Segment comprises contacts who have opened at least one message within the last 7 days, extending to the current moment. | ||||
| Within the 14 days | The Segment comprises contacts who have opened at least one message within the last 14 days, extending to the current moment. | ||||
| Within the 30 days | The Segment comprises contacts who have opened at least one message within the last 30 days, extending to the current moment. | ||||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes all contacts who have opened at least one of the last 5 Сampaigns sent on a specific channel. The contact would not be included in the Segment if fewer than 5 Campaigns were sent, even if they opened any Campaign. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts who have opened at least one Campaign within the last 7 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who have opened at least one Campaign within the last 14 days including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who have opened at least one Campaign within the last 30 days including the day the Segment is recalculated. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who have opened all of the last 5 Campaigns sent on a specific channel. | ||||
| Has not Opened | Email, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts who have not opened a specified Template. | |
| Campaign | Select Campaign | The Segment includes contacts who have not opened a specified Campaign. | |||
| Any messages | Select period | Within the 1 day | The Segment comprises contacts who received but have not opened any messages from yesterday over a 24-hour span, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after opening at least one message sent during the specified period. | ||
| Within the 7 days | The Segment comprises contacts who received but have not opened any messages within the last 7 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after opening at least one message sent during the specified period. | ||||
| Within the 14 days | The Segment comprises contacts who received but have not opened any messages within the last 14 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after opening at least one message sent during the specified period. | ||||
| Within the 30 days | The Segment comprises contacts who received but have not opened any messages within the last 30 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after opening at least one message sent during the specified period. | ||||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes contacts who have not opened at least one, few, or all of the last 5 received Campaigns sent on a specific channel. Even if a contact opens at least one of the last 5 Campaigns, they will still remain in this Segment because of the conditions specified. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts who have not opened at least one Campaign within the last 7 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they open all Campaigns sent on a specific channel during the specified period. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who have not opened at least one Campaign within the last 14 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they open all Campaigns sent on a specific channel during the specified period. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who have not opened at least one Campaign within the last 14 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they open all Campaigns sent on a specific channel during the specified period. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who have not opened all of the last 5 Campaigns sent on a specific channel. | ||||
| Has clicked on | Email, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts who have opened and clicked a specified Template. | |
| Campaign | Select Campaign | The Segment includes contacts who have opened and clicked a specified Campaign. | |||
| Any messages | Select period | Within the 1 day | The Segment comprises contacts who clicked at least one message from yesterday over a 24-hour span, extending to the current moment. | ||
| Within the 7 days | The Segment comprises contacts who have clicked at least one message within the last 7 days, extending to the current moment. | ||||
| Within the 14 days | The Segment comprises contacts who have clicked at least one message within the last 14 days, up to the current moment. | ||||
| Within the 30 days | The Segment comprises contacts who have clicked at least one message within the last 30 days, extending to the current moment. | ||||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes all contacts who have clicked at least one of the last 5 Сampaigns sent on a specific channel. The contact would not be included in the Segment if fewer than 5 Campaigns were sent, even if they opened any Campaign. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts who have clicked at least one Campaign within the last 7 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who have clicked at least one Campaign within the last 14 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who have clicked at least one Campaign within the last 30 days, including the day the Segment is recalculated. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who have clicked all of the last 5 Campaigns sent on a specific channel. | ||||
| Has not clicked on | Email, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts who have not clicked a specified Template. | |
| Campaign | Select Campaign | The Segment includes contacts who have not clicked a specified Campaign. | |||
| Any messages | Select period | Within the 1 day | The Segment comprises contacts who received but have not clicked any messages from yesterday over a 24-hour span, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after clicking at least one message sent during the specified period. | ||
| Within the 7 days | The Segment comprises contacts who received but have not clicked any messages within the last 7 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after clicking at least one message sent during the specified period. | ||||
| Within the 14 days | The Segment comprises contacts who received but have not clicked any messages within the last 14 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after clicking at least one message sent during the specified period. | ||||
| Within the 30 days | The Segment comprises contacts who received but have not clicked any messages within the last 30 days, extending to the current moment. It also includes contacts who haven’t received any messages due to a hard or soft status over the same timeframe. The contact will be excluded from the Segment after clicking at least one message sent during the specified period. | ||||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes contacts who have not clicked at least one, few, or all of the last 5 received Campaigns sent on a specific channel. Even if a contact clicks at least one of the last 5 Campaigns, they will still remain in this Segment because of the conditions specified. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts who have not clicked at least one Campaign within the last 7 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they click all Campaigns sent on a specific channel during the specified period. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who have not clicked at least one Campaign within the last 14 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they click all Campaigns sent on a specific channel during the specified period. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who have not clicked at least one Campaign within the last 30 days, including the day the Segment is recalculated. A contact will be excluded from the Segment if they click all Campaigns sent on a specific channel during the specified period. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who have not clicked all of the last 5 Campaigns were sent on a specific channel. | ||||
| Has been sent | Email, SMS, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts to whom the specified Template was sent. | |
| Campaign | Select Campaign | The Segment includes contacts to whom the specified Campaign was sent. | |||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes contacts to whom at least one of the last 5 Campaigns was sent on a specific channel. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts to whom at least one Campaign was sent within the last 7 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts to whom at least one Campaign was sent within the last 14 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts to whom at least one Campaign was sent within the last 30 days, including the day the Segment is recalculated. | ||||
| All of the last 5 Campaigns | The Segment includes contacts to whom all 5 most recent Campaigns were sent. | ||||
| Has not been sent | Email, SMS, Desktop WebPush, Mobile WebPush, Telegram, Viber | Template | Select Template | The Segment includes contacts to whom the specified Template wasn’t sent. | |
| Campaign | Select Campaign | The Segment includes contacts to whom the specified Campaign wasn’t sent. | |||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes all contacts to whom at least one of the last 5 Campaigns has not been sent on a specific channel. | ||
| Any Campaigns within the last 7 days | The Segment includes all contacts to whom at least one Campaign has not been sent within the last 7 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 14 days | The Segment includes all contacts to whom at least one Campaign has not been sent within the last 14 days, including the day the Segment is recalculated. | ||||
| Any Campaigns within the last 30 days | The Segment includes all contacts to whom at least one Campaign has not been sent within the last 30 days, including the day the Segment is recalculated. | ||||
| All of the last 5 Campaigns | The Segment includes contacts to whom all 5 most recent Campaigns weren’t sent. | ||||
| Dismissed WebPush | Desktop WebPush | Template | Select Template | The Segment includes contacts, who have received a specific Template but closed the Desktop WebPush notification that appeared in the browser. | |
| Campaign | Select Campaign | The Segment includes contacts, who have received a specific Campaign but closed the Desktop WebPush notification that appeared in the browser. | |||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes all contacts who closed at least one of the last 5 Campaigns messages sent on a Desktop WebPush channel. | ||
| Any Campaigns within the last 7 days | Segment includes contacts who received Push notifications within the last 7 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who received Push notifications within the last 14 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who received Push notifications within the last 30 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who closed all of the last 5 Campaigns messages sent on a Desktop WebPush channel. | ||||
| Mobile WebPush | Template | Select Template | The Segment includes contacts, who have received a specific Template but closed the Mobile WebPush notification that appeared in the browser. | ||
| Campaign | Select Campaign | The Segment includes contacts, who have received a specific Campaign but closed the Mobile WebPush notification that appeared in the browser. | |||
| Aggregated Campaigns | Select any kind of aggregated Campaigns | Any of the last 5 Campaigns | The Segment includes all contacts who closed at least one of the last 5 Campaigns messages sent on a Mobile WebPush channel. | ||
| Any Campaigns within the last 7 days | The Segment includes contacts who received Push notifications within the last 7 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| Any Campaigns within the last 14 days | The Segment includes contacts who received Push notifications within the last 14 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| Any Campaigns within the last 30 days | The Segment includes contacts who received Push notifications within the last 30 days, including the day the Segment is calculated, but closed at least one of them. | ||||
| All of the last 5 Campaigns | The Segment includes all contacts who closed all of the last 5 Campaigns messages sent on a Mobile WebPush channel. | ||||
| Last delivered | Email, SMS, Desktop WebPush, Mobile WebPush, Telegram, Viber | During 1 day (yesterday and today up to now) | N/A | The Segment includes contacts who received at least one message sent on a specific channel during the selected period of time. | |
| During 7 days | N/A | ||||
| During 14 days | N/A | ||||
| During 30 days | N/A | ||||
| Never | N/A | The Segment includes contacts who had never received any messages sent on a specific channel. | |||
| Total clicked (only unique clicks) | Email, SMS, Desktop WebPush, Mobile WebPush, Telegram, Viber | During 1 day (yesterday and today up to now) | Type message count | The Segment includes contacts who clicked on messages sent from a specific channel a determined number of times within the selected time period. | |
| During 7 days | Type message count | ||||
| During 14 days | Type message count | ||||
| During 30 days | Type message count | ||||
| Never | N/A | The Segment includes contacts who had never clicked on messages sent on a specific channel. | |||
| Total opened (only unique opens) | Email, Desktop WebPush, Mobile WebPush, Telegram, Viber | During 1 day (yesterday and today up to now) | Type message count | The Segment includes contacts who opened messages sent from a specific channel a determined number of times within the selected time period. | |
| During 7 days | Type message count | ||||
| During 14 days | Type message count | ||||
| During 30 days | Type message count | ||||
| Never | N/A | The Segment includes contacts who had never opened messages sent on a specific channel. | |||
| Total delivered | Email, SMS, Desktop WebPush, Mobile WebPush, Telegram, Viber | During 1 day (yesterday and today up to now) | Type message count | The Segment includes contacts who received messages sent from a specific channel a determined number of times within the selected time period. | |
| During 7 days | Type message count | ||||
| During 14 days | Type message count | ||||
| During 30 days | Type message count | ||||
| Never | N/A | Includes contacts to whom messages that were sent on a specific channel have never been delivered within the selected time period. | |||
Behavior
| Behavior | Events type | Event behavior | Action | Description |
| Events | Simple events | Event happened | N/A | An interaction between a user and your product. The Segment includes all contacts with whom the certain action has occurred. That action must be previously registered as an event in the Wooxy platform. |
| Event didn’t happen | N/A | An interaction between a user and your product. The Segment includes all contacts with whom the certain action has not occurred. That action must be previously registered as an event in the Wooxy platform. | ||
| Event happened multiple times | Type in or select the count | An interaction between a user and your product. The Segment includes all contacts with whom the certain action has occurred a specified number of times. That action must be previously registered as an event in the Wooxy platform. | ||
| Events with conversion | Event happened | N/A | An interaction between a user and your product. The Segment includes all contacts who have engaged in a specific action. This action is considered as a conversion for your company. It could be a variety of things, such as making a purchase, signing up for a newsletter, or downloading a whitepaper. That action must be previously registered as an event in the Wooxy platform. | |
| Event didn’t happen | N/A | An interaction between a user and your product. The Segment includes all contacts who have not engaged in a specific action. This action is considered as a conversion for your company. It could be a variety of things, such as making a purchase, signing up for a newsletter, or downloading a whitepaper. That action must be previously registered as an event in the Wooxy platform. | ||
| Event happened multiple times | Type in or select the count | An interaction between a user and your product. The Segment includes all contacts who have engaged in a specific action a specified number of times. This action is considered as a conversion for your company. It could be a variety of things, such as making a purchase, signing up for a newsletter, or downloading a whitepaper. That action must be previously registered as an event in the Wooxy platform. |
