# Cofiguration

Now that your Segment integration is connected, let's explore the event handling capabilities available. EdgeTag automatically sends your events to Segment.

### Event Types <a href="#event-types" id="event-types"></a>

#### Identify Events

You can use the Identify event to link an anonymous Segment ID with an EdgeTag lifetime ID, enabling consistent user tracking across sessions and devices. This is particularly useful for maintaining user continuity when transitioning from anonymous to identified users.

Additionally, you can send other user data in the payload, such as traits like name, email, company information, or any custom user properties. These traits are passed directly to Segment. See [Segment docs](https://segment.com/docs/connections/spec/identify/#traits) for detailed information about which parameters and traits you can send.

{% code title="Example" %}

```json
{
  'age': 30,
  'title: 'CEO'
}
```

{% endcode %}

#### Page Events

When you send a PageView event through EdgeTag we will send event as page

### Other Events

Segment doesn't have predefined events, so please check their [adapters](https://segment.com/docs/connections/destinations/catalog/) for the expected payload.&#x20;

All EdgeTag events are automatically forwarded to Segment using the `track` method. Events maintain their original names and properties, ensuring consistency across your data pipeline. EdgeTag handles the formatting and API calls, so events appear in Segment exactly as they would from a native implementation


---

# 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/segment/cofiguration.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.
