Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runconverge.com/llms.txt

Use this file to discover all available pages before exploring further.

Sales channels categorize individual events based on their specific tracking context, such as browser, mobile application, or POS. This classification doesn’t impact how stitching or deduplication are performed but rather ensures that any insights and warnings are increasingly accurate and aligned with the nature of each event. By distinguishing these events through sales channel types, Converge can provide more precise insights into a healthy Converge setup and highlight any areas of concern.

​
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,” such events aren’t mistakenly associated with user actions, and deduplication and session stitching rates remain accurate.

​
Supported sales channels

We support a number of sales channel types:
NameProperty ValueDescription
WebwebEvents occurring via browser-based interactions and actions
Subscriptionssubscription_contractAutomated events related to subscription renewals or contracts.
SMSsmsEvents or interactions triggered via SMS/Text communication.
Mobile Appmobile_appUser interactions occurring within mobile applications.
POSposPoint of Sale transactions taking place in physical stores.
MarketplacemarketplaceSales and interactions through third-party marketplaces like Amazon.
OfflineofflineOffline events such as amended orders, manual orders, or calls.
Facebook Shopfacebook_shopPurchases and interactions through the Facebook Shop channels.
Pinterest Shoppinterest_shopSales and activity through the Pinterest Shop channels.
TikTok Shoptiktok_shopOrders 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. 
resp = requests.post(
    "{YOUR_POSTBACK_ENDPOINT}",
    json=
        {
        "event_name": "Placed Order",
        "event_id": "order-1", # your order id, necessary for deduplication
        "properties": {
            # event properties
            "$sales_channel_type": "web",  # important, see supported sales channels
        },
        "profile_properties": {
            # Pass as many as possible
            "$first_name": "John",
            "$last_name": "Smith",
            "$email": "john.smith@apple.com",
            "$phone_number": "+199999999",
            "$city": "San Francisco",
            "$country_code": "US",
            "$state": "California",
            "$zip_code": "94103",
        },
        # important, this will be used for stitching backend orders to website sessions
        "aliases": ["urn:email:john.smith@apple.com"],
    }
)