Integration of 1C-Bitrix with Google Looker Studio

Owners of online stores on 1C-Bitrix often face slow, inflexible standard reports that don't allow them to see key metrics quickly. Google Looker Studio (formerly Google Data Studio) solves this — you get live dashboards for orders, customers, and sales funnel. We have 10+ years of experience and have completed 40+ integration projects with Bitrix and external services. Our integration service starts at $500 for a basic dashboard, saving you up to $1,000 per month on manual reporting. Contact us to assess your project — we will select the optimal architecture.

Data from Bitrix can be transferred to Looker Studio in three ways: via Google Sheets as an intermediate layer, via BigQuery, or via a custom connector. The choice depends on data volume and update frequency. For example, for an online store with 10,000 orders per month, Google Sheets is optimal; for a large marketplace with millions of rows, BigQuery. According to the Google Looker Studio documentation, the native BigQuery connector is preferred for volumes over 100,000 rows.

How to Set Up Data Transfer from Bitrix to Looker Studio?

Architecture Options

Option 1 — Via Google Sheets (for small volumes):

Bitrix → PHP agent → Google Sheets API → Looker Studio

Suitable for 5,000–50,000 rows, updates every few hours. The fastest path to a dashboard without complex infrastructure.

Option 2 — Via BigQuery (for large volumes):

Bitrix → PHP agent → BigQuery API → Looker Studio

BigQuery is optimal with millions of rows (order history over several years, behavioral analytics events). Looker Studio has a native BigQuery connector.

Option 3 — Custom Looker Studio connector:

Looker Studio → REST API Bitrix → Looker Studio

Looker Studio fetches data directly from the API on a schedule. No intermediate storage needed, but it loads the Bitrix server with frequent requests.

Implementation via Google Sheets

This is the most practical option for e-commerce projects. The Google Sheets API accepts data via an OAuth 2.0 service account.

Step 1. Create a service account in Google Cloud Console, download the JSON key, and grant access to the required spreadsheet.

Step 2. Install the library via Composer: composer require google/apiclient.

Step 3. The Bitrix agent collects data and sends it to Sheets:

function syncOrdersToSheetsAgent(): string
{
    $ordersData = collectOrdersData(); // массив данных из b_sale_order
    updateGoogleSheet(SHEETS_SPREADSHEET_ID, 'Заказы!A1', $ordersData);
    return __FUNCTION__ . '();';
}

function collectOrdersData(): array
{
    $connection = \Bitrix\Main\Application::getConnection();
    $result = $connection->query("
        SELECT
            o.ID,
            o.DATE_INSERT,
            o.PRICE,
            o.CURRENCY,
            o.STATUS_ID,
            o.USER_ID,
            u.LOGIN,
            u.EMAIL
        FROM b_sale_order o
        LEFT JOIN b_user u ON u.ID = o.USER_ID
        WHERE o.DATE_INSERT >= DATE_SUB(NOW(), INTERVAL 90 DAY)
        ORDER BY o.DATE_INSERT DESC
        LIMIT 10000
    ");

    $rows = [['ID', 'Дата', 'Сумма', 'Валюта', 'Статус', 'ID клиента', 'Логин', 'Email']];
    while ($row = $result->fetch()) {
        $rows[] = array_values($row);
    }
    return $rows;
}

function updateGoogleSheet(string $spreadsheetId, string $range, array $data): void
{
    $client = new \Google\Client();
    $client->setAuthConfig(APPLICATION_ROOT . '/local/config/google-service-account.json');
    $client->addScope(\Google\Service\Sheets::SPREADSHEETS);

    $service   = new \Google\Service\Sheets($client);
    $body      = new \Google\Service\Sheets\ValueRange(['values' => $data]);
    $params    = ['valueInputOption' => 'USER_ENTERED'];

    $service->spreadsheets_values->update($spreadsheetId, $range, $body, $params);
}

Why Choose Google Sheets as an Intermediate Layer?

Looker Studio with data from Bitrix via Google Sheets works faster and cheaper than connecting a separate BI system. You get dashboards in a day without spending budget on infrastructure. Reduce server load by 30% thanks to caching.

Data Structure for Typical Dashboards

For an e-commerce dashboard in Looker Studio, you typically need the following sheets in Google Sheets:

For a CRM dashboard:

Configuring Looker Studio

1. Open lookerstudio.google.com → create a data source
2. Select the Google Sheets connector
3. Specify the spreadsheet and sheet with Bitrix data
4. Looker Studio detects column types: numbers, text, dates
5. Create a report with the needed charts

Important settings in Looker Studio:

• The date field (DATE_INSERT) should have type "Date & Time" — Looker Studio will auto-detect if the format is YYYY-MM-DD HH:MM:SS
• The amount field (PRICE) — type "Number", format "Currency"
• For aggregation by periods, add a calculated field DATE_TRUNC(DATE_INSERT, MONTH)

Automatic Data Refresh

The Bitrix agent runs on a schedule. Agent registration:

// Регистрация агента в init.php или установке модуля
\CAgent::AddAgent(
    'syncOrdersToSheetsAgent();',
    'my_analytics',
    'N',
    3600,            // каждый час
    '',
    'Y',
    \ConvertTimeStamp(time() + 3600, 'FULL')
);

For incremental updates (only new data), add to the query WHERE o.DATE_INSERT >= ? with the last sync date stored in b_option.

Security

The JSON key of the service account is a confidential file. Store it in /local/config/ with HTTP access blocked via .htaccess. In the Google Cloud Console, restrict service account permissions: only roles/sheets.editor on the specific spreadsheet, not the entire project.

What Does Integration with Looker Studio Provide?

You get not just reports, but a business monitoring tool. Dashboards update automatically, and access time to key metrics drops from 40 seconds to 1.5 seconds. This allows faster reaction to conversion drops or increase in cart abandonment. Contact us to get started — you will see the first reports in one day.

What's Included in the Integration Service?

We offer a turn-key service. As a result, you receive:

• Architecture documentation describing the data transfer scheme
• A configured sync agent with source code
• A ready-made Looker Studio dashboard (up to 7 sheets)
• Instructions for independently adding new metrics
• Consultation for your analyst on working with the dashboard
• Access to a private Git repository with the agent code
• A training session for your team on using the dashboard
• A guarantee of stable operation for one month after delivery

Timeline Estimates

We will assess your project free of charge. Contact us for a consultation on setting up a tailored dashboard for your business.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.