# Send data to serverside v2

## 1. New concepts

On the new platform (aka Platform X), everything is Source/Event/Destination.\
\
[Sources](#source) (your website, app or server) collect your user actions by sending [events](#event).\
These events are sent to the platform servers and are then enriched, normalized and translated in each tool ([Destination](#destinations)) format, so that they can be sent to your chosen destinations.\
\
You can learn more in the [Concepts ](https://doc.commandersact.com/getting-started/concepts)section.

## 2.How to send events (standard / custom)

* From a **server**, use our [HTTP tracking API](https://doc.commandersact.com/features/sources/sources-catalog/server/http-tracking-api).

{% hint style="info" %}
Your data has to be sent to a [new url](https://doc.commandersact.com/features/sources/sources-catalog/server/http-tracking-api#track), following a [new format](#3.-format-events).
{% endhint %}

* From a **mobile application**, you can either use one of our SDK ([Android](https://doc.commandersact.com/features/sources/sources-catalog/mobile-app/android), [IOS](https://doc.commandersact.com/features/sources/sources-catalog/mobile-app/ios), ...) or use our [HTTP tracking API](https://community.commandersact.com/platform-x/features/integrations/sources/sources-catalog/http-tracking-api) if you don't want to use a SDK.

## 3. Format events

* Events are the new format of your data. As explain in the [event documentation](https://doc.commandersact.com/developers/tracking-and-integrations/tracking/about-events), common events have to be sent in the **standard format** (name and properties) to benefit from plug\&play features.

{% hint style="info" %}
For specific events, **custom events** name is possible. Nevertheless, please use **standard properties** in custom events, as far as possible, to benefit from automatic mapping, automatic QA, and plug\&play features.
{% endhint %}

* Standard event format can be found in our [event reference documentation](https://community.commandersact.com/platform-x/developers/tracking/events-reference)
* Go through this [**example,** ](https://doc.commandersact.com/getting-started/integrating-your-data/migration-guides-to-the-platform-x/migrate-from-ssv1-to-ssv2/send-data-to-serverside-v2/purchase-event-example-ssv1-to-ssv2)**based on the ssv1 format** : [purchase event example](https://doc.commandersact.com/getting-started/integrating-your-data/migration-guides-to-the-platform-x/migrate-from-ssv1-to-ssv2/send-data-to-serverside-v2/purchase-event-example-ssv1-to-ssv2)
