---
title: Split email address
description: Split a full email address into local and domain parts.
category: Data Transformation
tags: [email, split, transformation, string, data cleaning]
---

# Split email address

## Description

The **Split Email Address** activity separates email addresses into two components:

- **Local part**: The portion before the `@` symbol (e.g., `john.doe`)
- **Domain part**: The portion after the `@` symbol (e.g., `example.com`)

This transformation is helpful when filtering, categorizing, or validating email data in bulk, enabling more targeted operations in workflows involving user data or email processing.

> **Use case**:  
> You have a list of user emails and need to group them by email domain for organization-level analysis or to validate domains before sending bulk emails.

## Input

| Type     | Description                                                          |
| -------- | -------------------------------------------------------------------- |
| **Data** | A dataset containing at least one column with valid email addresses. |

## Output

| Type     | Description                                                                    |
| -------- | ------------------------------------------------------------------------------ |
| **Data** | Transformed data with the original email and the new local and domain columns. |

## Configuration Fields

| Field Name             | Description                                                             |
| ---------------------- | ----------------------------------------------------------------------- |
| **Column Name**        | The column containing full email addresses to be split (e.g., `email`). |
| **Local Part Column**  | The name of the new column where the portion before `@` will be stored. |
| **Domain Part Column** | The name of the new column where the portion after `@` will be stored.  |

> Make sure all values in the selected column are in standard email format (e.g., `user@domain.com`).

## Sample Input

| id  | name        | email                   |
| --- | ----------- | ----------------------- |
| 1   | Alice Smith | alice.smith@example.com |
| 2   | Bob Brown   | bob.brown@sample.org    |
| 3   | Charlie Lee | charlie.lee@test.edu    |
| 4   | Daisy Adams | daisy.adams@company.com |

## Sample Configuration

| Field              | Value       |
| ------------------ | ----------- |
| Column Name        | email       |
| Local Part Column  | local_part  |
| Domain Part Column | domain_part |

## Sample Output

| id  | name        | email                   | local_part  | domain_part |
| --- | ----------- | ----------------------- | ----------- | ----------- |
| 1   | Alice Smith | alice.smith@example.com | alice.smith | example.com |
| 2   | Bob Brown   | bob.brown@sample.org    | bob.brown   | sample.org  |
| 3   | Charlie Lee | charlie.lee@test.edu    | charlie.lee | test.edu    |
| 4   | Daisy Adams | daisy.adams@company.com | daisy.adams | company.com |

> This transformation simplifies downstream tasks like sorting emails by company domain, detecting invalid domains, or generating personalized email reports.
