Introduction to Sales Channels
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. |
$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, Woocommerce, a mapping occurs.
Custom integrations like webhooks require manual instrumentation of the property.
$sales_channel_type
is not passed (e.g. custom integration), or a mapping cannot be found (server integration), Converge defaults to “web” $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.