/
Integrating Converge

Integrating Converge

Integrating Converge

Converge is an all-in-one marketing measurement platform for e-commerce. It helps you manage tracking and understand what drives your business. The platform has two main products:

  1. Destinations: Set up tracking once, and Converge forwards your data to ad platforms, analytics tools, email providers, and more. Everything is optimized automatically.

  2. Analytics: Blend your first-party tracking with performance data from your marketing tools. Build custom reports to see what's driving your business.

This guide walks you through integrating Converge with UltraCart's StoreFront for privacy-compliant tracking. It covers configuring the Privacy and Tracking settings, obtaining required tokens from Converge, and selecting the appropriate sales channel type.

Prerequisites

  • An active UltraCart account with StoreFront access.

  • A Converge account. Sign up at runconverge.com if you don't have one.

  • Administrative access to your Converge dashboard to create sources and generate tokens.

Note: This integration enables both client-side (pixel-based) and server-side (webhook) tracking. Ensure your StoreFront complies with relevant privacy regulations, such as GDPR or CCPA, when enabling tracking.

Step-by-Step Instructions

image-20251110-162018.png

 

Step 1: Obtain Your Converge Tokens

To configure tracking in UltraCart, you'll need a Public Token (for client-side pixel tracking) and a Webhook Token (for server-side event forwarding). Follow these steps in your Converge dashboard:

  1. Log in to Converge at app.runconverge.com.

  2. Click Create a new source in the dashboard.

  3. For client-side tracking (Public Token):

    • Select Client as the source type.

    • Enter a name for your source (e.g., "UltraCart StoreFront").

    • Click Create Source.

    • In the source details, copy the Public Token (a 6-character alphanumeric code, e.g., AYU51m) from the HTML snippet provided. This token is used in the pixel script: https://static.runconverge.com/pixels/{YOUR_PUBLIC_TOKEN}.js.

  4. For server-side tracking (Webhook Token):

    • Click Create a new source again.

    • Select Server-side as the source type.

    • Enter a name (e.g., "UltraCart Webhook").

    • Click Create Source.

    • In the source configuration tab, copy the Webhook Token (a secure key for authenticating requests). You'll also note the webhook endpoint URL (e.g., https://app.runconverge.com/api/webhooks), though UltraCart handles sending events to this endpoint automatically once configured.

Tip: Store these tokens securely. The Public Token can be shared publicly for script inclusion, but treat the Webhook Token as sensitive.

Step 2: Determine Your Sales Channel Type

The Sales Channel Type categorizes events for accurate attribution in Converge (e.g., distinguishing web vs. in-store sales). It helps ensure insights reflect the true context of your tracking data without affecting event deduplication.

For a standard UltraCart StoreFront integration, select web unless your setup involves other channels.

Warning: Using the correct sales channel type maintains accurate stitching rates between client- and server-side events. Mismatched types can lead to incomplete attribution.

Step 3: Configure Converge in UltraCart

image-20251110-162538.png

  1. Log in to your UltraCart account.

  2. Navigate to Main Menu > StoreFronts > (Your StoreFront Menu) > Privacy and Tracking > Other tab.

  3. Scroll to the Converge section.

  4. Fill in the configuration fields:

    • Webhook Token: Paste the server-side Webhook Token from Step 1.

    • Public Token: Paste the client-side Public Token from Step 1.

    • Sales Channel Type: Select or enter your chosen type (e.g., web).

  5. Click Save to apply the changes.

 

Step 4: Test the Integration

  1. In Converge, navigate to your new sources and check the Logs tab for incoming events.

  2. Place a test order on your UltraCart StoreFront.

  3. Verify that events (e.g., "View Content", "Add to Cart", "Placed Order") appear in Converge's logs with the correct sales channel type.

  4. If events are missing, ensure your Public Token is active and review any error messages in the Webhook Token logs.

Prerequisite: Enable test mode in Converge if available to avoid affecting live data during testing.

Expected Outcome

Once configured, UltraCart will automatically:

  • Load the Converge pixel on your StoreFront pages for client-side tracking.

  • Forward server-side events (e.g., purchases) via webhook to Converge for blended analytics.

You should see real-time data flowing into your Converge dashboard, enabling custom reports and optimized ad performance.

Troubleshooting

  • Events not appearing: Confirm tokens are copied correctly (no extra spaces). Check Converge logs for authentication errors.

  • Stitching issues: Ensure the sales channel type matches across client- and server-side events (default to web).

  • Privacy concerns: Review Converge's consent mode implementation at docs.runconverge.com/guides/implementing-consent-mode to integrate with your CMP.

If issues persist, contact UltraCart support or Converge's team via their dashboard.

Next Steps

  • Explore Converge's Analytics features to build your first report.

  • Set up destinations in Converge to sync data with tools like Google Analytics or Facebook Ads.