# How the platform works

Commanders Act is a cookieless platform that allows you to **collect, normalize/fix, enrich, check and send** in real time your first-party customer data.

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-69dea3ade8e261245f3ce3adf5397acf7bf32d28%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

Basically, the platform libraries/API ([Source](#source)) collects user actions ([Event](#event)) on your website/app/etc.\
These events are sent to the platform servers and are then (in this order) [fixed](https://doc.commandersact.com/features/data-quality/data-cleansing), [normalized](https://doc.commandersact.com/features/data-quality/event-specification), [enriched](https://doc.commandersact.com/features/enrichments), [checked](https://doc.commandersact.com/features/data-quality), filtered and translated in each tool ([Destination](#destinations)) format, so that they can be sent to your chosen destinations.

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-19507803033cce9c3421bca02f0b2402312daf71%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

Platform servers can also store events, users and custom data in the Commanders Act database ([Data store](#data-store)) and send this data to your storage system (by FTP, email, S3, ...), BI system, etc.\
The user storage is based on a realtime [identity resolution system](https://doc.commandersact.com/features/identity-resolution) that give you a cross-device single view of your users (profiles), allowing you to build segments and use audience-based destination.

## Event

An [event ](https://doc.commandersact.com/developers/tracking-and-integrations/tracking/about-events)represents an action made by a user on your website or application. To track that action, you send an event that contains the data and will be received by Commanders Act.

## Source

A [source ](https://doc.commandersact.com/features/sources)is an emitter of events. It can represents your website, your mobile app, a point of sale (POS) etc. Defining your sources allow you to easily manage and monitor where your events are coming from.\
See more on:

{% content-ref url="integrating-your-data" %}
[integrating-your-data](https://doc.commandersact.com/getting-started/integrating-your-data)
{% endcontent-ref %}

{% content-ref url="../features/sources/sources-catalog" %}
[sources-catalog](https://doc.commandersact.com/features/sources/sources-catalog)
{% endcontent-ref %}

## Destination

[Destinations ](https://doc.commandersact.com/features/destinations)are the partners/tools where you eventually want the collected data to go. Commanders Act provide a library of many destinations ready to be used, like GA4, Facebook CAPI or Google Enhanced Conversion.\
See our [destination catalog here](https://doc.commandersact.com/features/destinations/destinations-catalog).

## Data store

Data store is the name of Commanders Act BigData database. You can store here your events and your [imported data](https://doc.commandersact.com/integrating-your-data#imports) (product catalog, etc.)\
Storing data inside the Data store allows you then to [enrich ](https://doc.commandersact.com/features/enrichments/events-enrichment)your events by retrieving additional data in any storage universe. It also allows you to create user [segments](https://doc.commandersact.com/features/customers/segment) and to benefit from analysis and insights.

## Data layer

A data layer is a specification of your data for tracking customer interactions. This can include data from websites, mobile apps, connected devices, and offline sources. The data layer enables your third-party vendor solutions and serves as the basis for your data-focused initiatives.

{% content-ref url="<https://github.com/TagCommander/PlatformX/blob/master/getting-started/concepts/broken-reference/README.md>" %}
<https://github.com/TagCommander/PlatformX/blob/master/getting-started/concepts/broken-reference/README.md>
{% endcontent-ref %}


---

# 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://doc.commandersact.com/getting-started/concepts.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.