Stape 5.20 and 5.21: Data Store, Requests Analytics, and Setup Wizard

On October 12 and 26, 2026, Stape released versions 5.20 and 5.21 of its server-side tracking platform. The main changes affect data management in Data Store, automated Google Tag Manager setup through Setup Wizard, usage forecasts, reporting, and the interface for managing Gateways.

Both updates aim to simplify the setup and operation of server-side tracking. Stape is expanding data management within its own infrastructure and reducing manual steps when connecting advertising platforms.

Data Store: Automatic Synchronization and Data Management

On October 26, version 5.21 expanded Data Store, Stape’s built-in NoSQL database for server-side Google Tag Manager containers.

Data Store makes it possible to store and use information directly within Stape infrastructure without creating a separate database in Google Cloud Firestore, Supabase, or another external system.

The storage model uses collections and documents. It can hold customer attributes, event parameters, identifiers, transaction data, and other information needed to process events in server-side GTM.

Version 5.21 introduced four capabilities:

Auto-sync. Scheduled automatic imports from an external CSV source. This feature is available on Enterprise plans and above.
Import Mode. A choice between merging imported data with existing records (Merge) and replacing the current contents (Replace).
Sync Fail Notification. Email notifications when automatic synchronization fails.
Documents Counter. The number of documents in a collection is displayed.

These changes are particularly relevant when a server-side container uses data that is updated regularly in external business systems.

For example, an online retailer can import a table of product costs to calculate Profit on Ad Spend, maintain a reference list of customer segments, or match event identifiers to additional parameters.

Automatic synchronization lets teams update these data sets without manually uploading files. However, record matching and data-processing rules still need to be configured correctly in the tracking infrastructure.

Data Store itself is available starting with the Pro plan, while Auto-sync requires Enterprise or a higher-tier plan.

Setup Wizard: GTM Container Creation and New CAPI Integrations

In release 5.20 on October 12, Stape added the ability to create server-side GTM containers directly through Google sign-in.

Users can sign in with Google, create a new GTM server container, or select an existing one. Stape then creates its own hosting container with the corresponding configuration.

The Setup Wizard received further updates in version 5.21 on October 26.

Stape revised the container creation flow, updated the wizard interface, and added two conversion destinations:

OpenAI Conversions API.
Microsoft Conversions API.

Setup Wizard automates the initial tracking configuration. It helps prepare Google Tag Manager templates and configure event delivery to selected advertising and analytics platforms.

For advertisers, these integrations expand the available destinations for server-side conversion data.

However, generating a configuration does not replace checking whether events are actually received, whether their parameters and identifiers are correct, or whether browser-side and server-side events are properly deduplicated.

Container Usage Forecasts and Limit Notifications

In version 5.21, Stape introduced request-usage forecasts for server-side GTM containers and Signals Gateway.

The interface now displays the expected number of requests through the end of the current billing period.

When forecast usage reaches 100% of the available limit, Stape sends an email notification.

Previously, users could review the actual number of processed requests. The forecast adds an early indication that a container may reach its allowance.

This is especially useful for websites with seasonal traffic fluctuations, promotional campaigns, or sudden increases in visits.

For performance marketers, the feature can reduce the risk of unexpected disruptions to event delivery. If estimated usage approaches the plan limit, the business can adjust its configuration or service plan before the limit is reached.

Requests Analytics: A New Name for an Existing Tool

On October 12, version 5.20 renamed two Stape products:

Stape Store → Data Store.
Stape Analytics → Requests Analytics.

These are name changes, not the launch of two new services.

Requests Analytics is designed to analyze requests received by a server-side container and assess how server-side tracking affects data collection completeness.

The tool provides information about total requests, recovered requests, event distribution by type and GTM client, and the effects of browser restrictions and ad blockers.

It helps teams evaluate how much data passes through their server-side infrastructure and whether tracking completeness changes after implementing server-side GTM.

However, Requests Analytics is not an end-to-end attribution system and does not replace GA4, advertising dashboards, or a CRM. Its purpose is to monitor data collection and recovery, rather than evaluate the commercial performance of campaigns.

Stape Interface Updates and Gateway Management

Release 5.20 included a major redesign of the Stape website, blog, and Website Tracking Checker reports. The company refreshed the navigation, forms, menus, and visual design.

In version 5.21, the changes continued inside the application.

All Gateways were consolidated on one page under a single menu item. Stape also updated the Power-ups list interface for the additional components that extend server-side container functionality.

The company improved container-list loading speed and made other smaller interface changes.

Across the two releases, Stape reported 44 bug fixes: 16 in version 5.20 and 28 in version 5.21.

Stape as Infrastructure for Server-Side Analytics and Conversion Tracking

Stape is a specialized platform for hosting and managing server-side Google Tag Manager and delivering server-side events to advertising and analytics systems.

Its primary role is to simplify the creation and maintenance of server-side tracking infrastructure without requiring businesses to deploy and administer their own servers in Google Cloud or other cloud environments.

Stape provides server-side GTM hosting, custom domains for tracking requests, ready-made advertising-platform integrations, and event-delivery diagnostics.

The ecosystem includes Meta Conversions API Gateway, TikTok Events API Gateway, Signals Gateway, solutions for Google Analytics and Google Ads, and integrations with Shopify, WordPress, Magento, and other platforms.

Additional capabilities include Requests Analytics, incoming and outgoing request logs, monitoring, the built-in Data Store, and a library of Power-ups for event processing.

For e-commerce, Stape can send product-view, add-to-cart, and purchase events, combine browser and server data, and enrich events with additional commercial parameters.

For service businesses and lead generation, the platform can send lead submissions and other conversion events to advertising systems, including CRM integrations and offline conversion uploads where configured.

For B2B companies, Stape can act as the server-side component of an analytics stack connecting website events with ad platforms and systems that record leads and sales outcomes.

Updates 5.20 and 5.21 do not change the underlying architecture of server-side tracking. They simplify container setup, automate internal data-store operations, and provide more tools for monitoring usage. For existing Stape customers, the main practical benefits are lower maintenance effort and improved control over data delivery.