> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/integrations/analytics/send-events-from-unreal.md).
# Send Events from Unreal
## Overview
{% hint style="info" %}
Before following this guide, we recommend downloading [this folder](https://github.com/msquared-io/msquared-mixpanel/tree/main/Mixpanel) from our Mixpanel repository, which contains pre-made assets that you can drop into your map to immediately start sending different test events.
{% endhint %}
In order to send events from your packaged editor, you should use the`/import` mixpanel ingestion api ([documentation found here](https://developer.mixpanel.com/reference/import-events)). The url is either:
* `https://api.mixpanel.com/import` , or:
* `https://api-eu.mixpanel.com/import`
depending on the location you selected for your data storage.
## Blueprint Implementation for Sending Mixpanel Events
A mixpanel event must contain 2 specific values: an **event name**, and a set of **properties:**
```
{
"event": "Signed up",
"properties": {
"time": 1618716477000,
"distinct_id": "91304156-cafc-4673-a237-623d1129c801",
"$insert_id": "29fc2962-6d9c-455d-95ad-95b84f09b9e4",
}
}
```
In properties, you must include:
* `time` (of when the event was sent)
* `distinct_id` (to identify unique users)
* `$insert_id`(a unique id for the event)
We have a number of helpful json nodes to help you construct this in blueprints. To get started:
1. Construct a Json object, and set the above values:
{% @blueprintue-embed/embed url="" %}
2. You can add additional properties alongside the required fields, which can contain important metadata that you might want to retrieve from a particular event:
{% @blueprintue-embed/embed url="" %}
3. To complete setting up the request body, create a new Json Object from a custom Mixpanel event struct (this will only contain a string member named event).
4. You can then set the properties field on this new json object, as shown below (note: the api body must be in the form of a json array as each request can accept up to 2000 different events):
{% @blueprintue-embed/embed url="" %}
5. Finally, set up the required authorization header. You should copy the previously stored basic auth value generated from your project token and use this in this step. Use the `Send Http Request` node to POST your request to the import api:
{% @blueprintue-embed/embed url="" %}
### Full Blueprint Example
{% @blueprintue-embed/embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.otherside.xyz/platform-documentation/integrations/analytics/send-events-from-unreal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.