Migration from the serverside v1 feature (platform 7 to platform X)
Severside v1 (aka SSv1) is the serverside tag management feature of the old platform (v7). It is now deprecated. In this section, we'll see how to migrate from a SSv1 setup to the new platform (aka SSv2)
Send data to serverside v2 (aka Platform X)
On the new platform (aka Platform X), everything is Source/Event/Destination. (your website, app or server) collect your user actions by sending . These events are sent to the platform servers and are then enriched, normalized and translated in each tool () format, so that they can be sent to your chosen destinations. You can learn more in the section.
From a server, use our .
Your data has to be sent to a , following a .
From a mobile application, you can either use one of our SDK (, , ...) or use our if you don't want to use a SDK.
Events are the new format of your data. As explain in the , common events have to be sent in the standard format (name and properties) to benefit from plug&play features.
Standard event format can be found in our
Go through this based on the ssv1 format :
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.cookie
parameter.
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