# Configuration

## Configuration

Now that the basic onboarding is complete, let's review all fields in the form and how to use them. The API Key and REST Endpoint were already filled in during onboarding, so we will focus on the remaining options.

#### Event Prefix

A string that is prepended to every event name before it is sent to Braze.

For example, setting the prefix to `ET_` will send a `PageView` event as `ET_PageView` and a `Purchase` event as `ET_Purchase`.

Use this to distinguish EdgeTag-sourced events from events sent by other tools in your Braze account. Leave blank to send events with their original names.

#### Excluded Events

A comma-separated list of event names that should not be forwarded to Braze.

**Example value**

```
PageView,AddToCart
```

Spaces around event names are trimmed automatically. Use this to reduce event volume or to suppress events that are already handled by another channel.

#### How User Identity Works

Braze requires a stable identifier to associate events with a user profile. EdgeTag uses the visitor's **email address** as the `external_id` in every request to Braze.

Events are only forwarded when EdgeTag has an email address for the current visitor. If no email is present — for example, if the visitor has not yet logged in or submitted a form — the event is silently skipped.

{% hint style="warning" %}
Events for anonymous visitors are not sent to Braze. This is by design: sending events without a stable identifier would create orphaned profiles and risk duplicate email or SMS sends in your Braze campaigns.
{% endhint %}

#### Profile Attributes

When EdgeTag identifies a user, it syncs the following attributes to the corresponding Braze profile:

| EdgeTag field | Braze attribute | Notes                                         |
| ------------- | --------------- | --------------------------------------------- |
| `email`       | `email`         | Also used as `external_id`                    |
| `phone`       | `phone`         | E.164 format recommended, e.g. `+14155552671` |
| `firstName`   | `first_name`    |                                               |
| `lastName`    | `last_name`     |                                               |
| `gender`      | `gender`        | Mapped to Braze enum values (see below)       |
| `dateOfBirth` | `dob`           | Format: `YYYY-MM-DD`                          |
| `city`        | `home_city`     |                                               |
| `country`     | `country`       | ISO 3166-1 alpha-2, e.g. `US`                 |
| `timezone`    | `time_zone`     | IANA timezone, e.g. `America/New_York`        |

**Gender values accepted:**

| Input                               | Sent to Braze as |
| ----------------------------------- | ---------------- |
| `male`, `m`                         | `M`              |
| `female`, `f`                       | `F`              |
| `other`, `o`                        | `O`              |
| `not applicable`, `na`, `none`, `n` | `N`              |
| `prefer not to say`, `p`            | `P`              |

#### Event Properties

The following properties are automatically included with every event sent to Braze:

| Property     | Source                                |
| ------------ | ------------------------------------- |
| `page_url`   | URL of the page where the event fired |
| `page_title` | Title of the page                     |
| `value`      | Order or event value, e.g. cart total |
| `currency`   | ISO 4217 currency code, e.g. `USD`    |
| `order_id`   | Order identifier                      |
| `items`      | Array of cart or order line items     |

Any additional custom properties in the event payload are forwarded as-is.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edgetag.io/channels/braze/configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.