Next Commerce

Configuration

The SDK is configured via window.nextConfig before the SDK script loads, and via meta tags in your HTML <head>.

Replace your-api-key-here with your actual Campaign API key from the dashboard.

Include the SDK

Add the Campaign Cart SDK loader script to every page of your campaign, ideally in the head.

<!-- Campaign Cart SDK -->
<script src="https://cdn.jsdelivr.net/gh/NextCommerceCo/[email protected]/dist/loader.js" type="module"></script>

JavaScript Configuration

Minimal Setup

// Configure before SDK loads
window.dataLayer = window.dataLayer || [];
window.nextReady = window.nextReady || [];

window.nextConfig = {
  apiKey: "your-api-key-here"
};

Full Configuration Reference

window.nextConfig = {
  // Required: Your Campaign Cart API key
  apiKey: "your-api-key-here",

  // Currency behavior when country changes
  currencyBehavior: 'auto', // 'auto' | 'manual'

  // Required for purchase deduplication with the NEXT Storefront Meta App
  storeName: 'store-name',

  // Payment and checkout configuration
  paymentConfig: {
    expressCheckout: {
      enabled: true, // Enable/disable express checkout methods
      requireValidation: true, // Require form validation before express checkout (radio option only, not express buttons)
      requiredFields: ['email', 'fname', 'lname'], // Fields required for express checkout radio option
      methodOrder: ['paypal', 'apple_pay', 'google_pay'] // Display order of express payment method buttons
    }
  },

  // Address and country configuration
  addressConfig: {
    // defaultCountry: "US",              // Low-priority fallback, used only when the campaign country list is empty
    // showCountries: ["US", "CA", "GB"], // Deprecated — the campaign API provides countries; fallback only
    dontShowStates: ["AS", "GU", "PR", "VI"], // State codes to hide from dropdowns
    enableAutocomplete: true, // Use NEXT address autocomplete (leave googleMaps.apiKey empty)
  },

  // Google Maps integration (address autocomplete)
  // Leave apiKey empty to use NEXT autocomplete. Set a key to use Google Maps instead — it takes priority when non-empty.
  googleMaps: {
    apiKey: "",
    region: "US",
  },

  // Analytics providers
  analytics: {
    enabled: true,
    mode: 'auto', // 'auto' | 'manual' | 'disabled'
    providers: {
      // NEXT Campaign analytics (always enabled when analytics.enabled is true)
      nextCampaign: {
        enabled: true
      },
      gtm: {
        enabled: false,
        settings: {
          containerId: "GTM-XXXXXX",
          dataLayerName: "dataLayer"
        },
        // Optional: blockedEvents: ["PageView"]
      },
      facebook: {
        enabled: false,
        settings: {
          pixelId: "YOUR_PIXEL_ID"
        },
        // Optional: blockedEvents: ["PageView"]
      },
      rudderstack: {
        enabled: false,
        settings: {}, // RudderStack config is handled by its own SDK; this just enables the adapter
        // Optional: blockedEvents: ["PageView"]
      },
      custom: {
        enabled: false,
        settings: {
          endpoint: "https://your-analytics.com/track",
          apiKey: "your-api-key"
        }
      }
    }
  },

  // UTM parameter transfer (preserve tracking params across pages)
  utmTransfer: {
    enabled: true,
    applyToExternalLinks: false, // Add UTM params to external links
    debug: false, // Enable debug logging for UTM transfer
    // Optional: excludedDomains: ['example.com', 'test.org'],
    // Optional: paramsToCopy: ['utm_source', 'utm_medium', 'utm_campaign', 'utm_content', 'utm_term', 'gclid', 'fbclid']
  }
};

storeName is required for purchase deduplication when using the NEXT Storefront Meta App. Set it to your store identifier.

Meta Tag Configuration

Configure the SDK on a per-page basis using meta tags in your HTML <head>:

<!-- Campaign API Key: Optional override -->
<meta name="next-api-key" content="your-api-key-here">

<!-- Funnel Name -->
<meta name="next-funnel" content="Example Funnel">

<!-- Page Type: product, checkout, upsell, or receipt -->
<meta name="next-page-type" content="product">

<!-- Next URL: Redirect after order completion (checkout pages) -->
<meta name="next-success-url" content="/upsell">

<!-- Upsell URLs: For upsell pages -->
<meta name="next-upsell-accept-url" content="/receipt">
<meta name="next-upsell-decline-url" content="/receipt">

The upsell meta tags (next-page-type, next-upsell-accept-url, next-upsell-decline-url) are covered in depth on the Upsell Flow page. For the separate analytics meta tag family (next-analytics-*), see Analytics Meta Tags.


Currency Behavior

The currencyBehavior setting controls whether the SDK geo-detects the shopper's currency. Once a shopper sees a price in a specific currency, the SDK locks that currency into sessionStorage for the rest of the session, so the cart, upsells, and order confirmation all stay consistent even if geo-detection would return a different result on a later page.

ValueBehavior
'auto' (default)Geo-detect on first load if no URL parameter or stored currency is present, then lock for the session
'manual'Never auto-detect. Falls back to the campaign default unless ?currency= or a stored value is set

How the currency is chosen on first page load

SourcePriority
?currency=<code> URL parameter1 — highest
Previously stored session currency2
Result of geo-detection (when currencyBehavior: 'auto')3
Campaign default currency4 — fallback

Once chosen, the value is written to sessionStorage and reused on every subsequent page load in the session. To reset, close the browser tab or clear sessionStorage.

To force a specific currency from a link (e.g. for currency-specific ad campaigns), use the ?currency= URL parameter.

On this page