BigCommerce Order Attribution: Navigating API Limitations for Source, Landing, and Referring Site Data

Understanding the full customer journey, from initial touchpoint to conversion, is paramount for any e-commerce business. For BigCommerce merchants and developers, accessing granular order attribution data—such as the customer's source, landing page, and referring site—is crucial for optimizing marketing spend, personalizing experiences, and refining sales strategies. However, retrieving this specific data through native BigCommerce APIs presents a common challenge.

The Quest for Detailed Order Attribution Data

A recent query on the BigCommerce community forum highlighted this exact need. A user, Sawyer Irwin, sought to retrieve several key order attribution fields via API, including:

• sourceName: The sales channel or source of the order (e.g., "web").
• landingSite: The first URL visited by the customer before placing the order.
• referringSite: The external referrer (e.g., Google, Facebook).
• subscriptionParentOrChildOrder: An indicator for subscription order hierarchy.

Sawyer provided a clear JSON example of the desired data structure:

{
 "sourceName": "web",
 "landingSite": "https:///products/product1",
 "referringSite": "www.google.com",
 "subscriptionParentOrChildOrder": "child"
}

The core question revolved around whether these specific fields were available through any native BigCommerce API, or if custom tracking or third-party solutions would be necessary.

BigCommerce API Limitations and Native Solutions

The response from Tanner Brodhagen of Brod Solutions, a BigCommerce Partner, provided a clear answer: the BigCommerce Orders API, unfortunately, does not natively expose detailed visitor source, landing page, or referring site information. While the API does offer an order_source field, it typically provides a more general classification rather than the granular URLs and external referrers sought after.

For merchants relying solely on BigCommerce's built-in functionalities, the closest native access to this detailed data is through the Analytics - Marketing reports. However, this data is only available via CSV export, meaning it's not programmatically accessible through an API for real-time or automated integration purposes. This limitation can pose significant hurdles for businesses aiming to build custom dashboards, integrate with CRMs, or automate marketing attribution workflows.

Leveraging Third-Party Analytics for Comprehensive Attribution

Given the API gap, the recommended and most effective solution involves integrating third-party analytics platforms. These tools are specifically designed to monitor and capture extensive visitor journey data, which can then be matched to orders within BigCommerce. Tanner specifically mentioned:

• Google Analytics: A widely used platform offering deep insights into user behavior, traffic sources, and conversion paths.
• TripleWhale: An analytics platform often favored for its comprehensive e-commerce attribution modeling.
• Brod Analytics: Another specialized analytics solution capable of tracking and correlating visitor data with orders.

These platforms typically integrate with your BigCommerce store to track user sessions, identify referrers, record landing pages, and then link this data to specific orders once a purchase is made. While this requires an additional integration step, it provides the robust, granular attribution data that the native BigCommerce API currently lacks.

The Unanswered Question: Subscription Order Hierarchy

It's worth noting that while the discussion clarified the availability of source, landing, and referring site data, the specific field subscriptionParentOrChildOrder was not addressed in the reply. This suggests that for subscription-specific order hierarchy, merchants would likely need to rely on the API of their chosen subscription management app, as this functionality is typically managed by such specialized tools rather than core BigCommerce order processing.

Conclusion for BigCommerce Users and Developers

For BigCommerce users and developers seeking comprehensive order attribution data beyond the basic order_source, the path forward is clear: embrace third-party analytics solutions. While the native API offers a wealth of order information, detailed customer journey metrics like specific landing and referring sites often require external tools to capture, process, and integrate. This approach ensures that businesses can still gain the deep insights needed to optimize their e-commerce operations effectively.