Partner guide
This article is for Optimizely Implementation Partners to reference when setting up customers to use Optimizely B2B Analytics.
Implementation requirements for B2B Analytics
In most cases, implementation of B2B Analytics does not require partner support.
However, some customizations of Configured Commerce may impact B2B Analytics and should be avoided. Specifically, each of the following requirements should be met in the implementation of Configured Commerce for Configured CommerceAnalytics to work as expected:
- Configured Commerce must be cloud-hosted.
- The client must have Google Analytics and Tag Manager implemented on their Configured Commerce site.
- Off-line order history data should be loaded into the data tables of Configured Commerce.
- Analytics leverages the data tables of Configured Commerce. Standard use of key fields within key tables is required for Analytics to work properly.
Cloud-hosted Configured Commerce
B2B Analytics is only available for cloud-hosted Configured Commerce customers. It is linked to the backend data tables of Configured Commerce, which are only accessible in a cloud-hosted implementation.
Implementation of Google Analytics and Tag Manager
B2B Analytics provides information on key user actions on the site and uses Google Analytics and Tag Manager to track user behavior. Clients are expected to have Google Analytics and Tag Manager implemented on their site. Clients may choose to complete set-up for Google Analytics and Tag Manager on their own or require support from their Partner.
Offline order data loaded into Configured Commerce
B2B Analytics provides a summary of all orders, online and offline, in one place by pulling the offline order data from the data tables of the Configured Commerce Admin Console. To see offline order history, the client must have an integration job set between their ERP and the Configured Commerce that pulls in offline order history into Configured Commerce.
Standard use of key fields within specific data tables
The primary source of order history data for B2B Analytics is the data tables of Configured Commerce. The totalNetPrice field of the OrderHistoryLine and CustomerOrderLine tables is the most important field. Customizations done to this field may impact how data is aggregated in B2B Analytics and may need to be investigated.
In addition to the OrderHistoryLine and CustomerOrderLine data tables, B2B Analytics references the following tables to provide enrichment to its data: Customer, InvoiceHistory, InvoiceHistoryLine, Order History, Product, and Customer.
Other notes
- B2B Analytics is a product that Optimizely hosts and maintains.
- Optimizely provides any SQL scripts (or file template, such as if data is not being loaded into Configured Commerce for Order History) needed for implementation.
- Once Optimizely has the data flowing into B2B Analytics, the initial data should be available within a few days (at most) to customers.
- Optimizely manages user access to B2B Analytics.
- Optimizely maintains the Dashboards within B2B Analytics.
- Customers who purchase a B2B Analytics subscription can add five users as part of their subscription. Optimizely charges for additional users.
Overview of the analytics implementation process and timeline
The implementation process for B2B Analytics is outlined below.
No | Step | Responsibility | Timing | Description |
|---|---|---|---|---|
0 | Intro to Analytics at Onboarding kick-off | Optimizely’s Onboarding team | During Onboarding kick-off | 5-minute overview of the Analytics implementation process, requirements, and Configured Commerce implementation constraints. |
0 | Analytics Kick-off Meeting | Optimizely’s Onboarding team | 4-8 weeks before scheduled Go-live | 30–45-minute meeting to kick off the Analytics provisioning process, including a short demo of the product and review of remaining Analytics implementation steps. |
1 | Implementation of Google Analytics | Client or Partner | Any time before Go-live | Client or Partner to implement Google Analytics on the client’s site. Testing should be completed in Sandbox before transitioning to Production environment. |
2 | Implementation of Google Tag Manager | Client or Partner | Any time before Go-live | Client or Partner to implement Google’s Tag Manager on the client’s site. Testing should be completed in Sandbox before transitioning to Production environment. |
3 | Go Live checklist | Client | 1-2 weeks before scheduled Go-live | Client to submit required details to the Optimizely team for Analytics provisioning. |
4 | QA Validation | Optimizely Analytics Team with feedback from client | 3-5 days after Go-live | Optimizely Analytics team to link client’s data to the Optimizely instance and provide client with a preview of the data for validation. Issues and/or questions can be addressed through email or a 30-minute meeting. At least 10 production orders and a month of offline orders are required to complete this step. |
5 | Analytics Provisioning | Optimizely Analytics Team | 3-14 days after go-live | Once QA is complete, the Optimizely Analytics team will provision client users within 3 working days |