Example 1: Browser and Server “Placed Order” Event
In this example, a “Placed Order” event is initiated on the browser with a corresponding “Placed Order” event being received from a server-side data source. We want concepts like deduplication and session stitching to be applicable and relevant here. By categorizing both as “web,” Converge can ensure that calculations and insights reflect a true picture of the setup without introducing irrelevant discrepancies from non-web sources where deduplication or stitching may not make sense.Example 2: Subscriptions
For this example, a “Started Subscription” event is captured on the browser, followed by a “Placed Order” event from the server side, indicating a successful subscription start. These events will be categorized as a “web” sales channel given the user web journey. However, thirty days later, the server sends Converge a “Placed Recurring Subscription Order.” This event is categorized as a “subscription_contract” sales channel because it’s an automated event rather than a user-initiated event. Since there are no corresponding browser interactions for the recurring subscription order, concepts like deduplication and session stitching aren’t applicable or necessary in this scenario. By using a different sales channel from “web,” it means such events aren’t mistakenly associated with user actions and ensure deduplication and session stitching rates remain accurate.Supported sales channels
We support a number of sales channel types:Name | Property Value | Description |
---|---|---|
Web | web | Events occurring via browser-based interactions and actions |
Subscriptions | subscription_contract | Automated events related to subscription renewals or contracts. |
SMS | sms | Events or interactions triggered via SMS/Text communication. |
Mobile App | mobile_app | User interactions occurring within mobile applications. |
POS | pos | Point of Sale transactions taking place in physical stores. |
Marketplace | marketplace | Sales and interactions through third-party marketplaces like Amazon. |
Offline | offline | Offline events such as amended orders, manual orders, or calls. |
Facebook Shop | facebook_shop | Purchases and interactions through the Facebook Shop channels. |
Pinterest Shop | pinterest_shop | Sales and activity through the Pinterest Shop channels. |
TikTok Shop | tiktok_shop | Orders and interactions made via the TikTok Shop channels. |
Implementation
Sales channels are introduced via an event’s event properties using the$sales_channel_type
property.
All events sent from the Converge pixel are categorized as a “web” sales channel type.
If an event is received by Converge from a server-side integration like Shopify, BigCommerce, Firmhouse, or WooCommerce, a mapping occurs.
Custom integrations like webhooks require manual instrumentation of the property.
By default, if
$sales_channel_type
isn’t passed (e.g., custom integration), or a mapping can’t be found (server integration), Converge defaults to “web”. Make sure that the
$sales_channel_type
is the same for the web events and server-side event you are using for stitching. If not, the stitching rate in the Data Quality report won’t be accurate.