Introduction to Aliases
checkout_token
alias in both the browser-side Started Checkout event and the server-side Placed Order event. This enables Converge to recognize that both events belong to the same profile and session.
Aliases are primarily used to link server-side conversions with browser sessions, but they can also merge profiles across different websites, browsers, or devices.
In Converge JS, the customer’s browser session cookie is used as the default alias. Additionally, Converge provides a set of default aliases for its integrations.
Code Examples
urn:cart_token:123xyz
): can be used to stitch a checkout on a different domain with the storefront session; or to stitch a server-side purchase to a website session.urn:checkout_token:456abc
): can be used to stitch a checkout on a different domain with the storefront session; or to stitch a server-side purchase to a website session.urn:email:john.smith@apple.com
): can be used to stitch a server-side order to a checkout sessionurn:user_id:123456
): can be used to stitch server-side order to a website sessionPlaced Order
event is received in Converge, before the client-side event with the stitching alias has been received. As such a cart_token
you can pick up early in the journey is a much more reliable alias than an email
property you receive very late in the journey.Placed Order
to the corresponding website session.Placed Order
event.$first_name
is a clear profile property (it persists across events) yet it does not uniquely define this profile so it would not be a correct alias.
Set up a first-party server-side cookie
Pass the cookie as an alias in all of your client-side ConvergeJS calls