**Behavioral Data Hub > Attributes**
**Behavioral Data Hub > Attributes > Add new attribute**.
2. In the **Source name** field, enter the name of the parameter as it is sent by the SDKs/API.
3. In the **Display name** field, enter a human-readable label for display in the Synerise portal.
4. Optionally, in the **Description** field, you can add an explanation about the purpose of this property.
5. From the **Type** dropdown list, select the format of the property value as sent by the SDKs/API.
6. If you don't want to display this attribute in the filters across the Synerise platform, disable **Show attribute**.
6. Confirm by clicking **Save**.
## Managing membership attributes
---
Membership attributes are created when the segmentation sharing process is initiated. The segmentation results are saved as membership attributes and are synchronized.
These attributes have a boolean value (true or false) indicating whether a profile belongs to a segmentation from the current workspace or other workspaces (if you use [Co-Brand Decisioning Layer](/docs/settings/workspace/multibrand-workspaces)).
The membership attributes will have predefined names, format:
- display name: `
**Behavioral Data Hub > Attributes**.
2. On the left panel, select **Membership attributes**.
### Changing display name and description
1. In **Display name**, you can provide a user-friendly name of the membership attribute.
This name will display in the [filters](/docs/analytics/i_profile-filter) in the Synerise platform.
2. In **Description**, you can provide a description for the membership attribute that explains the purpose of it to other workspace users.
### Changing membership attribute visibility
To display or hide this attribute in the [filters](/docs/analytics/i_profile-filter) in the Synerise platform, use the **Show attribute** toggle.
# Profile tags
Profile tags is a feature that lets you create and manage tags which can be assigned to profiles (who can be found in the **Behavioral Data Hub**). This feature will help you effectively organize and group profiles, enabling precise targeting of specific profile segments.
## Tag management
---
All profile tags you create are stored in **Behavioral Data Hub > Tags** in an alphabetical order. In this place, apart from creating new tags, you can also search for the tags, [edit](#editing-profile-tags) or [remove](#removing-profile-tags) them.
### Adding new profile tags
You can create tags in the following ways:
- On the interface of the Synerise platform:
- [On the list of profile tags](#on-the-profile-tag-list)
- [On the profile cards](#on-the-profile-cards)
- With the [Create a tag API method](https://hub.synerise.com/api-reference/asset-management#operation/createTagUsingPOST)
- When you create or update profiles with Imports or the API
#### On the profile tag list
1. Go to **Behavioral Data Hub > Tags > Add tag**.
**Result**: A pop-up appears.
2. In the **Tag name** field, enter the name of the tag you want to add.
All characters are allowed. The limit for the tag name is 20 characters.
3. Optionally, you can change the color of the tag label by clicking the color picker next to the **Tag name** field and selecting the color.
4. Confirm the settings by clicking **Create**.
**Result**: A tag appears on the list. It is available on the filter lists in Tags tab across the Synerise platform.
**Profiles**.
2. Open the card of any profile to whom you want to assign a tag.
3. On the left pane, under the personal information of a profile, in the **Tags** section, click **Add tag**.
**Result**: A text field and list of tags appear.
4. Enter the name of the tag.
**Result**: A dropdown list appears. If the tag doesn't exist yet, in the dropdown, you can also add the new tag directly from this place.
**Behavioral Data Hub > Tags**.
2. Next to the name of the tag you want to edit, click 
3. From the dropdown list, click **Edit**.
4. Click the color picker and select a new color.
5. Confirm the changes by clicking **Apply**.
### Removing profile tags
---
You can organize your tags by removing those which are unused.
1. Go to **Behavioral Data Hub > Tags**.
2. Next to name of the tag you want to edit, click
3. From the dropdown list, click **Delete**.
**Result**: A pop-up appears.
4. Confirm the action by clicking **OK**.
**Result**: A tag is deleted from the list of profile tags and removed from all profiles who were assigned with this tag.
## Assigning tags to profiles
---
You can assign tags to profiles:
- **Manually** - This option lets you assign a tag to individual profiles.
1. Go to **Behavioral Data Hub > Profiles**.
2. Open the card of any profile to whom you want to assign a tag.
3. On the left pane, under the personal information of a profile, in the **Tags** section, click **Add tag**.
**Result**: A text field and list of tags appear.
4. From the list, select the tag or [create a new one](#on-the-profile-cards).
- **Through the Automation Hub** - This option lets you create workflows which either mass-assign tags to profiles or assign tags to them based on specific conditions, for example, when a profile performs a particular action. Such workflows must contain the ["Update Profiles node"](/docs/automation/actions/change-attribute-node) which assigns a specific tag defined in the node configuration to a profile that goes through a workflow.
- When you create or update profiles with Imports or the API.
**Behavioral Data Hub > Expressions > New expression**.
2. To let other users know about the purpose of the expression, you can add a short description to it.
3. To select the type of expression you want to create, click the 
icon.
4. From the dropdown list, select **Attribute**. In practice it means that you can use this expression in different types of analyses (for example, aggregates, funnels, and more).
4. To start creating the formula of the expression, click the **Select** button.
5. You can choose one of four elements: customer, constant, dynamic key, or a [function](/docs/crm/expressions/functions-in-expressions).
6. To define the settings of the chosen element, click that element.
7. In case you choose a customer, from the **Choose attribute** dropdown, select the customer attribute you want to include in the formula.
8. In case you choose a constant, type a number or text.
**Behavioral Data Hub > Live Aggregates > Create aggregate**.
2. As the aggregate type, select **Profile**.
2. Enter the name of the aggregate.
4. By clicking the button next to **Analyze profiles by**, define the type of aggregate result. You can choose from:
| Function | Description | Profile aggregate | Event aggregate |
|---|---|:---:|:---:|
| **Exists** | Returns a boolean value informing you whether a chosen event occurred in the selected time range. | 
| |
| **Sum** | Returns the total value of an event parameter from all matching event occurrences. | | |
| **Min** | Returns the minimal value of an event parameter. | | |
| **Median** | Returns the value separating the higher half from the lower half. For example, if you examine the total value of purchases for a single profile, the aggregate returns the middle value of amounts spent. | | |
| **Quantile** | Returns the value dividing the ordered statistical population into equal parts. For example, selecting the `80` quantile shows the value above which 20% of results are higher and the rest are lower. | | |
| **Max** | Returns the maximal value of an event parameter. | | |
| **Average** | Returns the average value of an event parameter. | | |
| **Count** | Returns the number of event occurrences. | | |
| **Count Distinct** | Returns the number of unique occurrences of an event parameter. | | |
| **Last** | Returns the latest value of an event parameter. | | |
| **Last - Time Window** | Works the same as Last, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | 
| |
| **First** | Returns the first value of an event parameter. | | |
| **First - Time Window** | Works the same as First, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **First Multi** | Returns a list (of a size you define) of items. The list can include parameters from only the first event, or from the first event and subsequent events if the first one did not contain enough items. | | |
| **First Multi - Time Window** | Works the same as First Multi, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **Last Multi** | Returns a list (of a size you define) of items. The list can include parameters from only the last event, or from the last event and preceding events if the last one did not contain enough items. | | |
| **Last Multi - Time Window** | Works the same as Last Multi, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **Top** | Returns the most popular occurrence of an event parameter. | | |
| **Bottom** | Returns the rarest occurrence of an event parameter. | | |
| **Top Multi** | Returns a list (of a size you define) of items, showing the most popular occurrences of an event parameter. | | |
| **Bottom Multi** | Returns a list (of a size you define) of items, showing the least popular occurrences of an event parameter. | | |
5. From the **Choose event** dropdown list, select an event.
6. If you want to be more specific and analyze a particular aspect of the event click the **Where** button, to select [event parameters](/docs/analytics/i_events-parameter-value).
6. To determine the time range from which the data will be analyzed, click the calendar icon.
7. Optionally, if you want to show this aggregate on a customer card, switch the **Show in Profiles** option on. As an effect, you can check the results of the aggregate for a particular customer on a customer card.
**Behavioral Data Hub > Profiles**.
2. At the top of the list, click **Add new**.
3. From the dropdown list, select **Profile**.
You can save a profile without any data at this stage and add them directly on the profile card.
4. Optionally, you can fill in the following fields:
- email address,
- first name,
- last name
5. Optionally, you can add attributes (properties) to the profile you add:
1. Click **Add attribute**.
2. From the dropdown list, from the attributes available in your workspace, select the name of the attribute.
3. In the **Value** text field, enter the value of the attribute (for example, `New York` for the `City` attribute).
4. To add more attributes, click **Add attribute**.
### Defining attributes
In this part of the process, you can create attributes, however, you are not allowed to create [reserved parameters](/docs/assets/imports/importing-clients#reserved-parameters).
6. Optionally, you can define new attributes.
1. Click **New attribute**.
2. In the **Source name** field, enter the name of the attribute as sent by the SDKs/API.
3. In the **Display name** field, enter a human-readable label for display in the Synerise portal.
4. Optionally, in the **Description** field, you can add an explanation about the purpose of this attribute.
5. From the **Type** dropdown list, select the format of the attribute value as sent by the SDKs/API.
6. Confirm by clicking **Save**.
**Behavioral Data Hub Hub > Aggregates > Create aggregate**.
2. As the aggregate type, select **Event**.
2. Enter the name of the aggregate.
4. By clicking the button next to **Analyze events by**, define the function according to which events will be aggregated:
| Function | Description | Profile aggregate | Event aggregate |
|---|---|:---:|:---:|
| **Exists** | Returns a boolean value informing you whether a chosen event occurred in the selected time range. | | |
| **Sum** | Returns the total value of an event parameter from all matching event occurrences. | | |
| **Min** | Returns the minimal value of an event parameter. | | |
| **Median** | Returns the value separating the higher half from the lower half. For example, if you examine the total value of purchases for a single profile, the aggregate returns the middle value of amounts spent. | | |
| **Quantile** | Returns the value dividing the ordered statistical population into equal parts. For example, selecting the `80` quantile shows the value above which 20% of results are higher and the rest are lower. | | |
| **Max** | Returns the maximal value of an event parameter. | | |
| **Average** | Returns the average value of an event parameter. | | |
| **Count** | Returns the number of event occurrences. | | |
| **Count Distinct** | Returns the number of unique occurrences of an event parameter. | | |
| **Last** | Returns the latest value of an event parameter. | | |
| **Last - Time Window** | Works the same as Last, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **First** | Returns the first value of an event parameter. | | |
| **First - Time Window** | Works the same as First, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **First Multi** | Returns a list (of a size you define) of items. The list can include parameters from only the first event, or from the first event and subsequent events if the first one did not contain enough items. | | |
| **First Multi - Time Window** | Works the same as First Multi, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **Last Multi** | Returns a list (of a size you define) of items. The list can include parameters from only the last event, or from the last event and preceding events if the last one did not contain enough items. | | |
| **Last Multi - Time Window** | Works the same as Last Multi, with the addition of a time window that limits results to event occurrences within a defined period. The maximum time window is 5 years. | | |
| **Top** | Returns the most popular occurrence of an event parameter. | | |
| **Bottom** | Returns the rarest occurrence of an event parameter. | | |
| **Top Multi** | Returns a list (of a size you define) of items, showing the most popular occurrences of an event parameter. | | |
| **Bottom Multi** | Returns a list (of a size you define) of items, showing the least popular occurrences of an event parameter. | | |
5. From the **Choose event** dropdown list, select an event.
6. In the **Size** field, define the number of items to return.
7. For Time Window functions (for example, **First - Time Window**), in the **Time window** field, enter a numeric value and select the interval (**days**, **hours**, or **minutes**). The maximum allowed time window is 5 years.
8. If you want to be more specific and analyze a particular aspect of the event, click the **Where** button, to select [event parameters](/docs/analytics/i_events-parameter-value).
9. To exclude the event occurrence for which you are calculating this aggregate, enable **Ignore the most recent occurrence of the event**.
10. To determine the time range from which the data will be analyzed, click the calendar icon.
11. To complete the process, click the **Save** button.
# Editing profiles
Keeping your profile information up to date is crucial for precise targeting of your campaigns and for providing excellent customer service. On the Synerise platform, you can update profile data in the following ways:
- [editing a single profile](#editing-a-single-profile) on the profile card
- [batch editing](#batch-editing) either on the list of profiles by selecting the profiles on the list or performing a profile import
- [launching a workflow](#launch-workflow-updating-profiles) which updates profile information when specific conditions occur (for example, a profile submits a form or performs other activity).
## Editing a single profile
---
Go to the details of a profile by clicking them on the list of profiles in the **Behavioral Data Hub**.
This way, you can edit the following information:
- profile information (in the **Profile info** section) such as: first name, last name, city, province; except birthdate
- contact information (in the **Contact info** section) such as: telephone or email address
- other information (in the **Other** section) such as: anonymous_type (status of the profile, it defined whether they are recognized or anonymous), avatar_url (which is the avatar that displays in the upper left corner), sex (defined by the following values: `0`, `1`, or `2`)
- assign or remove [tags](/docs/crm/customer-tag)
- enable or disable marketing agreements for email, SMS, mobile push, and web push (in the **Subscriptions** section).
- [add manually event to the profile activity list](/docs/crm/adding-events-in-customer-cards)
- assign a profile to a company
Each change of an attribute generates a [`profile.updated` event](/docs/assets/events/event-reference/profiles#profileupdated) on the activity list on the profile card.
Custom profile attributes and birthdate can be updated by [batch edit](#batch-editing) or [submitting a form by a profile](/developers/web/tracking-form-data).
## Batch editing
---
By editing several or group of profiles at the same time, you can conveniently perform the same change or set of changes for a large amount of profiles, which saves your time. You can do it on the interface on the Synerise platform or through API.
The scope of changes covers information described in [editing a single profile](#editing-a-single-profile) and custom profile attributes and brithdate.
### On the profile list
---
**Behavioral Data Hub > Profiles**.
2. On the list of profiles, select the checkboxes next to the profiles which you want to edit.
**Result**: The **Edit** button appears.
3. Click the **Edit** button.
**Result**:
**Behavioral Data Hub > Profiles**.
2. At the top of the page, click **Recognized**.
**Behavioral Data Hub > Profiles**.
2. At the top of the page, click 
**Filter**.
**Result**:
**Behavioral Data Hub > Live Aggregates**.
2. On the list of aggregates, find the profile aggregate you want to check the preview of.
3. Click the aggregate.
4. Select the identifier of a customer for whom you want to see the results.
**Result**: You get the preview of the aggregate:
# Importing profiles
To learn how to import profiles to Synrise, see the [Importing profiles](/docs/assets/imports/importing-clients) article.
# Exporting profiles
You can export profiles (both recognized and anonymous) from the Behavioral Data Hub along with the data you collected about them to a file. You can choose from the following file formats:
- `CSV`
- `JSON`
- `JSONL`
### Scope of exported data
You can export profiles with the following information:
- ID of the profile (automatically added),
- [profile attributes](/docs/crm/customer-properties): value of the attributes you select for export or `true`/`false` values for the [tags](/docs/crm/customer-tag) selected for export,
- [aggregates](/docs/crm/aggregates/introduction-to-aggregates): result of the selected aggregates for every profile,
- [expressions](/docs/crm/expressions/introduction-to-expressions): result of the selected expressions for every profile,
- [segmentations](/docs/analytics/segmentations/introduction-to-segmentations): `true`/`false` values; true if a profile belongs to the segmentation, false if they don’t.
### Limits
There are some limits you must follow:
- You can export up to 10,000,000 profiles per a single export.
- The file containing profiles cannot exceed 5GB in size.
### Export methods
The export methods are divided in terms of export frequency:
- [**Single export**](#single-export) - This method is recommended if you want to perform a one-off export of profiles and upload a file to your device.
- [**Exports in Automation Hub**](#export-in-automation-hub) with a pre-designed, configurable workflow
- This method is designed for:
- one-off and cyclical exports which generate a file containing profiles and their data, which you can then download.
- individual and cyclical exports of the file with profile data to the following external resources:
- Your server (using SFTP or HTTPS protocols),
- Azure,
- Amazon S3,
- Google Cloud Storage.
- You need to configure these settings of the workflow:
- Define the export frequency.
- Choose the conditions profiles must meet to be included in the export.
- Define rules for transforming the file (if needed).
- Specify the export destination and its specifics.
## Prerequisites
---
Only for **Exports in Automation Hub**:
- If the exported data must follow specific requirements (for example, specific column names), create a [data trasnformation rule](/docs/automation/data-transformation-and-imports/creating-data-transformation).
- You must be assigned with a [user role](/docs/settings/identity-access-management/permissions) with the following [permissions](/docs/settings/identity-access-management/permissions#permissions):
- to preview the **Save File** node configuration: **Data export > Save file** - **Read**
- to run and resume workflows containing the **Save File** node: **Data export > Save file** - **Execute**
- to edit the **Save File** node configuration: **Data export > Save file** - **Edit**
## Single export
---
### Selected profiles
This method is recommended if you want to perform a one-off export of several profiles. The process involves selecting profiles from the list and filling out export configuration form (defining the name of the file to which profile data will be exported and the scope of profile data for export). The `CSV` file will be available for downloading in **Data Modeling Hub > Exports**.
1. Go to **Behavioral Data Hub > Profiles**.
2. To select a profile for export, on the list, next to the profile name, select a checkbox.
**Result**: The **Export selected** button appears.
3. Click **Export selected**.
**Result**: A pop-up appears.
**Behavioral Data Hub > Profiles**.
2. In the upper-right corner, click **Export**.
**Result**: A pop-up appears.
Click the Everyone tab. No further configuration is needed.
**Behavioral Data Hub > Profiles**.
2. In the upper-right corner, click **Export**.
**Result**: A pop-up appears.
**Data Modeling Hub > Export**.
2. On the list of exports, find your export.
3. Click the name of the export.
**Result**: A pop-up appears.
| | | |
| From: Has email, recognized | | | | 1 |
| From: Has custom ID, anonymous | | | | |
| From: Has custom ID, recognized | | | | |
1See [Special case - email conflict](#special-case---email-conflict)
### Special case - email conflict
**This can happen only when non-unique emails are disabled.**
If a profile A (is recognized, has email) is merged into a profile B (is recognized, has custom ID) that also has an email, the email from A is lost, because properties are not transferred from source profiles to the target profile.
**Exception**: If the update operation that caused the merge included the email from A as the identifier, the mail from A is retained. This is because the update operation is resumed after the merge, so the email from the update request (which is now treated as a regular update of B) is saved into the profile after the merge.
# Adding events in profiles
You can generate events manually directly in a profile. It's useful in situations when you want to change event parameters, but cannot do it in an automated way.
An example of use is correcting the loyalty points when a customer submits a complaint, products are returned, and there is a need to return to the amount of points before the purchase.
## Prerequisites
---
A tracking code implemented into the website.
**Behavioral Data Hub > Profiles**.
2. Find a target profile. To make it faster, you can use the search box.
3. Go to the profile by clicking its name.
4. At the bottom of the activity list, click the 
button.
5. From the dropdown list, select an event to add to the profile by ticking the checkbox next to the name of the event. The list contains all tracked events.
**Data Modeling Hub > Event List**.
**Decision Hub > Dashboards > Add dashboard**.
2. Click the 
icon on the dashboard.
3. Select from the list the aggregate you want to add.
## Adding a new aggregate
1. Go to **Decision Hub > Dashboards > Add dashboard**
2. Click the icon on the dashboard.
3. Select the option **Create new** at the bottom of the list.
4. Follow instructions in [Creating profile aggregates](/docs/crm/aggregates/creating-profile-aggregates).
# Creating event expressions
You can create an event expression to enrich its parameters while creating different types of analyses (for example, metrics, segmentations, funnels, and so on). This means that you can use the result of the event expression as a special parameter of an event in other types of analytics.
**Behavioral Data Hub > Expressions > New expression**.
2. To let other users know about the purpose of the expression, you can add a short description to it.
3. To select the type of expression you want to create, click the icon. From the dropdown list select **Event**.
4. From the **Choose event** dropdown, select an event.
5. To start creating the formula of the expression, click the **Select** button.
5. You can choose one of four elements: customer, constant, dynamic key, or a [function](/docs/crm/expressions/functions-in-expressions).
6. To define the settings of the chosen element, click that element.
- In case you choose a customer, select the customer attribute you want to include in the formula.
- In case you choose a constant, type the number or text (users can write a number in words, `nine` instead of `9`).
- In case you choose a dynamic key, type in the key name (the ID of the key, for example `orderID`) and its default value. The default value will be replaced with the target one indicated in, for example, the request for expression result (when you request the expression result through Synerise Analytics API).
10. Define the dependencies between the elements in the expression by selecting the mathematical operators.
11. To complete creating the expression, click **Save**.
## Example of use
---
**Goal**: To create a metric that counts liters of sold liquid products.
**Prerequisites**: Non-standard attributes for **bought product** event: `product quantity` and `product volume`. Instruction for adding event parameters available at the [link](/docs/assets/events/adding-event-parameters).
**Steps**:
1. Go to **Behavioral Data Hub > Expressions > New expression**.
2. Enter the name of the expression.
**Decision Hub > Metrics > New metric**.
2. Enter the name of the metric.
3. As a type, select **Simple metric**.
3. As the aggregator, set `Count`.
4. As the occurrence type, set `All`.
5. From the **Choose event** dropdown list, select `Bought product`.
6. Click 
button.
**Result**: The **Choose parameter** button appears.
7. Click the **Choose parameter** button.
**Result**: A pop-up appears.
8. On the pop-up, click the three-dot button.
**Result**: A dropdown shows.
9. From the dropdown, select **Expressions**.
10. In the list of expressions, find the event expression you have just created.
11. To select a specific time range, click the calendar icon. Confirm your choice with the **Apply** button.
12. To complete the process, click **Save**.
**Behavioral Data Hub > Expressions > New expression**.
2. Enter a name of the expression.
3. Optionally, you can let other users know about the purpose of the expression by writing a short description.
4. Define the kind of expression you are creating by selecting the **Events** option. To do so, click the button.
5. Select an event to analyze.
f(x) = exp(x) or ex
(where the argument x is written as an exponent).
Therefore, the Exp function returns the result of e to the power given in the brackets.
## Floor
---
This function rounds down the results of expressions (e.g. 4.99 will be rounded down to 4).
## IfNull
---
This function checks if a given value is null (empty or undefined). If it is, the function returns a specified alternative value; otherwise, it returns the original value. This is useful for handling missing or undefined data.
**Syntax**
**Behavioral Data Hub > Expressions**.
2. Click the chosen expression.
3. Make the changes to the expression.
- To save the changes as a draft, click the **Finish later** button.
- If you want to publish the changes, click the **Publish** button.
- If you want to go back to the previous version:
1. In the right upper corner, click the 
icon.
2. On the list of versions, find the one you want to restore.
3. Hover the mouse cursor over the version and click the icon.
4. From the dropdown list, click either the **Publish** (to restore the other version of the expression) or **Edit** (to make changes to other version of the expression) button.
**Behavioral Data Hub > Live Aggregates**.
2. Click the icon available on the aggregate you want to remove.
**Behavioral Data Hub > Expressions**.
2. On the list of expressions, find the expression you want to preview.
3. Click the expression.
4. To switch on the preview mode, click the **Preview analyze** button.
5. To choose a customer for whom you want to analyze the expression:
- Click the search engine.
- Enter the email address of a customer.
- Optionally, you can change the search attribute for a tag, city or phone number.
# Adding expressions to analytics dashboards
When you create an analytical dashboard, you can add all types of analytics to it.
## Adding existing expressions
1. Go to **Decision Hub > Dashboards > Add dashboard**.
2. Click the 
icon on the dashboard.
3. From the list, select the expression you want to add.
## Adding a new expression
1. Go to **Decision Hub > Dashboards > Add dashboard**.
2. Click the icon on the dashboard.
3. At the bottom of the list, Select the **Create new** option.
4. Follow the steps in the procedure described [here](/docs/crm/expressions/creating-expressions).
# Deleting profiles
Managing profiles in a workspace is crucial for keeping data accurate. You must also delete old or unnecessary profiles to maintain data hygiene and comply with regulations. This helps protect customer trust and loyalty.
You can delete profiles using the following methods:
- [On the profile list](#on-the-profile-list) - From the profile list, you can select the profile which you want to delete
- [Launching a workflow](#launching-a-workflow) - You can set up an automated process to delete profiles based on specific conditions, such as when a customer requests to delete their account.
- Through an API request - By making a request to the [Delete a profile](https://hub.synerise.com/api-reference/profile-management#tag/Profile-management/operation/DeleteAClient) endpoint.
**Behavioral Data Hub > Profiles**.
2. On the list of profiles, select the checkbox next to the name of the profile.
**Result**: The **Delete** button appears.
3. Click the **Delete** button.
**Result**: A pop-up appears.
## Launching a workflow
---
This method allows you to establish automated processes for deleting profiles, for example when they receive an event after a customer deletes their account on your website, or for groups of profiles that meet a filter.
In such case, you must [create a workflow](/docs/automation/creating-automation) that contains the [Delete Profile node](/docs/automation/actions/delete-profile).
# Loyalty point count expression
This expression can be used for [Promotions for selected items](/docs/ai-hub/promotions/creating-promotions). It allows you to check whether customers gathered enough loyalty points to use the promotion.
## Requirements
---
- Paste the tracking code to the website source.
If you want to create exactly the same expression as described in this article, you need to:
- Create an analysis that counts a daily number of transactions.
- Create an analysis that counts the sum of the product value.
- Create an analysis that checks whether the customer is blocked.
- Create an analysis that checks whether the customer is in a segmentation for the VIP customers.
- Create an analysis that counts the number of boosted products.
- Create an analysis that counts the value of boosted products.
**Behavioral Data Hub > Expressions**.
2. On the list of expressions, find the expression you want to remove.
icon on the right side and select the **Remove** option on the dropdown list.
# Expressions
Expressions allow you to create your own indicators based on mathematical formulas or calculations for both profiles and events and use them as custom attributes. Expressions for events work as event attributes while expressions for customers work as profile attributes.
## Business benefits
- Expressions are a great tool for building loyalty programs and scoring structures. Expressions for attributes will perform perfectly well in this role. Thanks to this, you can award points and bonuses to your profiles if they perform a specific action.
- Expressions are helpful with building custom profile attributes which values are calculated in real time.
## Example use cases
---
- [Earn and Burn - Exchange points for rewards](/use-cases/earn-burn)
- [Creating event parameters out of event expressions](/use-cases/multi-params-expression)
- [Calculating Customer Age from Birthdate Attribute](/use-cases/age-calculation)
## Contents