Introduction to the Converge Source concepts
PageView
and Added To Cart
on the browser, but Placed Order
events on .
Placed Order
event in the example above).
However, profile properties are also useful for storing information across events within a single source.
Imagine a user that triggers a Subscribed to Newsletter
event with an $email
parameter. Afterward, that same user triggers an Added To Cart
.
Storing the $email
as a profile property ensures that you have this information available at the moment of the Added To Cart
event without you as a developer having to pass this information again.
Code Examples
eventID
parameter. This is especially important for events that are used as conversions.
Converge will deduplicate events with the same eventID
at ingestion time.
Code Examples
email
as an alias. Thus, Converge can merge a profile of browser events (e.g. Pageviews) with a profile with backend events (e.g. Started Subscription) if they have the same email
.
In the examples below we add an email
alias. Other aliases that are useful:
cart_token
checkout_token
: this is absolutely necessary if your checkout lives on a different domain than your storefront token.customer_id
Code Examples