Tracking first-party events is at the core of Converge. You can track any event you want, but in most cases Converge will automatically track key events like Viewed Product, Added to Cart, and Placed Order.
Client-side: Events are sent directly from the user’s browser to Converge. For example Viewed Product, Added to Cart, and Started Checkout are tracked by the Converge JS Pixel, added to your website directly or via an integration.
Server-side: Events are sent from your servers to Converge after users interact with your website. For example Placed Order or Cancelled Subscription are sent to Converge via integrations like Shopify, WooCommerce, or the Converge Webhook.
Converge groups all events into Profiles and Sessions:
Profiles: A profile is a long-term view of a user’s behavior. All events tied to a user are grouped here.
Sessions: A session represents a single visit to your site. Sessions are attributed to Channels or Ad Campaigns, helping you understand how users arrive on your website and what they do.
Marketing sources pull in metrics from platforms like Facebook Ads, Google Ads, and TikTok Ads. Once connected, Converge will sync metrics like Ad Spend, Impressions, Clicks, Conversions, Revenue, and metadata like Campaign, Ad Set, and Ad names.
Marketing source data is blended with first-party event data from your Event sources to create richer reports.For example, if you connect Google Ads, you can report on both Sessions and Purchases (from events) and Impressions, Ad Spend (from marketing data), and you can calculate metrics like a ROAS based on both.
Converge doesn’t alter the metrics it receives from your marketing sources. But your Destinations setup can influence how these platforms attribute results.