On the new platform (aka Platform X), everything is Source/Event/Destination. Sources (your website, app or server) collect your user actions by sending events. These events are sent to the platform servers and are then enriched, normalized and translated in each tool (Destination) format, so that they can be sent to your chosen destinations. You can learn more in the Concepts section.
From a server, use our HTTP tracking API.
Your data has to be sent to a new url, following a new format.
From a mobile application, you can either use one of our SDK (Android, IOS, ...) or use our HTTP tracking API if you don't want to use a SDK.
Events are the new format of your data. As explain in the event documentation, common events have to be sent in the standard format (name and properties) to benefit from plug&play features.
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.
Standard event format can be found in our event reference documentation
Go through this example, based on the ssv1 format : purchase event example
Here are an example of a serverside v1 hit : Booking Confirmation :
It should be sent to the serverside v2 in this format (adding maximum of recommanded properties) :
Other standard recommanded parameters should be added to the purchase event, following the purchase event documentation
Cookies should be sent through thedevice.cookieparameter.
For example, if you use Facebook CAPI, you'll have to send _fbp and _fbc cookies
RGPD: User consents have to be sent in each events, inside the user.consent_categories parameter