Loading Datablow...
Datablow Gateway Overview
PS
Active Containers
+1 this month
Avg. Response Time
↓ 18ms vs last week
Events Routed (24h)
+12.4% vs yesterday
Signal Recovery
vs 68% client-side

Active GTM Server Containers

Your deployed server-side containers and their routing mappings.

Container Provisioning Wizard
4-step onboarding flow
NEW

Paste your GTM Container Config string, pick a region, assign a custom subdomain, and deploy — all without touching GCP or a terminal.

Launch Wizard
Custom Loader & Snippet Generator
3 obfuscation variants
NEW

Generate a modified GTM snippet that routes through your first-party subdomain. Includes parameter obfuscation to defeat fingerprint-based ad-blockers.

Open Generator
Edge Worker Templates
Cloudflare · Lambda@Edge · Vercel
NEW

Pre-built same-origin edge scripts that proxy example.com/gtm/ to your sGTM container with correct IP forwarding headers.

Browse Templates
Health Dashboard
/healthy endpoint monitoring
NEW

Real-time health checks against each container's /healthy endpoint. Includes uptime tracking, response time charts, and alert thresholds.

View Health Monitor
Regional Deployment
5 global regions · latency-aware selection
NEW

Choose from EU-West, US-East, US-West, APAC (Singapore), or South America for your GTM server container. Estimated latency is shown per region to help you deploy closest to your audience.

Configure Regions
Architecture Selection

Choose Your Tracking Method

Select the deployment model that best fits your marketing and technical requirements.

Option 1: sGTM + Datablow

RECOMMENDED (BEST PRACTICE)
Set up a full first-party Google Tag Manager Server container to capture, filter, and distribute events downstream.
Advantages:
  • Better attribution quality score across search and social ads
  • Improved iOS tracking with extended first-party cookie lifetimes
  • Highly resilient to ad-blockers and tracking protection shields
  • Forward to multiple endpoints (Meta CAPI, GA4, TikTok, Ads) from one server stream

Option 2: Meta Pixel Gateway

DIRECT CAPI SETUP
Set up a direct event proxy gateway routing browser actions through your subdomain straight to Meta API without GTM.
Setup Details:
  • Replace standard Pixel tag with the gateway proxy tracking script
  • Browser sends events directly to your tracking subdomain prefix
  • No external subscription wrapper or complex custom container files required
  • Dedicated forwarding directly to Meta Server endpoints
How to get your Container Config string
In GTM → Admin → Container Settings → Set up server-side tagging → Manually provision tagging server → Copy the config string.
Paste the Base64 config string (or JSON configuration) from GTM above.

Choose the region closest to your primary audience to minimize tracking latency.

.tracking.datablow.com
Your endpoint: mytracker.tracking.datablow.com
⚡ Fully Automated — Zero DNS Setup
We will automatically create the DNS A-record and issue a free SSL certificate. Your subdomain will be live within ~60 seconds of provisioning.
Provisioning Container…
Spinning up your dedicated GTM server container. This takes ~30 seconds.
Allocating container resources…
Injecting GTM container config…
Configuring CNAME routing…
Issuing SSL certificate…
Running health check…
Configuration
Select a deployed domain or enter details manually.
Requests go to ss.yourdomain.com/xtag/js — unrecognizable to blockers.
Parameter Obfuscation
Scramble query params to defeat fingerprinting
Async Loading
Non-blocking load for performance
Noscript Fallback
Include <noscript> pixel fallback
IP Anonymization
Redact visitor IP addresses on proxy proxying
PII Redaction
Strip sensitive customer PII from payload query parameters
Event Tracking (Optional)
Select additional events to generate their implementation code & guides.
Select standard conversion or ecommerce actions to view setup code & parameters.
HTML — Place in <head>

              
HTML — Obfuscated Loader (ad-blocker resistant)

              
How obfuscation works: Query parameters like id= and gtm_auth= are base64-encoded and routed through your custom path alias. Ad-blockers cannot match known GTM fingerprints.
JavaScript — Next.js / React Component

              
PHP — WordPress Plugin File (datablow-gtm.php)

              
Create a new folder named datablow-gtm under your WordPress site's wp-content/plugins/ directory, save this code as datablow-gtm.php inside it, and activate it in the admin dashboard.
Why GTM Tag Assistant shows "Could not connect"
Shopify's Customer Pixel runs inside a sandboxed <iframe> — it is completely isolated from the main page DOM. GTM Tag Assistant cannot detect scripts inside this sandbox, so it reports "no debuggable tags".

Solution: Two-part setup. You need both snippets below — Part 1 injects GTM into your storefront so Tag Assistant can find it, Part 2 captures checkout/purchase events from the sandboxed pixel context.
1
Theme.liquid — GTM Web Container Loader
Makes your store detectable by GTM Tag Assistant & Preview Mode
Liquid — layout/theme.liquid (inside <head>)

              
How to add: In Shopify Admin → Online StoreThemesEdit code → open layout/theme.liquid → paste this snippet right before the closing </head> tag → click Save.
2
Customer Pixel — Checkout & Purchase Events
Captures checkout events from the sandboxed pixel context (add_to_cart, purchase, etc.)
JavaScript — Shopify Customer Pixel (Web Pixels API)

              
How to add: In Shopify Admin → SettingsCustomer eventsAdd custom pixel → name it Datablow sGTM → paste this script → click Connect pixel.
Google Tag Manager Server Container Tag
If you prefer to route your events from a GTM Web Container through a GTM Server Container first (similar to Stape.io), you can import our custom GTM Tag Template. This tag forwards container events to the Datablow backend.
Instructions:
  1. Download the datablow-connect-tag.tpl template file above.
  2. In your GTM Server Container, navigate to TemplatesTag Templates → Click New.
  3. Click the top-right menu (three vertical dots) and choose Import.
  4. Select the downloaded datablow-connect-tag.tpl file and click Save.
  5. Go to TagsNew → Choose the Datablow Connect Server Tag.
  6. Set the Datablow Tracking Endpoint to: https://ss.yourdomain.com (your deployed subdomain) and select a trigger to fire on all events.
Custom Event Tracking Code
No events selected yet. Select a tracking action from the dropdown in the left panel to populate code templates.
📋 Implementation Checklist
Paste the snippet into your website's <head> section
Ensure ss.yourdomain.com CNAME is propagated (use dnschecker.org)
Test with GTM Preview Mode — open your site with ?gtm_debug=x
Verify https://ss.yourdomain.com/healthy returns {"health":"ok"}
Template Variables
These values are automatically substituted into all templates below.
JavaScript — Cloudflare Worker

            
🚀 Deploy Steps
  1. 1 Go to Cloudflare Dashboard → Workers & Pages → Create Application → Worker
  2. 2 Paste the code → click Deploy
  3. 3 Under Settings → Triggers, add route: example.com/gtm/*
  4. 4 Test: curl https://example.com/gtm/healthy
Why this beats ITP: Requests to example.com/gtm/ are same-origin. Safari's ITP only restricts third-party cookies — your server sets first-party cookies that survive 180+ days.
JavaScript — AWS Lambda@Edge (Node.js 18.x)

          
🔶 AWS Setup Steps
  1. 1.Create Lambda function in us-east-1 (required for Lambda@Edge)
  2. 2.Set runtime: Node.js 18.x, handler: index.handler
  3. 3.Deploy to Lambda@Edge from CloudFront behavior matching path pattern /gtm/*
  4. 4.Trigger type: Origin Request
TypeScript — Vercel Edge Middleware (middleware.ts)

          
▲ Vercel Setup Steps
  1. 1.Save as middleware.ts in your project root
  2. 2.Add env var SGTM_HOST = your sGTM domain
  3. 3.Deploy: vercel --prod
  4. 4.Middleware runs at edge globally — zero cold starts
nginx.conf — Reverse Proxy Block

          
🔧 Nginx Setup Steps
  1. 1.Add this block to your existing server {} block
  2. 2.Test config: nginx -t
  3. 3.Reload: nginx -s reload
  4. 4.Requires ngx_http_proxy_module (default in most builds)
Containers Online
3/3
Avg. Response Time
42ms
Last polled just now
30-Day Uptime
99.97%
12 min downtime total
Active Alerts
0
All Clear
Response Time — Last 24 Hours
All containers combined · sampled every 5 minutes
Avg 42ms P95 87ms
24h ago18h ago12h ago6h agoNow
EU-West Frankfurt US-East Virginia US-West Oregon APAC Singapore SA São Paulo
Latency: ● < 50ms — Excellent ● 50–150ms — Good ● > 150ms — Consider closer region
Multi-Region Failover
Auto-fail to next closest region on downtime · Agency Scale
Deploy to Selected Region
Endpoint: https://ss.yourdomain.com → eu-west.containers.datablow.com
US
Free Starter
Account Details
Email cannot be changed after registration.
Subscription & Organization
Current Plan
Free Starter
1 sGTM Container · 3 domains
Organization
Name:
Slug:
Member since:
Change Password
Update your account password. You'll be logged out after changing.
Create API Key
Keys are only shown once upon creation. Store them securely.
Active API Keys
Manage your keys. Hashed values are stored in the database.
No active API keys found.
Your Plan: Growth Suite
Status: Active
Containers 0 / 5
Custom Domains 0 / 3
Upgrade Plan
Unlock more containers and higher request quotas.
Action Resource User IP Address Timestamp
Total Registered Users
-
Total Organizations
-
Active GTM Containers
-
Custom Domains / Gateways
-
All System Accounts
Manage user subscriptions, elevate roles to admin, or delete inactive organizations.
User / Email Role Organization (Slug) Current Plan Active Resources Actions
Google OAuth Credentials
Allow users to log in securely using Google Accounts. Configurations fall back to .env values if empty.

Create Meta Conversions API Gateway

Establish a dedicated proxy gateway that relays client web events directly to Meta Graph servers using your Pixel ID and API Access Token. No manual tagging required.

How Direct CAPI Works

With Direct CAPI, you copy-paste the Meta Pixel base code (with your Pixel ID) into your website's <head> tag. Then you add a server-side POST call from your backend (Node.js, PHP, Python, etc.) to the Meta Graph API endpoint to record conversions with full user data — bypassing browser restrictions and ad blockers entirely.

No custom domain needed
Available on Free plan
Works with any tech stack
Highest match quality score
Step 1 — Enter Your Meta Pixel ID
Enter your Pixel ID to generate a ready-to-use tracking snippet.
Found in Meta Events Manager → Data Sources → Your Pixel.
From Meta Business Settings → System Users → Generate Token.
Step 2 — Copy & Paste Into Your Website
Add the base pixel code inside <head> of every page. Then use the server snippet for purchase/lead events from your backend.
<!-- Click "Generate Snippet" above to create your code -->
Step 3 — Server-Side Event Implementation
Send conversion events from your backend to Meta's Graph API to guarantee 100% event capture.
// Node.js / Express - Direct Meta CAPI Event
const axios = require('axios');

async function sendCapiEvent(eventName, userData, eventSourceUrl) {
  const PIXEL_ID = process.env.META_PIXEL_ID;
  const ACCESS_TOKEN = process.env.META_CAPI_TOKEN;

  const response = await axios.post(
    `https://graph.facebook.com/v19.0/${PIXEL_ID}/events`,
    {
      access_token: ACCESS_TOKEN,
      data: [{
        event_name: eventName,
        event_time: Math.floor(Date.now() / 1000),
        action_source: 'website',
        event_source_url: eventSourceUrl,
        user_data: {
          client_ip_address: userData.ip,
          client_user_agent: userData.userAgent,
          em: userData.hashedEmail,  // SHA-256 hashed email
          ph: userData.hashedPhone,  // SHA-256 hashed phone
          fbp: userData.fbp,
          fbc: userData.fbc,
        },
      }],
    }
  );
  return response.data;
}

// Usage in your Express route:
app.post('/checkout/complete', async (req, res) => {
  await sendCapiEvent('Purchase', {
    ip: req.ip,
    userAgent: req.headers['user-agent'],
    fbp: req.cookies['_fbp'],
    fbc: req.cookies['_fbc'],
  }, req.headers.referer);
  res.json({ success: true });
});
WordPress? Use Our Plugin

The Datablow CAPI Tracker plugin adds server-side Meta CAPI events to your WordPress site with zero code. Supports WooCommerce, hashed user data, deduplication — with a visual settings panel.

Tips for Maximum Match Quality
Follow these best practices to achieve the highest Meta Event Match Quality Score.
✓ Send IP Address
Always forward the client IP from server logs — this alone contributes 30%+ to match quality.
✓ Hash PII Fields
SHA-256 hash emails and phone numbers before sending. Never send plain PII to the Graph API.
✓ Pass fbp & fbc Cookies
Read _fbp and _fbc cookies from the browser to enable deduplication.
✓ Use Event Deduplication
Set event_id on both browser pixel and server CAPI call with the same unique value.

Create DataBlow Gateway

Deploy a fast, secure edge proxy. Serve Google scripts (`gtag.js`, `gtm.js`) from your first-party subdomain, extending ITP cookie lifetimes to 2+ years and bypassing ad-blocker filters.

TikTok Events API
TikTok CAPI Gateway

Send web events directly to TikTok Ads servers. Restores event mapping and increases match values by 20%+.

GA4 Server Gateway
GA4 MP Connector

Forward events directly to GA4 using the Measurement Protocol. Preserves visitor sessions and bypasses ad-blockers.

Google Ads Conversions
Google Ads Gateway

Securely stream offline conversions and hashed user parameters directly to Google Ads conversion trackers.

LinkedIn Conversions
LinkedIn CAPI Gateway

Relay qualified leads and website events to LinkedIn Campaign Manager to elevate B2B matches.

Snapchat Conversions API
Snap CAPI Gateway

Route purchases, signups and clicks to Snap Pixel endpoints, bypassing browser cookie blocks.

Shopify CAPI Proxy
Shopify Gateway

Connects directly to Shopify Customer Pixels and routes all checkouts and events in first-party context.

viaSocket Connector
Server-Side Tracking

Use the viaSocket connector for server-side tracking to trigger offline conversion events from 2,000+ apps to www.datablow.com gateway.

Pipeline Name Source CRM Match Rate Routed (24h) Sent (24h) Status Actions
Loading offline tracking pipelines...
Datablow Gateway
Features Pricing
Gateways
CAPI Gateway DataBlow Gateway
Setup Guides
sGTM Setup Guide Direct CAPI Guide viaSocket Guide
Documentation & Demo
API Docs ↗ Book Demo
Legal
Privacy Policy Terms of Service
Integrations
WordPress Plugin
Copied to clipboard!