DEV Community: Luke Sandelands

How to Recover Lost Shopify Conversions with CAPI Shield (Server-Side Tracking)

Luke Sandelands — Wed, 12 Aug 2026 18:43:49 +0000

The 120-order gap is not a reporting anomaly — it represents real sales that Meta’s algorithm never learned from. Every budget decision, every audience adjustment, and every bid strategy is being built on just 40% of your actual data.

If you're relying strictly on browser-side pixels, you are bleeding ad spend. Here is why the tracking gap exists and how to close it using a server-side architecture (without paying hundreds a month for a tracking app).

The Root Cause: The Browser Tracking Gap

Since iOS 14.5, Intelligent Tracking Prevention (ITP), and the widespread adoption of ad-blockers, the traditional client-side pixel is failing.

When a user clicks your ad and buys your product, the browser often strips the ad click IDs (like fbclid) and actively blocks the tracking scripts from firing on the checkout page. The result? Shopify captures the revenue, but the advertising platform never receives the attribution signal. You lose the conversion data, and your Customer Acquisition Cost (CAC) looks artificially high.

The Solution: Server-Side Tracking

To bypass browser restrictions, you need to send the purchase event directly from your server (Shopify) to the ad platform's server. This is the exact purpose of the Meta Conversions API (CAPI) and Google Ads Enhanced Conversions.

Instead of hoping the user's browser executes a JavaScript snippet, you use a webhook to natively catch the orders/paid event in Shopify, parse the backend payload, and POST it directly to Meta and Google.

Enter CAPI Shield: A Zero-Cost Make.com Architecture

You don't need expensive, bloated Shopify apps (like Triple Whale or Elevar) to achieve this. You can build a "CAPI Shield" using a single, free Make.com scenario.

Here is the server-side architecture:

The Trigger: A native Shopify Webhook listens for the orders/paid event.
The Payload: Shopify fires a rich JSON payload to your Make.com webhook. This contains pristine first-party data: customer details (email, phone, IP address, user agent) and order data (value, currency, SKUs, order ID).
The Transformation: Make.com parses this data and formats it to match Meta's strict CAPI schema. (PII like emails and phone numbers are automatically hashed via SHA-256 before transmission).
The Delivery: The workflow pushes the hashed server event via HTTP POST directly to the Meta CAPI and Google Ads endpoints.

Because this transaction happens entirely server-to-server, ad blockers and iOS restrictions cannot intercept it. Your tracking instantly jumps from 40% visibility to 100% raw data delivery.

The Impact: High EMQ and Zero Monthly Fees

By passing clean, unblockable first-party data directly from Shopify's backend, this server-side setup typically achieves an Event Match Quality (EMQ) score of 7.0 to 8.5 out of 10.

Better yet, because a standard store processing up to 250 orders a month only uses a tiny fraction of Make.com's free tier (1,000 operations/month), this entire infrastructure costs $0/month to run. You completely eliminate the need for $150+/month third-party tracking apps while getting significantly better data.

Wrap Up

Stop letting the algorithms optimize your ad campaigns based on partial data. By moving your tracking server-side with CAPI Shield, you feed Meta and Google exactly what they need to stabilize your ROAS and find your next customer.

Want the exact blueprint? Check out the step-by-step setup guides for CAPI Shield and the rest of the free automation stack at Stack Architect.

Tidio for Shopify: Complete AI Live Chat Setup Guide (2026)

Luke Sandelands — Sat, 08 Aug 2026 14:02:30 +0000

Order status, shipping questions, and product FAQs account for 60–70% of all Shopify support volume. Tidio’s Lyro AI resolves them automatically — without a human agent, without a complex helpdesk subscription, and without a monthly fee on the free plan.

This guide covers the complete setup: installation, widget configuration, Lyro AI training, chatbot flows, Shopify order sync, and the tuning routine that separates stores achieving 70% resolution from those stuck at 30%.

Why Tidio Works for Shopify Stores

Most Shopify merchants overpay for customer support infrastructure. Platforms like Gorgias or Zendesk cost anywhere from £60–£300/month and assume a human agent is in the loop for every conversation.

Tidio’s Lyro AI reads and responds to queries using a generative language model trained directly on your FAQ content and Shopify product catalogue — resolving approximately 70% of inbound queries without human intervention, and escalating the remainder automatically.

The free tier covers 50 Lyro AI conversations per month. For stores under £30,000/month GMV, this typically handles the full support volume. Above that threshold, paid plans extend the conversation limit cleanly.

Installation — 10 Minutes

Step 1: Install from the Shopify App Store

Search for “Tidio” in the Shopify App Store and install the free app. Tidio automatically creates a live chat widget on your storefront.

Step 2: Connect Your Shopify Store Data

In the Tidio admin panel, navigate to:
Settings → Integrations → Shopify

Tidio connects automatically on installation, but verify the integration is active — you should see your store name accompanied by a green connected status.

Once connected, Tidio pulls live order data, customer purchase history, and product catalogues into the agent sidebar. Test this by looking up a recent order through the Tidio chat interface.

Step 3: Configure the Chat Widget

Navigate to Settings → Widget and configure the following:

Position: Bottom-right is standard (or bottom-left if you have competing floating CTAs).
Color: Match your brand hex code (avoid the default blue, as it looks generic).
Welcome Message: Use a specific message rather than a vague greeting. Try: "Questions about your order? We usually reply in under 2 minutes."
Operator Hours: Set your actual human response hours. Outside those hours, route all traffic to automated responses.

Step 4: Set Up the Shopify Data Sidebar

In Tidio’s agent view, the right sidebar pulls Shopify order data for the current customer. Test this with a known customer email. Human agents should be able to view order status, tracking numbers, and purchase history without ever leaving Tidio.

Lyro AI Configuration — 20 Minutes

Lyro AI’s performance depends almost entirely on the quality of your FAQ content. Default resolution rates hover around 25–35%. Reaching 70% requires deliberate knowledge base construction.

Step 1: Access the Lyro Configuration Panel

In the Tidio admin panel, go to:
Lyro AI → Knowledge Base

This is where you upload the exact content Lyro uses to answer incoming customer queries.

Step 2: Write FAQs for Actual Support Volume

Write at least 20 Q&A pairs covering these critical areas:

Order Status: "Where is my order?" — Answer with your typical processing and shipping timelines.
Returns: "How do I return an item?" — Answer with your exact return process step-by-step, not just a bare link to a policy page.
Shipping: "How long does delivery take?" — Provide specific timelines broken down by region.
Product Specifications: Provide explicit answers for the 5–10 most common product questions on your top sellers.
Out of Stock: "When will X be back in stock?" — Outline your restock communication or pre-order process.
Discount Codes: "My discount code isn’t working" — Cover common causes (exclusions, order minimums) and resolution steps.

Note: The more specific your FAQs, the higher Lyro’s resolution rate. Vague answers produce unnecessary agent escalations.

Step 3: Upload Your FAQ Content

Tidio supports plain text Q&A pairs, website URL crawling, and PDF uploads. The Q&A pair format gives the most reliable results — URL crawling often imports extraneous page elements that can confuse Lyro’s responses.

Step 4: Configure Escalation Rules

In Lyro AI → Escalation, set the following parameters:

Unresolved Handling: Route to a human agent during operating hours, or collect customer contact details outside operating hours.
Escalation Triggers: Include explicit phrases like "connect me to a person", "speak to someone", or "not helpful".
Priority Escalation: Configure complaints about damaged items or missing orders to immediately bypass AI and alert human agents.

Step 5: Enable Lyro on Your Widget

In Settings → Widget → Chat Behaviour, toggle Lyro AI to active and set Lyro as the first responder for all incoming conversations. Human agents can monitor all active conversations and take over at any point.

Chatbot Flows for Common Queries

Beyond Lyro AI, Tidio’s visual chatbot builder allows you to build structured menu flows for predictable interaction pathways:

Fixing Shopify Google Ads Conversion Tracking: Server-Side Setup Without GTM

Luke Sandelands — Thu, 06 Aug 2026 11:01:03 +0000

If your Google Ads dashboard consistently reports significantly fewer purchases than your Shopify order log, your client-side conversion tracking is failing. On standard Shopify setups, browser-based Google Ads pixels fail to capture between 20% and 40% of completed transactions.

Rather than deploying complex, paid Google Tag Manager server containers, you can resolve this attribution gap for free by implementing a direct server-to-server Enhanced Conversions pipeline using native webhooks and HTTP REST calls.

Why Browser Tracking Fails on Shopify

Standard Google Ads conversion tracking relies on gtag.js loading on the order confirmation page within the customer browser. This mechanism fails in production environments due to three distinct technical barriers:

Parameter Stripping: Safari and iOS Link Tracking Protection strip the gclid (Google Click Identifier) from URLs when links originate from Mail, Messages, or Private Browsing mode. Without the gclid, the client-side pixel cannot attribute the purchase to the corresponding campaign.
Cookie Lifespan Caps: Safari Intelligent Tracking Prevention (ITP) aggressively caps the lifespan of first-party client-side cookies. A user who clicks an ad on Monday and completes checkout on Friday often falls outside the active browser attribution window.
Script Blocking: Privacy-focused browsers like Brave, alongside extensions such as uBlock Origin, block gtag.js requests entirely.

When any of these conditions occur, the client-side conversion event vanishes, leaving smart bidding algorithms to optimize on incomplete datasets.

How Google Enhanced Conversions Works

Google Enhanced Conversions operates as a server-side matching system. When a purchase occurs, your backend sends SHA-256 hashed customer identifiers directly to Google’s API.

Google takes these hashed attributes (such as normalized email addresses and E.164 formatted phone numbers) and matches them against logged-in Google account records. If a customer clicked an ad while signed into YouTube or Gmail on mobile, but completed the purchase three days later on desktop without a valid cookie, Google matches the server payload to the user account and restores attribution.

The Architecture: Direct API Upload vs Server-Side GTM

Most industry guides recommend deploying a Google Tag Manager Server-Side container hosted on Cloud Run or Stape.io. This introduces unnecessary complexity and recurring infrastructure costs ($10 to $30 per month).

The cleaner architectural approach calls the Google Ads API directly via an automated webhook pipeline. When an order fires, your middleware formats the payload, hashes the customer identifiers, and sends an HTTP POST directly to the Google Ads endpoint.

Shopify (orders/paid Webhook)
│
▼
Middleware (Make.com / Cloudflare Worker)
├── Normalizes & Hashes PII (SHA-256)
└── Formats API Payload
│
▼
Google Ads API (uploadClickConversions Endpoint)

Implementation Payload

Your server-side pipeline list runs off the Shopify orders/paid event. The middleware extracts the customer data, applies SHA-256 hashing to the email, and issues a POST request to https://googleads.googleapis.com/v17/customers/{CUSTOMER_ID}:uploadClickConversions.

Here is the JSON payload structure required by the Google Ads API:


json
{
  "conversions": [
    {
      "conversionAction": "customers/1234567890/conversionActions/AbCdEfGhIjK",
      "conversionDateTime": "2026-08-06 11:45:00+00:00",
      "conversionValue": 149.99,
      "currencyCode": "USD",
      "orderId": "1001",
      "userIdentifiers": [
        {
          "hashedEmail": "f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44a"
        }
      ]
    }
  ],
  "partialFailure": true
}
Critical Data Handling Rules
To ensure a high match rate, your middleware must process customer attributes strictly according to Google specifications prior to hashing:

Email: Trim all leading and trailing whitespace, convert all characters to lowercase, and apply SHA-256 encoding.

Phone: Strip all non-numeric characters except for the leading plus sign, format according to the E.164 standard (e.g., +14155552671), and apply SHA-256 encoding.

Order ID: Pass the exact string representation of the Shopify order number to enable automatic platform deduplication against any surviving client-side pixel events.

System Verification
Once the HTTP pipeline is active, allow 24 to 48 hours for data aggregation. You can verify system health inside your Google Ads account under Goals → Summary → [Purchase Conversion] → Diagnostics.

The Enhanced Conversions status will transition to Active, and the reported purchase discrepancy between Shopify and Google Ads will typically compress from 30% down to under 10%.

You can read the complete architectural guide, including cross-platform setup blueprints for Meta CAPI and TikTok Events API, at [Stack Architect](https://stackarchitect.xyz/blog/how-to-fix-shopify-google-ads-conversion-tracking-2026/).

How to Fix ‘Service Invoked Too Many Times’ in Google Apps Script 2026

Luke Sandelands — Tue, 28 Jul 2026 16:12:53 +0000

“Service invoked too many times” is one of the most common Google Apps Script errors. It means your script is calling a Google service (Sheets, Docs, Drive, Gmail) faster than Google’s rate limits allow. The fix depends on which service is being called and how your script is structured.

This guide covers the exact cause for each service type and the specific code pattern that resolves it.

What the Error Actually Means

Google Apps Script enforces rate limits on calls to each of its services. These limits exist to protect shared infrastructure — your scripts run on Google’s servers alongside millions of others. When you exceed the rate for a service within a rolling time window, Google stops accepting calls and throws this error. Google’s official Apps Script quotas documentation lists the specific limits for each service type by account tier.

The key distinction: this is a rate error, not a quota error. You haven’t necessarily hit your daily limit — you’ve made too many calls too quickly. This means slowing down your script or batching calls resolves the error without waiting for a quota reset.

Common rate limits (consumer accounts):

Google Sheets read/write operations: not formally published, but high-frequency row-by-row operations reliably trigger this
Google Docs/Drive service calls: approximately 30 per minute
Gmail sends: 100 per day total (daily quota, not rate)
UrlFetch calls: 20,000 per day (daily quota)
Workspace Studio add-ons (Google Gemini Alpha program): 2-minute execution timeout, tighter than the standard 6 minutes — relevant if you build automations into Google’s newer AI surfaces

The Root Cause in 95% of Cases: Row-by-Row Processing

The most common cause is a script that processes data one row at a time, calling a service method on each iteration:


javascript
// THIS TRIGGERS THE ERROR
function processOrders() {
  var sheet = SpreadsheetApp.getActiveSheet();
  var lastRow = sheet.getLastRow();

  for (var i = 2; i <= lastRow; i++) {
    var orderId = sheet.getRange(i, 1).getValue();    // service call per row
    var status = sheet.getRange(i, 2).getValue();     // service call per row
    var result = processOrder(orderId, status);
    sheet.getRange(i, 3).setValue(result);            // service call per row
  }
}

For 100 rows, this script makes 300 service calls in rapid succession. For 500 rows, it makes 1,500. Google’s rate limiter stops accepting calls before the script finishes.

Fix 1 — Batch Reading and Writing (Resolves Most Cases)

Load all data into memory at the start, process it as an array, then write all results at once. This reduces service calls from 3× row count to exactly 2 regardless of how many rows you have.

// THIS FIXES THE ERROR
function processOrders() {
  var sheet = SpreadsheetApp.getActiveSheet();
  var lastRow = sheet.getLastRow();

  // ONE read call — load all data into memory
  var data = sheet.getRange(2, 1, lastRow - 1, 2).getValues();
  var results = [];

  // Process array in memory — no service calls
  for (var i = 0; i < data.length; i++) {
    var orderId = data[i][0];
    var status = data[i][1];
    results.push([processOrder(orderId, status)]);
  }

  // ONE write call — write all results at once
  sheet.getRange(2, 3, results.length, 1).setValues(results);
}

This single change resolves the error for most Sheets-based workflows. The processing time may actually be faster as well — memory operations are orders of magnitude faster than service calls.

Fix 2 — Exponential Backoff for Transient Errors

Some scripts make service calls that genuinely cannot be batched — for example, creating a new Google Doc for each row. For these, add exponential backoff: catch the rate limit error and retry with increasing delays.

function callWithBackoff(fn) {
  var maxAttempts = 5;
  var delay = 1000; // start with 1 second

  for (var attempt = 1; attempt <= maxAttempts; attempt++) {
    try {
      return fn();
    } catch (e) {
      if (e.message.indexOf('Service invoked too many times') !== -1) {
        if (attempt === maxAttempts) {
          Logger.log('Max retries reached: ' + e.message);
          throw e;
        }
        Logger.log('Rate limited, waiting ' + delay + 'ms before retry ' + attempt);
        Utilities.sleep(delay);
        delay *= 2; // double the delay each retry
      } else {
        throw e; // not a rate limit error, don't retry
      }
    }
  }
}

// Use it like this:
function createDocument(rowData) {
  return callWithBackoff(function() {
    return DocumentApp.create('Order_' + rowData.orderId);
  });
}

Exponential backoff handles transient rate limit spikes — situations where Google’s rate limiter briefly rejects calls that would otherwise be within limits. It does not resolve structural over-calling. If your script consistently triggers the error even with backoff, Fix 1 (batching) is the correct solution.

Fix 3 — Stagger Triggers to Prevent Concurrent Execution

If multiple time-based triggers fire simultaneously, each running instance competes for the same service quota pool. Two scripts making 200 service calls each simultaneously may trigger the rate limit even if 200 calls from one script would not.

In Apps Script: Edit → Current project’s triggers

Review all time-based triggers. If any fire at the same time (e.g., two triggers set to “every hour”), offset them by at least 5–10 minutes. A trigger at :00 and a trigger at :10 will not overlap; a trigger at :00 and another at :00 will compete.

Fix 4 — LockService for Concurrent Event Triggers

If your script runs on a form submission or webhook trigger rather than a time-based trigger, multiple simultaneous submissions can launch competing instances. Use LockService to ensure only one instance runs at a time:

function onFormSubmit(e) {
  var lock = LockService.getScriptLock();

  try {
    lock.waitLock(30000); // wait up to 30 seconds for the lock

    // Your script logic here
    processSubmission(e);

  } catch (e) {
    Logger.log('Could not obtain lock: ' + e.message);
  } finally {
    lock.releaseLock();
  }
}

This queues concurrent submissions rather than running them simultaneously, preventing service call competition between instances.

Fix 5 — Move to Make.com for High-Volume Workflows

For Autocrat-style document generation workflows that consistently hit rate limits regardless of batching and backoff, the structural solution is moving the work outside of Apps Script entirely.

Make.com calls the Google Docs API directly via HTTP module — not through Apps Script’s service layer. This bypasses Apps Script’s rate limits and the shared consumer quota pool.

The Autocrat Quota Fix guide covers the full Make.com implementation for document generation. Benefits:

No 6-minute execution ceiling

No Apps Script service rate limits

No document create daily cap (250/day consumer limit)

Runs reliably at any volume

Replace Google Apps Script with Make.com

If quota errors are blocking your Shopify workflows, Make.com is the permanent fix — it replaces GAS entirely for order-triggered automations with no quota limits on the free tier. The Complete Kit includes four ready-to-import Make.com scenarios: server-side tracking, inventory, TikTok CAPI, and P&L reporting. $29 one-time.

Frequently Asked Questions

What causes the 'Service invoked too many times' error in Google Apps Script?

This error occurs when your script makes too many calls to a Google service (Sheets, Docs, Drive, Gmail, or UrlFetch) within a rolling time window. Google enforces rate limits on service calls — typically 30 Docs/Drive operations per minute for consumer accounts. High-frequency loops that call getValues(), setValues(), openById(), or similar methods on every iteration hit this limit quickly.

How do I fix 'Service invoked too many times' in Google Sheets automation?

The primary fix is batching: call getValues() once at the start of your script to load all data into a JavaScript array, process the array in memory, then call setValues() once at the end to write results back. This reduces service calls from one per row to two total regardless of row count — eliminating the rate limit trigger for most workflows.

Does 'Service invoked too many times' mean I've hit my daily quota?

Not necessarily. Service invoked too many times is a rate limit error — too many calls in a short time window. This is different from a daily quota exhaustion error. Rate limit errors can be resolved by slowing down your script or batching calls. Daily quota errors reset 24 hours after the first request of the day (a rolling window, not a fixed midnight cutoff), or you can move the work to Make.com to bypass the quota entirely.

How do I add exponential backoff to Google Apps Script?

Wrap your service calls in a retry function that catches exceptions containing 'Service invoked too many times' and retries with increasing delays: wait 1 second, retry; if it fails again, wait 2 seconds, retry; then 4 seconds, 8 seconds, up to a maximum of 5 retries. If all retries fail, log the error and continue processing remaining rows. But what happens when you hit it? The automation silently dies. The invoice isn't sent. The inventory isn't updated. You lose money.

Tired of Apps Script crashing? I built a free workaround that moves your automation completely off Google Apps Script and onto Make.com, bypassing the 6-minute and 90-minute limits entirely. 👉 Get the free Autocrat Quota Fix here: https://stackarchitect.xyz/autocrat-quota-fix/

Is 'Service invoked too many times' different from 'Exceeded maximum execution time'?

Yes. These are two different quota errors. 'Service invoked too many times' is a service call rate limit — too many API calls in a short window. 'Exceeded maximum execution time' is an execution time limit — your script ran for longer than the 6-minute limit that applies to both consumer and Workspace accounts (the 30-minute Workspace limit cited by older guides no longer applies). Each requires a different fix. See the Google Apps Script quotas guide for the full breakdown.

Shopify Agentic Storefronts 2026 — Sell on ChatGPT & Google AI Mode (Setup Guide)

Luke Sandelands — Mon, 27 Jul 2026 09:57:05 +0000

Home
›
Guides
›
Shopify Agentic Storefronts Setup Guide 2026

Shopify Agentic Storefronts 2026 — Sell on ChatGPT & Google AI Mode (Setup Guide)

Winter '26 Edition · Early Access · Complete Setup Guide

Shopify Agentic Storefronts 2026
Sell on ChatGPT & Google AI Mode
Complete Setup Guide

AI-driven purchases on Shopify increased **11x in 2025**. Agentic Storefronts let customers buy your products without leaving ChatGPT, Google AI Mode, or Copilot. Here's the complete setup guide — including eligibility requirements, the Knowledge Base App, and exactly what to do if you're not eligible yet.

ChatGPT
Google AI Mode
Microsoft Copilot
Perplexity

11x
AI purchase growth 2025

4
AI sales channels

$0
No channel fees currently

45min
Full setup time

Jump to setup guide →
Not eligible yet? →
Free store audit

Complete guide — what's covered

01What Agentic Storefronts actually are
02Eligibility — check in 60 secondscheck first
03The 4 AI sales channels covered
04Complete 6-step setup guidesetup
05Knowledge Base App — what to writeimportant
06Product data optimisation for AI
07Limitations and what they mean for you
08Tracking AI orders and attribution
09Not eligible yet — 5 things to do now
→FAQ — 6 questions answered

In January 2026, Shopify launched Agentic Storefronts as part of their Winter '26 Edition — a feature that turns AI platforms like ChatGPT, Google AI Mode, Microsoft Copilot, and Perplexity into fully functioning sales channels for your store. When a customer asks ChatGPT "what's the best running shoe for wide feet under $120?", your products can now appear in the response — and the customer can buy directly inside the conversation without visiting your store.

This guide covers the complete setup process, including the parts most guides skip: the Knowledge Base App, product data requirements, the critical limitations that affect tracking and checkout, and a concrete action plan for stores that aren't eligible yet. The preparation matters whether you can enable it today or not — your products are already being crawled and recommended by AI platforms regardless of your settings.

If you're evaluating your full Shopify stack while setting this up, it's worth noting that email marketing costs are the second-largest app expense for most stores after tracking tools. Replacing Klaviyo with Systeme.io's free plan saves $150–$400/month and takes 30 minutes — the same time investment as the Knowledge Base App setup below.

⚠️ Still in early access — US only
As of March 2026, Agentic Storefronts are in early access and currently only available for US-based stores selling to US customers. International stores are not yet eligible for direct AI checkout — though your products are still discoverable by AI platforms via web crawling and Shopify Catalog. The preparation steps in this guide apply to all stores regardless of eligibility. Section 9 covers exactly what to do if you can't enable it yet.

01 — What Agentic Storefronts actually are

What Are Shopify Agentic Storefronts?

Shopify Agentic Storefronts connect your product catalog to AI platforms through a single setup in your Shopify admin, allowing your products to be discovered and purchased directly inside AI conversations — with no separate integrations required for each platform.

There's an important distinction most merchants miss. Product discovery on AI platforms already happens without Agentic Storefronts. AI platforms like ChatGPT and Google already crawl the web and can recommend your products. What Agentic Storefronts adds is direct checkout — the ability for a customer to complete a purchase inside ChatGPT without being redirected to your store.

Discovery vs checkout — the key distinction

**Without Agentic Storefronts active:** AI platforms can recommend your products (via web crawling and Shopify Catalog), but customers are redirected to your store to complete the purchase.

**With Agentic Storefronts active:** Customers can discover your products AND complete checkout directly inside the AI conversation. Your pricing and inventory stay current in real time. Orders appear in Shopify Admin with full channel attribution.

02 — Eligibility requirements

Who Is Eligible for Shopify Agentic Storefronts?

Eligibility check takes 60 seconds: go to Shopify Admin → Settings → Apps and sales channels. If you see an "Agentic Storefronts" section, your store is eligible. If not, review the requirements below.

Required to be eligible

US-based store selling to US customers
Terms of Service added to your store (Settings → Policies)
Privacy Policy added to your store
Refund Policy added to your store
Guest checkout enabled (customers cannot be required to log in)
Agreement to Shopify's Agentic Storefronts Supplemental ToS

Not yet supported

Non-US stores (international rollout in progress)
Stores requiring mandatory customer login before checkout
Stores without published policies
Subscription-only product catalogs
Stores on Shopify Starter plan

Not eligible yet? Sign up at shopify.com/chatgpt to be notified when your store becomes eligible. Shopify is rolling out eligibility in stages through 2026. International stores are expected in H2 2026.

03 — The 4 AI sales channels

Which AI Platforms Does This Cover?

Shopify Agentic Storefronts currently supports four AI platforms at varying levels of checkout integration. Each requires individual activation inside your Shopify admin.

ChatGPT

● LIVE — Full checkout

Complete in-chat checkout. Products appear when users ask shopping-intent questions. Orders attributed to ChatGPT channel in Shopify Admin. Largest current user base for AI shopping.

Google AI Mode & Gemini

● LIVE — Full checkout

Products surface in Google AI Mode responses and Gemini shopping queries. Checkout stays inside the Google interface. High traffic potential given Google's search volume.

Microsoft Copilot

● LIVE — Full checkout

Shopping integration inside Microsoft Copilot (formerly Bing Chat). Strong B2B audience and Windows user base. Separate channel toggle in Agentic Storefronts settings.

Perplexity

○ DISCOVERY — Redirect checkout

Product discovery via Perplexity's shopping answers. Currently redirects to your Shopify store for checkout rather than completing in-chat. Direct checkout expected later in 2026.

04 — Complete 6-step setup guide

How to Set Up Shopify Agentic Storefronts (Step-by-Step)

Total setup time: approximately 45 minutes if your product catalog is already well-organised. Allow 90 minutes if you need to clean product descriptions and add policies first.

Check Eligibility required first

Go to Shopify Admin → Settings → Apps and sales channels. Look for an "Agentic Storefronts" section. If it's there, you're eligible. If not, the section will not appear — see Section 9 for what to do.

⏳ 2 minutes

Add Store Policies required

Go to Shopify Admin → Settings → Policies. Ensure you have a Terms of Service, Privacy Policy, and Refund Policy published. These must be live before you can activate Agentic Storefronts. Shopify's policy generator can create compliant templates if you don't have them.

⏳ 5–10 minutes

Install the Knowledge Base App strongly recommended

Search "Knowledge Base" in the Shopify App Store, or navigate to Settings → Apps and channels → Knowledge Base App. Free for Shopify Plus. $50/month for standard plans. Activate it, then create your first knowledge base — include FAQs, return policies, shipping information, and brand voice guidelines. AI agents use this to give accurate, on-brand answers. See Section 5 for exactly what to write.

⏳ 20–30 minutes

Optimise Your Product Catalog strongly recommended

Ensure every product has: a complete descriptive title (brand + product + key spec), a detailed description (200+ words covering materials, sizing, use cases), all variants defined with accurate stock, current pricing, and high-quality images. Add relevant metafields. Use Shopify's Catalog Mapping for custom product data structures. See Section 6 for the full product data checklist.

⏳ Variable — depends on catalog size

Enable Agentic Storefront Channels activation

Go to Settings → Apps and sales channels → Agentic Storefronts. Read and agree to the Supplemental Terms of Service. Toggle on each AI channel individually: ChatGPT, Google AI Mode and Gemini, and Microsoft Copilot. Each channel has a separate toggle. You can enable them individually or all at once.

⏳ 5 minutes

Verify and Monitor ongoing

Go to Agentic Storefronts → Test Agent to verify your products appear correctly in simulated AI queries. Monitor AI-attributed orders in your Orders list, filtered by channel. Review search trend data and FAQ insights in your Agentic Storefronts dashboard to understand what customers are asking AI agents about your products.

⏳ Ongoing

05 — Knowledge Base App

The Knowledge Base App — What to Actually Write

The Knowledge Base App is the most under-used part of Agentic Storefronts. It's invisible to your customers but directly shapes what AI agents say about your products. When a customer asks "does this store have a good return policy?", the AI answers from your Knowledge Base content — not by scraping your website.

Most merchants activate it and write nothing useful. Here's what to actually include:

1. FAQs — Write for the Questions AI Agents Get Asked

Think about what customers ask during the purchase decision phase. Write at least 15–20 Q&As covering: shipping times and costs, return and refund policy (specifics, not generalities), product sizing and fit guidance, materials and care instructions, warranty and quality guarantees, and your brand's core differentiators. Write answers in plain, direct language — AI agents paraphrase content, so clarity matters more than marketing tone.

2. Return and Refund Policy (Detailed Version)

Your Shopify policies page is a legal document. Your Knowledge Base entry should be the customer-friendly version: what the process actually involves, how long refunds take, what "free returns" means in practice, and any exceptions. AI agents will cite this when answering return questions — make it accurate and reassuring.

3. Brand Voice Guidelines

Tell the AI how to represent your brand. Specify: formal or casual tone, key phrases you want used or avoided, how to describe your core product benefits, and any regulatory or compliance language to include or exclude. This is particularly important for supplements, medical devices, or regulated products where AI paraphrasing could create compliance issues.

4. Shipping and Fulfilment Information

Processing times, carrier options, tracked vs untracked shipping, delivery estimates by region, international shipping availability, and what happens if an order is delayed. Be specific — "3–5 business days" is more useful than "fast shipping".

Replacing your tracking stack at the same time?

CAPI Shield gives you free server-side tracking for Meta & Google — critical because Agentic Storefronts only fires server-side pixels.

See CAPI Shield →

06 — Product data optimisation for AI

Optimising Your Product Data for AI Discovery

AI agents are not search engines. They don't just match keywords — they interpret intent and match products to conversational queries. A product titled "Blue Sneaker" will lose to "Men's Wide-Fit Running Sneaker — Breathable Mesh, Cushioned Sole, UK 7–13" when a customer asks ChatGPT for a comfortable wide-fit running shoe.

Product Title Formula

Use: [Brand] + [Product Type] + [Key Differentiator] + [Size/Variant Info if relevant]. Aim for 60–80 characters. Include the words customers actually use in conversation, not internal product codes.

Product Description Requirements

Minimum 200 words. Cover: what the product is (plain language first sentence), key materials and specifications, who it's designed for and in what use case, how it compares to common alternatives, care and maintenance, and any certifications or quality guarantees. Use short paragraphs and bullet points — AI agents parse structured content more reliably than dense prose.

Variant and Inventory Accuracy

AI agents will not recommend products that show as out of stock. Keep inventory counts current. Define all variants explicitly — if you sell in 5 colours and 8 sizes, all 40 combinations should be defined with accurate stock counts. Vague "multiple options available" descriptions hurt AI recommendations.

Metafields for AI Context

Add metafields for: material composition, care instructions, age/gender suitability, country of manufacture, certifications, and compatible products. AI agents can use metafield data to answer specific questions your product description doesn't cover.

07 — Limitations

Agentic Storefronts Limitations (March 2026)

These are the limitations that matter most for your operations. Read this section before enabling — several have direct revenue and compliance implications.

[Table data omitted for Markdown - please format manually if needed]

Table accurate as of March 2026. Shopify is actively expanding capabilities through H1 2026.

⚠️ Critical — tracking gap
Google Analytics 4 and browser-based pixels (Meta Pixel, TikTok Pixel) do not fire inside agentic checkout. Only server-side pixels are supported. If you rely on GA4 conversion data or browser pixels for ROAS measurement, you will have a blind spot for AI-channel orders. The fix is server-side tracking — CAPI Shield covers Meta and Google server-side for free. For TikTok, see the TikTok Events API guide.

08 — Tracking AI orders and attribution

How to Track Agentic Storefront Orders

Orders completed through Agentic Storefronts appear in your Shopify Admin Orders list with full channel attribution. You can filter by AI channel (ChatGPT, Google AI Mode, Copilot) to see revenue by source. The Agentic Storefronts dashboard also shows search trend data — the queries customers typed into AI platforms before finding your products — which is highly useful for content and SEO strategy.

Server-Side Tracking Setup (Required for Full Attribution)

Because browser pixels don't fire in agentic checkout, you need server-side events to capture conversions properly in your ad platforms. Three setups to have in place:

Shopify Pixels (native): These fire server-side by default and will capture agentic orders automatically once you've set them up in Settings → Customer events.
Meta Conversions API: Ensure your CAPI setup sends Purchase events server-side. CAPI Shield handles this at zero cost.
Google Enhanced Conversions: Set up via Google Tag Manager server-side container or directly through Shopify's Google channel. This ensures agentic purchases are attributed correctly in Google Ads.

What the Agentic Storefronts Dashboard Shows

Inside Settings → Apps and sales channels → Agentic Storefronts → Analytics, you'll find: orders and revenue by AI channel, product discovery data (which products appeared in AI responses), customer search queries from AI platforms, Knowledge Base usage and top-queried topics, and conversion rate by channel. Export this data monthly — it's one of the most valuable sources of unfiltered customer intent language available.

09 — Not eligible yet

Not Eligible Yet — 5 Things to Do Right Now

If Agentic Storefronts isn't available in your Shopify admin yet, your products are still being discovered and recommended by AI platforms through web crawling and Shopify Catalog. The difference is checkout only — discovery is already happening. These five steps improve your AI discovery performance now and put you in the best possible position when eligibility opens.

step 01
Install and populate the Knowledge Base App

AI agents can access your Knowledge Base for product discovery even without Agentic Storefronts active. Install it now, write comprehensive FAQs, and populate your return policy and shipping info. When Agentic Storefronts goes live for your store, your Knowledge Base is already doing work.

step 02
Clean your entire product catalog

Complete titles, 200+ word descriptions, all variants defined, accurate pricing and inventory. Do this now — AI platforms are already crawling your catalog. Every product you improve increases your chances of appearing in AI recommendations today, not just after Agentic Storefronts launches.

step 03
Add FAQ schema to blog posts and product pages

FAQ schema markup (JSON-LD FAQPage type) makes your content directly parseable by AI crawlers. Add FAQ schema to every blog post and key product pages. Tools like Make.com can automate schema injection across your content at scale.

step 04
Set up server-side tracking now

When Agentic Storefronts enables, browser pixels won't fire in agentic checkout. If you're not server-side ready, you'll have an immediate attribution gap. Get CAPI Shield set up now — it's free and takes under an hour — so tracking is solid on day one.

step 05
Sign up for early access

Register at shopify.com/chatgpt to be notified when your store becomes eligible. Shopify is rolling out eligibility in stages. International stores are expected in H2 2026. Being on the waitlist ensures you're notified at the earliest opportunity.

bonus
Reduce app costs while you wait

Most stores waste $400–$700/month on apps they can replace for $0. Use the Automation Scanner to find which apps you can cut immediately, and the App Cost Calculator to see your exact monthly bill. Savings go straight to margin.

Want to replace your paid Shopify apps for free?

Make.com's free tier replaces email automation, order workflows, inventory alerts, and more. 884 workflows — zero monthly cost.

Start free on Make.com →

FAQ — Common questions answered

Shopify Agentic Storefronts — FAQ

What are Shopify Agentic Storefronts?

Shopify Agentic Storefronts allow customers to discover and purchase your products directly inside AI platforms like ChatGPT, Google AI Mode and Gemini, and Microsoft Copilot — without leaving the conversation. Launched as part of Shopify's Winter '26 Edition, they connect your Shopify product catalog to AI platforms through a single setup in your Shopify admin, with no separate integrations required for each platform. Orders appear in your Shopify admin with full channel attribution.

Who is eligible for Shopify Agentic Storefronts?

As of March 2026, Agentic Storefronts are in early access and require: (1) A US-based store selling to US customers; (2) Store policies including Terms of Service published; (3) Guest checkout enabled — customers cannot be required to log in before checkout; (4) Agreement to the Shopify Agentic Storefronts Supplemental Terms of Service. Shopify is rolling out eligibility in stages through 2026. Sign up at shopify.com/chatgpt for early access notification.

Is the Shopify Knowledge Base App free?

The Knowledge Base App is free for Shopify Plus merchants. For standard Shopify plans (Basic, Shopify, Advanced), it costs $50/month. The app is only visible to AI agents — it does not appear anywhere on your storefront. It allows you to upload FAQs, return policies, shipping information, and brand voice guidelines so AI agents give accurate, on-brand answers about your products. It's worth installing even before Agentic Storefronts is active, as AI platforms can access it through Shopify Catalog.

Can customers still find my products on ChatGPT if I don't enable Agentic Storefronts?

Yes. Your products can still be discovered and recommended via web crawling and Shopify Catalog, regardless of your Agentic Storefronts settings. The difference is checkout: with Agentic Storefronts active, customers can purchase directly inside the AI chat. Without it, they are redirected to your Shopify store to complete the purchase. Discovery is automatic. Direct AI checkout requires Agentic Storefronts to be enabled.

What are the key limitations of Shopify Agentic Storefronts?

Key limitations as of March 2026: (1) US-only — only available for US stores selling to US customers; (2) No Google Analytics or browser pixel tracking in agentic checkout — only server-side pixels fire; (3) Subscriptions and product bundles are not supported; (4) Discount codes may not work depending on the AI channel's checkout interface; (5) Some checkout blocks and customisations do not display; (6) Local delivery, store pickup, and pickup points are not available as delivery options.

What should I do if my store isn't eligible for Agentic Storefronts yet?

Four things to do now: (1) Install and populate the Knowledge Base App — AI agents use it for product discovery even without Agentic Storefronts active; (2) Clean your product catalog — complete titles, detailed descriptions, all variants defined, accurate pricing; (3) Add FAQ schema markup to your blog posts and product pages; (4) Sign up at shopify.com/chatgpt to be notified when your store becomes eligible. Your products are already being crawled and recommended by AI platforms — the preparation matters now.

free — no account required

Replace your paid
Shopify apps for free

Make.com's free tier handles email automation, order workflows, inventory alerts, and Slack notifications. Most stores save $400–$700/month. Setup takes under an hour.

Start free on Make.com →
See the full $0 stack →

// AFFILIATE DISCLOSURE — Links marked sponsored on this page may earn Stack Architect a commission at no cost to you. We only link to tools we use and recommend. Make.com affiliate: techie123. Systeme.io affiliate link used on relevant pages.

Recover 20–40% of invisible Shopify conversions — free

Luke Sandelands — Sun, 26 Jul 2026 11:13:35 +0000

Home
›
Guides
›
Shopify Server-Side Tracking: Free Setup Guide 2026

Free Setup · No Code · Under 20 Minutes · Meta + Google + TikTok

✓ UPDATED JULY 2026 — VERIFIED FREE TIER · iOS 26

Recover 20–40% of invisible
Shopify conversions — free

Your Shopify dashboard shows 68 orders. Meta shows 41. Google Ads shows 29. TikTok shows 18. The gap is real revenue your ad algorithms are optimising blind on. This guide fixes it free in under 20 minutes using Make.com — no code, no app, no agency.

Meta CAPI
Google Enhanced Conversions
TikTok Events API
20–40% Conversions recovered
17.8% Lower CPA w/ CAPI (Meta, '26)
$0 Cost vs $225+/mo Elevar
18 min Setup time

Start Free on Make.com →
Jump to Setup

TL;DR — 6 Key Points

01 Server-side tracking sends purchase events from Shopify's backend directly to Meta, Google and TikTok — bypassing browsers, ad blockers and iOS ATT.

02 iOS App Tracking Transparency and Safari ITP now block 30–40% of browser pixel events. Server-side is the only reliable fix.

03 The Make.com webhook method costs $0/month. Elevar charges from $225/month for the same result. Triple Whale uses GMV-based pricing that scales with store revenue.

04 Full three-platform build takes ~18 minutes: one Shopify webhook, three Make.com HTTP modules, zero code. No developer needed.

05 Always run browser pixel AND server events simultaneously. Use matching event_id values for deduplication so you count one purchase, not two.

06TikTok requires CompletePayment not "Purchase". Include hashed email, phone, IP and user agent to achieve Event Match Quality score 8+.

IOS IMPACT: What iOS 14–18 actually broke in your Shopify tracking — step-by-step diagnostic and the exact settings to restore attribution.

Contents

Direct answer (60 seconds)
What is server-side tracking?
Why it matters in 2026
2020–2026 privacy timeline
Pixel vs CAPI vs hybrid
EMQ benchmarks
What you need
Complete 7-step setup
Meta CAPI deep dive
Google Enhanced Conversions
TikTok Events API
Free vs paid comparison
Troubleshooting
FAQ

DIRECT ANSWER

Shopify Server-Side Tracking Explained in 60 Seconds

Shopify server-side tracking is a method of sending purchase, checkout, and add-to-cart events from Shopify's backend directly to Meta, Google, and TikTok — bypassing the customer's browser entirely. It is the only reliable way to track conversions in 2026 because iOS App Tracking Transparency, Safari's Intelligent Tracking Prevention, ad blockers, and consent banner rejections now combine to block 30–40% of browser pixel events on the average Shopify store.

The mechanism is straightforward. When a Shopify order is paid, Shopify fires an orders/paid webhook. That webhook is intercepted by an automation tool — Make.com is the free standard — which receives the order payload (email, phone, total, line items, customer IP, user agent), hashes the personal data with SHA-256, and posts a signed event to three endpoints: Meta's Conversions API, Google's Enhanced Conversions endpoint, and TikTok's Events API. The browser pixel still fires alongside this for deduplication; both events share the same event_id so each platform counts one conversion, not two.

The result is what Meta calls a higher Event Match Quality (EMQ) score — typically jumping from 4–5 (browser-only) to 8–9 (server + browser hybrid) — which feeds richer signal back into the ad platform's machine learning. Higher EMQ directly lowers cost-per-acquisition because the algorithm can find lookalikes more accurately.

Quick answer table

What it is: Server-to-server transmission of conversion events, fired by Shopify webhooks instead of browser JavaScript.
Why it's needed in 2026: iOS ATT, Link Tracking Protection (introduced in iOS 17 and still enforced in iOS 26), Safari ITP 2.3+, and consent rejection block roughly one in three browser pixel events.
What it costs: $0/month using the Make.com webhook method. From $145/month using managed services (Analyzify, Triple Whale, Elevar).
How long it takes: 18 minutes for a working Make.com setup. 2–3 hours if you want full GTM Server-Side Container deployment on Google Cloud Run.
What you need: Shopify Admin access, Meta Business Manager access token, Google Ads conversion ID, TikTok Pixel ID, a free Make.com account.
What you should track: Purchase (Meta), conversion (Google), CompletePayment (TikTok). Note: TikTok does not use "Purchase" — this is the most common setup error.
Expected uplift: 20–40% additional reported conversions, 1–3 point Meta EMQ improvement, 10–25% lower cost-per-purchase as the algorithm receives cleaner signal.

DEFINITION

What is Server Side Tagging (Shopify Server-Side Tracking)?

Server-side tracking (also called Conversions API, server-to-server tracking, or S2S tracking) sends conversion events directly from your web server to advertising platforms — completely bypassing the customer's browser. Instead of relying on a JavaScript pixel in the browser to fire when a purchase completes, a webhook fires from Shopify's backend the moment payment is confirmed, routing event data directly to Meta's Conversions API, Google's Enhanced Conversions endpoint, and TikTok's Events API.

The key distinction is where the event originates. A browser pixel depends on the customer's device: their browser settings, installed extensions, network conditions, and whether they accepted your cookie banner. A server event originates from Shopify's infrastructure — it fires regardless of what the customer's browser does, making it immune to ad blockers, iOS privacy restrictions, and Safari's Intelligent Tracking Prevention.

Server-side vs browser pixel: the architecture

The complete $0 architecture: one webhook, one Make.com scenario, three ad platforms fed server-to-server. Nothing in this path can be blocked client-side.

✕ Browser pixel only

1Customer completes purchase

2Thank-you page loads in browser

3Pixel JavaScript tries to fire

4Ad blocker / ITP / ATT blocks it

5Conversion never recorded

✓ Server-side tracking

1Customer completes purchase

2Shopify backend fires webhook instantly

3Make.com receives full order payload

4HTTP module POSTs to Meta/Google/TikTok

5Conversion recorded every time

Server-side tracking does not replace your browser pixel — it runs in parallel with it. The pixel handles upper-funnel events (ViewContent, AddToCart, InitiateCheckout) that server webhooks cannot capture since they only fire on confirmed payment. Together, the two methods give each ad platform the most complete signal possible.

WHY IT MATTERS IN 2026

Why Server-Side Tracking Is Non-Negotiable in 2026

The browser tracking environment has degraded dramatically since 2021 and continues to worsen. iOS 14.5 introduced App Tracking Transparency (ATT), requiring explicit opt-in for cross-app tracking — approximately 62% of iOS users decline. iOS 17 added Link Tracking Protection, which strips UTM and click-ID parameters from URLs in Safari Private Browsing and Mail. Safari's Intelligent Tracking Prevention deletes first-party cookies after 7 days and blocks all third-party cookies. Firefox Enhanced Tracking Protection blocks third-party cookies by default. Chrome's Privacy Sandbox continues its phased rollout despite delays.

The cumulative effect: on a typical Shopify store with normal UK or US traffic mix, 30–40% of actual purchases are invisible to your browser pixel. Your ad platforms are optimising delivery on incomplete data — which means higher CPAs, suppressed ROAS, and budget allocated to audiences that look unprofitable but aren't.

How much data are you actually losing?

Estimated browser pixel loss by platform (2026 UK/US traffic mix)

How iOS, Chrome and Safari Broke Browser Pixels: A Dated Timeline

Server-side tracking did not become essential overnight. It became essential because of seven specific platform changes between 2020 and 2026, each of which removed a slice of the data browser pixels used to capture. Understanding the timeline matters because it explains why the same Shopify store reporting 95% of Meta conversions in 2019 now reports 60–70% in 2026 with no change to its setup. Nothing is broken — the rules changed underneath the pixel.

April 2021 — iOS 14.5 and App Tracking Transparency

Apple shipped App Tracking Transparency in iOS 14.5, requiring every app to display a permission prompt before accessing the Identifier for Advertisers (IDFA). Industry opt-in rates settled at 20–25% globally and 16–18% in the US. For Shopify stores, the immediate effect was that Meta lost the ability to attribute roughly 75% of in-app Instagram and Facebook conversions on iOS devices. Meta's Aggregated Event Measurement protocol launched in response, capping each domain to eight tracked events with a 24–72 hour delayed-attribution window. Meta CAPI was Meta's recommended remediation from this date forward.

September 2021 — Safari ITP 2.3 enforcement on Shopify checkouts

Safari's Intelligent Tracking Prevention had existed since 2017, but version 2.3's seven-day cap on first-party cookies set via document.cookie reached full enforcement on Shopify domains in late 2021. Stores using legacy _fbp and _fbc cookies set client-side saw return-visitor attribution windows collapse from 30 days to seven. The fix — setting these cookies server-side via HTTP Set-Cookie headers with a maximum 30-day lifetime — required either Shopify Plus access to checkout extensibility or a server-side tagging container.

October 2022 — iOS 16 link tracking parameter stripping

iOS 16's Mail, Messages and Safari Private Mode began stripping known click-tracking parameters from URLs — including fbclid, gclid and ttclid. Stores relying on URL parameters to attribute paid traffic lost the click identifier the moment a user shared a product link via iMessage. Server-side tracking partially mitigates this by capturing the fbc/fbp values at order creation rather than at click time, but the fundamental loss of click attribution on shared links remains a 2026-era reality.

September 2023 — iOS 17 Link Tracking Protection

iOS 17 extended parameter stripping into Mail and Messages by default for all users, not just Private Mode. Combined with iOS 17's expanded ATT prompts, average attribution loss for Shopify Meta campaigns measured by Meta's own conversion-lift studies reached 28–34% on iOS traffic.

2024 — Google Consent Mode v2 mandatory in EEA

From March 2024, Google Ads and GA4 in the European Economic Area required Consent Mode v2 with explicit ad_storage and ad_user_data signals. Stores without correctly configured Consent Mode v2 saw EEA conversion reporting drop to zero in Google Ads. Server-side tracking via Google Enhanced Conversions partially preserves attribution because hashed first-party data (email, phone) is sent server-side and matched to logged-in Google accounts, sidestepping the cookie-consent dependency.

2025 — Chrome third-party cookie deprecation pivot

Google walked back its 2020 commitment to remove third-party cookies in Chrome and instead shipped a per-user opt-in choice in 2025. The practical result for Shopify stores is roughly 20–30% of Chrome users now operate without third-party cookies, which breaks cross-domain pixel matching for retargeting audiences. Server-side first-party data transmission is the only durable counter.

2026 — iOS 18 advanced fingerprinting protection and Apple Intelligence

iOS 18 introduced advanced fingerprinting protections in Safari Private Mode, blocking screen-resolution, canvas, audio-context and font-list reads commonly used by browser pixels for probabilistic matching. Apple Intelligence summaries also began surfacing third-party content without driving the click that would normally fire a pixel. The cumulative attribution gap on browser-only pixel setups now ranges from 30% (best case, mostly Android traffic) to 45% (DTC stores with majority iOS audiences).

What the timeline means in practice
If your Shopify store launched before 2021 and still relies on Shopify's default Meta pixel app or a basic GTM client-side container, your reported ROAS is mathematically understated by 25–40% versus reality. You are over-paying for attribution gaps. The 18-minute Make.com setup recovers the majority of this gap at $0/month.

ARCHITECTURE MATRIX

Browser Pixel vs Server-Side CAPI vs Hybrid: Which Setup You Actually Need

There are exactly three viable conversion-tracking architectures for a Shopify store in 2026. Most guides recommend hybrid by default without explaining when the simpler options are acceptable. Here is the honest decision framework, with the named failure modes for each approach so you can pick on facts, not vibes.

Option 1 — Browser pixel only (Shopify default)

The native Meta Pixel app, Google Tag in theme.liquid, and TikTok Pixel app fire JavaScript events from the customer's browser. This is what every Shopify store starts with and what 70% of stores never move beyond.

Where it works: stores under $5,000/month ad spend, audiences that skew Android, and merchants who do not run lookalike or retargeting campaigns. If your decisions are not algorithmically driven, signal degradation matters less.

Named failure modes:

iOS attribution gap — 30–45% of iOS purchases never report back to Meta.
Ad-blocker silence — uBlock Origin, Brave browser, and Pi-hole networks block pixel script downloads entirely. No event fires at all.
Consent rejection — in EEA/UK markets, 30–55% of users decline marketing cookies. With Consent Mode v2 active, pixel events are conversion-modelled rather than directly observed, halving precision.
Page-load drop-off — 8–12% of purchase events fire late or not at all because the customer closed the tab or hit a thank-you page redirect before the pixel completed its network request.
Bot inflation — pixel scripts execute for any browser-like client, including the 15–25% bot share on the average Shopify store. Audiences become polluted.

CASE STUDY: CAPI Shield: how server-side events recovered 20–40% of purchases invisible to pixel-only tracking — EMQ scores and deduplication data included.

Option 2 — Server-side CAPI only (no browser pixel)

You disable the browser pixel entirely and rely solely on webhook-fired server events. This sounds clean and is occasionally recommended in privacy-focused communities. It is wrong for every commercial Shopify store.

Where it works: nowhere, in practice. The closest legitimate use case is a B2B Shopify Plus store where every transaction is invoiced manually after a sales call — a tiny minority.

Named failure modes:

No view-content data — product views, search events and add-to-cart events are extremely awkward to fire server-side because they do not generate a Shopify webhook. Meta's lookalike models depend on these mid-funnel signals.
No browser cookies for matching — without the pixel setting _fbc and _fbp, your CAPI events arrive with degraded match keys. Meta EMQ scores cap around 5–6 even with hashed PII.
No Advanced Matching auto-collection — the browser pixel auto-hashes form-field email and phone. Server-only setups must manually capture and pass these.
Lookalike audience starvation — without browser-pixel page-view density, custom audiences for retargeting drop below the 1,000-user minimum required to run.

Option 3 — Hybrid: browser pixel + server-side CAPI with deduplication

Both fire. Both share an event_id. Meta, Google and TikTok deduplicate on the platform side and count one conversion. This is the architecture every documented case study at scale uses — Shopify itself uses it for native apps, so does Klaviyo for its predictive analytics integrations, and every reputable agency from Common Thread Collective to Triple Whale defaults to hybrid.

Where it works: any Shopify store running $1,000/month or more in paid social, paid search or TikTok Ads. The marginal cost of adding server-side to an existing pixel setup is 18 minutes and $0 if you use the Make.com webhook method.

Named failure modes:

Missing event_id — if both events fire without a shared identifier, conversions double-count. Meta will report 1.6–1.9x actual purchases.
Mismatched event names — firing "Purchase" in the browser and "CompletePayment" server-side on TikTok prevents deduplication. Same event, two different platforms' APIs use different names.
Webhook silence on free Shopify plans — Shopify Basic limits webhook reliability under sustained load; the fix is the Make.com retry policy, which catches missed deliveries and retries with exponential backoff for 24 hours.

The matrix

Browser only: simplicity 10/10, signal quality 4/10, EMQ ceiling 5/10, monthly cost $0, data loss 30–45%.
CAPI only: simplicity 6/10, signal quality 5/10, EMQ ceiling 6/10, monthly cost $0, data loss 25–35% (mid-funnel events missing).
Hybrid (recommended): simplicity 7/10, signal quality 9/10, EMQ ceiling 9/10, monthly cost $0–$500 depending on stack, data loss 5–15%.

The cheapest path to hybrid in 2026 is the Make.com webhook method documented in the setup section of this guide. Make.com's free tier covers up to 1,000 credits/month, which is sufficient for any Shopify store under approximately 250 orders per month. Above that volume, the Core plan at $12/month covers 10,000 credits — free Make.com account here.

EMQ BENCHMARKS

Event Match Quality Benchmarks: What "Good" Looks Like in 2026

Event Match Quality is Meta's 1–10 score for how confidently it can match an inbound CAPI event to a real Facebook or Instagram user. It is the single most actionable diagnostic in server-side tracking because it directly correlates with cost-per-acquisition in Meta's machine-learning bidding. Stores at EMQ 8+ consistently report 12–28% lower cost-per-purchase than equivalent stores at EMQ 5–6. This section gives you the benchmark ranges, the specific match keys that move each score, and the failure modes that cap your EMQ regardless of effort.

The Meta EMQ scale, decoded

Meta publishes EMQ in Events Manager under each event source. The score is calculated daily on a rolling 7-day basis from the match keys present in your CAPI payloads. The bands map to this:

EMQ 9–10 (excellent): Hashed email + phone + first name + last name + city + state + zip + IP + user agent + fbc + fbp + external_id. Achievable only with logged-in customers or post-purchase events from Shopify.
EMQ 7–8 (very good): Hashed email + phone + zip + IP + user agent + fbc + fbp. The realistic ceiling for guest-checkout Shopify stores using the Make.com webhook method.
EMQ 5–6 (acceptable): Hashed email + IP + user agent only. The default for stores running CAPI without browser-pixel cookie capture.
EMQ 3–4 (poor): IP + user agent only. This is what bot traffic and malformed payloads look like; Meta will downweight your data in lookalike construction.
EMQ 0–2 (broken): Missing or malformed payloads. Investigate immediately; events are likely not being attributed.

Match-key impact, ranked by lift

Not all match keys move EMQ equally. Based on Meta's own documentation and observed behaviour across multiple Shopify deployments, here is the ranked impact of each key on EMQ score:

Email (em): +2.0 to +2.5 points. The single highest-leverage match key. Always SHA-256 hash, lowercase, trim whitespace.
Phone (ph): +1.5 to +2.0 points. Must be E.164 format (e.g. 447700900123, no +, no spaces) before hashing.
External ID (external_id): +1.0 to +1.5 points. Use Shopify's customer.id. Hash it.
Click ID (fbc): +0.5 to +1.0 points. Capture from the URL parameter fbclid or from the browser pixel cookie at order creation.
Browser ID (fbp): +0.5 to +0.7 points. Read from the _fbp cookie set by the Meta browser pixel.
First name + last name + city + state + zip: +0.3 to +0.6 points combined. Hash each individually.
IP address (client_ip_address): +0.2 to +0.4 points. Must be the customer's IP, not Shopify's or Make.com's server IP — the most common Make.com setup error.
User agent (client_user_agent): +0.1 to +0.3 points. Captured from the order's browser_user_agent field in the Shopify order payload.

Google Enhanced Conversions match-rate benchmarks

Google does not publish an equivalent to EMQ. Instead, Enhanced Conversions reports a match rate as a percentage in the Google Ads conversion-action diagnostic panel. The benchmarks for Shopify stores are:

70%+ match rate: excellent. Achieved with hashed email + phone + name + address.
50–70% match rate: good. Typical for hashed email + phone only.
30–50% match rate: acceptable, but indicates many guest checkouts with throwaway emails.
Below 30%: investigate immediately. Often indicates SHA-256 hashing is being applied incorrectly (e.g. hashing already-hashed values) or that the user_data object is missing required fields.

TikTok Events API match scoring

TikTok measures event quality differently. The diagnostic appears as "Event Match Score" in TikTok Events Manager, scored 0–100. The benchmarks:

80–100: excellent. Hashed email + phone + IP + user agent + TikTok Click ID (ttclid) all present.
60–80: good. Most match keys present, possibly missing ttclid (organic/direct traffic legitimately won't have it).
40–60: acceptable for direct/organic traffic only. Investigate for paid-traffic events.
Below 40: something is wrong. Check that the event name is CompletePayment, not Purchase — this is the single most common TikTok integration error.

Common EMQ-killer mistakes (and their fixes)

Hashing the wrong format: emails must be lowercased and trimmed before hashing. Phones must be E.164 digits-only. "User@Example.com " hashed raw will not match Meta's expected hash of "user@example.com".
Sending Shopify's server IP: if you use Shopify's native Meta CAPI integration, it sends the customer's IP correctly. If you use Make.com, you must explicitly map order.client_details.browser_ip, not the IP of the Make.com runtime.
Double-hashing: Shopify's order payload contains plaintext email and phone. Hash these once, server-side, before posting to Meta. Re-hashing already-hashed values produces a useless string.
Missing external_id: the simplest +1.0 EMQ point most Shopify stores leave on the table. Pass order.customer.id as external_id after hashing.
Stale fbp/fbc: _fbp cookies expire after 90 days. If your store has a long sales cycle and the cookie has expired by purchase time, fall back to the email + phone + external_id combination.

Diagnostic checklist
Open Meta Events Manager → Data Sources → your pixel → Settings tab. Check "Event Match Quality". If you see anything below 7.0 after running CAPI for 7 days, work down the match-key impact list above starting with email format, then phone E.164, then external_id, then IP source. Each fix typically lifts EMQ within 48 hours.

PREREQUISITES

What You Need Before Starting

You need four things before you begin. All are free. None require a developer.

A Make.com account — free plan covers 1,000 credits/month, sufficient for stores up to ~300 orders/month. Sign up free here.
Meta Pixel ID and Conversions API Access Token — found in Meta Events Manager → your pixel → Settings → Conversions API → Generate access token.
Google Ads Conversion ID and label — found in Google Ads → Tools → Measurement → Conversions → your purchase conversion → Tag setup.
TikTok Pixel ID and Events API Access Token — found in TikTok Events Manager → your pixel → Settings → Events API → Generate access token.

Keep all four credentials in a secure note — you will paste them into Make.com HTTP modules during setup. Never share your access tokens publicly or commit them to GitHub.

7-STEP SETUP

Complete Setup: The Make.com Webhook Method

This method fires directly from Shopify's backend on payment confirmation — no browser dependency, no thank-you page required, no Shopify app to install. Total time: 18 minutes.

GOOGLE ADS: Google Enhanced Conversions via Make.com webhook for Shopify — no GTM container, no server hosting, no monthly cost.

Create your free Make.com account

Sign up at Make.com — no credit card required. The free plan gives you 1,000 credits/month. One Shopify order = 4 credits (the webhook trigger plus one HTTP module per platform), so the free plan covers ~250 orders/month. Create a new scenario and name it "Shopify Server-Side Tracking".

⏱ 2 minutes

Add a Webhooks trigger module

In your new scenario, click the empty module circle. Search for Webhooks → Custom webhook. Click Add, name it "Shopify order webhook", save. Make.com generates a unique webhook URL — copy it now. This URL is your secure endpoint that Shopify will POST order data to.

⏱ 2 minutes

Add the Shopify Order Payment webhook

In Shopify Admin → Settings → Notifications → Webhooks, click Create webhook. Set:

Event: Order payment • Format: JSON • URL: paste your Make.com webhook URL
Save. Shopify will POST the full order payload to Make.com every time a payment is confirmed — not on order creation, not on fulfilment, on confirmed payment only.

⏱ 2 minutes

META Add Meta CAPI HTTP module

Add an HTTP → Make a request module. Configure:

URL: https://graph.facebook.com/v24.0/YOUR_PIXEL_ID/events?access_token=YOUR_TOKEN
Method: POST • Body type: Raw • Content type: JSON
Use the current Graph API version — Meta deprecates older versions roughly every two years. Check the Graph API changelog for the latest vXX.0 and swap it into the URL.
In the body, map: event_name = Purchase, event_id = order ID, event_time = Unix timestamp, value = order total, currency = currency code. In user_data: SHA-256 hash email and phone before sending.

⏱ 5 minutes

GOOGLE Add Google Enhanced Conversions module

Add a second HTTP → Make a request module branching from the same webhook trigger. Google Enhanced Conversions matches server data to logged-in Google accounts using hashed user data. Send SHA-256 hashed email, phone, first_name, last_name alongside the conversion value and order ID. This improves match rate significantly above email-only matching.

⏱ 4 minutes

TIKTOK Add TikTok Events API module

Add a third HTTP module. POST to https://business-api.tiktok.com/open_api/v1.3/event/track/.

Critical: use event_name = CompletePayment, not "Purchase". TikTok's algorithm only recognises CompletePayment as a purchase event. Include hashed email, hashed phone, customer IP address, and user agent from the Shopify order payload. These four signals together drive Event Match Quality above 8/10.

⏱ 4 minutes

Activate and verify all three platforms

Switch the Make.com scenario On. Place a test order on your store. Check within 60 seconds:

Meta: Events Manager → Test Events → look for Purchase, source: server
Google: Ads → Conversions → Diagnostics → Enhanced conversions status
TikTok: Events Manager → Test Events → look for CompletePayment
All three should show green. If any shows yellow, see the Troubleshooting section below.

⏱ 3 minutes

Ready to start? Create your free Make.com account

No credit card. Free plan covers 250 orders/month. Full three-platform build takes ~18 minutes.

Start Free →

META CAPI

Meta Conversions API: Complete Configuration

Meta's Conversions API (CAPI) is the server-side counterpart to the Meta Pixel. It was introduced after Apple's iOS 14.5 ATT update and has since become Meta's primary recommended tracking method for e-commerce. When your browser pixel fires and your CAPI event fires for the same purchase, Meta deduplicates them using the event_id field — so you see one conversion, not two. The full [Meta Conversions API documentation](https://developers.facebook.com/docs/marketing-api/conversions-api) covers all available parameters and the required fields for e-commerce events. ### The exact Meta CAPI payload Every field below improves your Event Match Quality score. The more fields you send, the better Meta can match the event to a real user in its database and attribute the conversion correctly. Full Meta CAPI payload structure

**Endpoint:** POST https://graph.facebook.com/v24.0/{PIXEL_ID}/events?access_token={TOKEN} *(use the current Graph API version — see Meta's [changelog](https://developers.facebook.com/docs/graph-api/changelog/))*

Required: event_name Purchase • event_time Unix timestamp • action_source website • event_id Shopify order ID (must match browser pixel)

User data (all SHA-256 hashed): em email • ph phone • fn first name • ln last name • ct city • zp zip code • country 2-letter code • client_ip_address raw IP • client_user_agent raw UA

Custom data: currency • value • order_id • content_ids array of SKUs • num_items quantity

Deduplication: the most important step

Without deduplication, every purchase generates two "Purchase" events in Meta Events Manager — one from your browser pixel and one from CAPI. This inflates your reported ROAS and causes Meta's algorithm to optimise on false data. The fix is simple: set the same event_id value in both events. In your browser pixel, pass eventID: '{{order.id}}' in the Purchase event parameters. In Make.com, pass the same order ID as event_id. Meta matches them and counts one conversion.

Testing Meta CAPI

In Meta Events Manager, navigate to Test Events. You will see a Test Event Code. Add this as a test_event_code parameter in your Make.com HTTP module during testing. Place a real test order. Within 60 seconds you should see a Purchase event appear with source labelled "Server". Once confirmed, remove the test_event_code from your production scenario.

GOOGLE ENHANCED CONVERSIONS

Google Enhanced Conversions: Setup & Verification

Google Enhanced Conversions improves conversion measurement accuracy by sending hashed first-party customer data alongside your conversion tags. When a customer who is logged into a Google account makes a purchase on your store, Google can match the hashed data to their Google profile and attribute the conversion even if no cookie was set — including cross-device conversions where the customer first clicked your ad on desktop but purchased on mobile.

There are two implementation approaches: via Google Tag Manager Server-Side container, or via the Google Ads Enhanced Conversions for Web feature. For Make.com users, the simplest approach is to configure Enhanced Conversions for Web in Google Ads and send the hashed data in your existing conversion tag, then complement this with an order-level upload via the Make.com HTTP module.

Data fields that improve Google match rate

High impactEmail (SHA-256)
Primary match signal. Must be lowercase, trimmed, then hashed.

High impactPhone (SHA-256)
E.164 format (+447911123456) then hashed. Significantly improves mobile attribution.

Medium impactFirst + Last Name
Lowercase, trimmed, SHA-256 hashed. Improves match for users without email history.

Medium impactPostal address
Street, city, postal code, country. Useful for cross-device attribution.

SHA-256 hashing in Make.com
In Make.com, use the built-in sha256(lowercase(trim(email))) function to hash customer data. Apply this to every user data field before sending. Never send raw PII to any advertising platform — all platforms require SHA-256 hashing as a condition of their API terms.

Verifying Google Enhanced Conversions

In Google Ads, navigate to Tools → Measurement → Conversions. Click your purchase conversion action, then Diagnostics. The Enhanced conversions tab shows your match rate percentage. A match rate above 40% is good; above 60% is excellent. If your rate is below 20%, check that you are hashing email correctly (lowercase and trimmed before hashing) and that phone numbers are in E.164 format.

Prefer a ready-made version? CAPI Shield is the pre-built Make.com scenario for Meta CAPI and Google Enhanced Conversions — import it and go, no manual webhook build required.

TIKTOK EVENTS API

TikTok Events API: Maximising Event Match Quality

TikTok's Events API uses an Event Match Quality (EMQ) score to measure how well your server events can be matched to TikTok users. Scores range from 0–10. A score above 7 is considered good; above 9 is excellent. The EMQ score directly affects TikTok's ability to attribute conversions and optimise delivery — a higher score means more conversions attributed and better ROAS.

The single most important difference between TikTok and Meta/Google: TikTok requires the event name CompletePayment, not "Purchase". If you send "Purchase" to TikTok's Events API, it will appear in your Events Manager but will not be used for purchase campaign optimisation. This is the most common TikTok setup mistake.

TikTok EMQ signal hierarchy

Critical (+3 EMQ)Email (SHA-256)
Strongest matching signal. Send as lowercase SHA-256 hash.

Critical (+3 EMQ)Phone (SHA-256)
E.164 format, then SHA-256. Essential for mobile-first TikTok audience.

High (+2 EMQ)External ID
Your internal customer ID from Shopify. Hashed SHA-256.

Medium (+1 EMQ)IP + User Agent
Raw IP address and full user agent string. Send unhashed from Shopify order payload.

TikTok API endpoint
POST https://business-api.tiktok.com/open_api/v1.3/event/track/
Headers: Access-Token: YOUR_TOKEN • Content-Type: application/json
Required body fields: pixel_code • event CompletePayment • timestamp ISO 8601 • event_id order ID • context.user with hashed signals • context.ip • context.user_agent • properties.currency • properties.value

Sending all four high-impact signals (email, phone, external_id, IP/UA) typically achieves an EMQ score of 8–9/10. A higher match score directly improves TikTok's ability to attribute conversions and optimise delivery — the same server-side principle Meta quantified in April 2026, when it reported advertisers using the Conversions API for web events saw an average 17.8% lower cost per result than those without it. Check your EMQ score in TikTok Events Manager → your pixel → Overview → Event Match Quality.

The pre-built TikTok version is TikTok Events API for Shopify — the same CompletePayment setup, ready to import in minutes.

FREE VS PAID COMPARISON

Make.com Free vs Elevar vs Triple Whale vs Analyzify

Server-side tracking is a solved problem. The question is whether you need to pay $99–$950/month for a managed solution or whether the free Make.com method gives you equivalent tracking quality. Here is the honest comparison.

[Table data omitted for Markdown - please format manually if needed]

The tracking quality difference between Make.com and paid solutions like Elevar is minimal for stores sending the same data fields. Elevar's premium justifies itself primarily through managed GTM setup, data layer configuration, and attribution reporting dashboards — not through superior API access. Both hit the same Meta CAPI and TikTok Events API endpoints with the same payload structure. The key advantage of paid solutions is that they handle edge cases automatically (order edits, refunds, subscription renewals). If your store processes over 1,000 orders/month, Make.com's Core plan at $12/month is still dramatically cheaper than any managed alternative.

Our recommendation: Start with Make.com free. If you grow to 300+ daily orders or need refund/edit tracking and multi-currency handling, evaluate Elevar at that point. Until then, the Make.com method gives you 95% of the tracking quality at 0% of the cost.

META'S FREE ONE-CLICK CAPI

What About Meta's New One-Click Conversions API? (April 2026 Update)

In April 2026 Meta launched a Meta-enabled Conversions API — a free, one-click setup inside Events Manager that turns on server-side tracking for Meta with no developer, no code, and no ongoing maintenance. If your only goal is Meta CAPI, this is now the fastest route, and you should use it: it is genuinely easier than building a webhook, and it is free. We would be doing you a disservice not to say so.

So when does the Make.com method in this guide still make sense? Three honest cases:

You run more than just Meta. Meta's one-click setup covers Meta only. The Make.com webhook fires one Shopify order to Meta, Google Enhanced Conversions and TikTok Events API in a single scenario, with a shared event_id across all three. One source of truth, three platforms, no per-platform native setup to maintain separately.
You want control over the payload. The native setup is a black box — you get what Meta sends. With Make.com you decide exactly which match keys go out, how IP and user-agent are mapped, and how refunds or order edits are handled. That control is what moves EMQ from 6 to 8+.
You don't want to depend on each platform's native tool. Native integrations change on the platform's schedule, not yours. A single Make.com scenario you own keeps your tracking portable if you switch platforms or one native tool degrades.

The honest summary: if you advertise on Meta alone and want the simplest possible setup, use Meta's one-click native CAPI — it's free and excellent for that one job. If you run Meta + Google + TikTok, or you want control over match quality and a portable setup you own, the Make.com method below is still the most capable free option. Many stores run both: native one-click for Meta as a baseline, and the Make.com scenario for Google and TikTok.

TROUBLESHOOTING

Troubleshooting Common Server-Side Tracking Issues

Events not appearing in Meta Events Manager

Check in this order: (1) Is your Make.com scenario switched On? Scenarios default to Off. (2) Did you place a test order on a published product, not a draft? Shopify's Order payment webhook only fires for real checkout orders, not test orders placed via the Shopify admin. (3) Is your access token correct and unexpired? Meta access tokens generated via Events Manager do not expire, but tokens generated via the Graph API Explorer expire after one hour. (4) Is your Pixel ID correct? The Pixel ID in your Make.com URL must match the pixel you are viewing in Events Manager.

Double-counting conversions (seeing 2x purchases)

This means deduplication is not working. Both your browser pixel and CAPI are firing but with different event_id values. Fix: ensure your browser pixel Purchase event passes eventID set to the Shopify order ID. In Make.com, ensure event_id is mapped to the same order ID field from the webhook payload. Both values must be identical strings.

TikTok events show but EMQ score is low (<5)

Low EMQ almost always means missing user data fields. Check: (1) Is email being sent and SHA-256 hashed? It must be lowercase before hashing. (2) Is phone in E.164 format (+447911123456) before hashing? (3) Are IP address and user agent mapped from the Shopify order payload? In Make.com, map browser_ip from the order webhook for IP and client_details.user_agent for user agent.

Google Enhanced Conversions match rate below 20%

The most common cause is incorrect email hashing. Google requires: lowercase the email → trim whitespace → SHA-256 hash → send. If any step is skipped, the hash will not match Google's database. In Make.com use: sha256(lowercase(trim(email))). Also verify you are sending phone in E.164 format before hashing.

Make.com scenario fails with HTTP 400 error

A 400 error from any platform API means your payload is malformed. The most common causes: (1) Missing required fields — check the platform's API docs for required vs optional fields. (2) Incorrect data types — value must be a number, not a string. (3) Invalid timestamp — event_time must be a Unix timestamp (seconds since epoch), not a date string. In Make.com, use the toUnix(now) function to generate the correct timestamp format.

Want the Make.com scenario pre-built?

CAPI Shield is our free pre-configured Meta + Google server-side tracking setup for Shopify stores. Zero configuration required. Want all of it — Meta, Google, and TikTok — as one importable bundle? The Complete Kit has all four scenarios ready in 10 minutes.

Get CAPI Shield Free →

FAQ

Frequently Asked Questions

What is Shopify server-side tracking and how does it work?Shopify server-side tracking sends purchase events directly from your server to ad platforms (Meta, Google, TikTok) without going through the customer's browser. When a Shopify order is paid, a webhook fires to Make.com which routes the event to each platform's API endpoint — bypassing iOS restrictions, ad blockers, and cookie limitations. It works alongside your existing browser pixel, not instead of it.

Do I need to remove my browser pixel when setting up server-side tracking?No — keep your browser pixel running alongside server-side tracking. The pixel captures upper-funnel events (ViewContent, AddToCart, InitiateCheckout) that server webhooks don't cover since they only fire on confirmed payment. Set a matching event_id in both your pixel and server events so each platform deduplicates and you see one conversion, not two.

How much of my lost Shopify conversion data will server-side tracking recover?Most Shopify stores recover 20–40% of previously invisible conversions after deploying server-side tracking, consistent with measured iOS attribution loss of 28–45% on browser-only pixels. Meta reported in April 2026 that advertisers running the Conversions API for web events saw an average 17.8% lower cost per result versus those without it. The exact figure depends on your traffic mix — stores with high iOS and mobile traffic typically see higher recovery rates. The gap between your Shopify dashboard and ad platform reports should narrow significantly within 24–72 hours.

Is server-side tracking GDPR compliant?The data flows through your own Make.com workspace — you control what is sent and can delete the scenario at any time. All personally identifiable information (email, phone) is SHA-256 hashed before transmission as required by each platform's API specification. Ensure your store privacy policy discloses server-side conversion data sharing with advertising platforms. For GDPR-specific advice consult a legal professional.

How long before I see results after setting up server-side tracking?Server events start flowing immediately after your first paid order. More conversions will appear in your ad platform reporting within 24–48 hours. Meaningful CPA and ROAS improvement typically takes 7–14 days as ad platform algorithms recalibrate delivery optimisation using the more complete conversion signal.

How often does Make.com's free tier actually fail or rate-limit?The Make.com free plan limit is 1,000 credits/month, refreshing on the 1st of each month. One Shopify order = 4 credits (webhook trigger + Meta + Google + TikTok), so the free tier handles ~250 orders/month before hitting the cap. Make.com does not "fail" mid-month — it pauses your scenario and emails you. Real failure modes are different: a temporary Meta API outage, an expired access token, or a malformed payload. These are caught in Make.com's execution log under each scenario, and re-runs are free.

Will server-side tracking keep working as iOS tightens privacy further?Yes. Server-side tracking is specifically designed to be immune to iOS browser-level restrictions because the event originates from Shopify's server, not the customer's iPhone. Every iOS release since 17 has extended Link Tracking Protection and tightened Safari's Intelligent Tracking Prevention — both of which only affect browser pixels. CAPI, Google Enhanced Conversions, and TikTok Events API will continue to function exactly as documented. If anything, server-side tracking becomes more valuable with each iOS release.

Do I still need server-side tracking if I'm using Shopify's native Customer Events / Web Pixels?Yes. Shopify's Web Pixels framework is still browser-based — it loads in a sandboxed iframe in the customer's browser and is subject to the same ad blocker and ITP restrictions as a regular pixel. It improves reliability slightly versus a raw Meta Pixel install, but does not match the recovery rate of a true server-side webhook firing from Shopify's backend on confirmed payment. Run Web Pixels for upper-funnel events (PageView, AddToCart) and the Make.com webhook method for the Purchase event.

What is the difference between Meta CAPI and Shopify's native data sharing?Shopify's native Maximum data sharing setting enables their own CAPI integration, but it is still partially browser-triggered — if the thank-you page pixel fails to execute, the server event may not fire. The Make.com webhook method fires directly from Shopify's backend on payment confirmation with zero browser dependency, making it more reliable.

Can I set up Shopify server-side tracking without a developer?Yes. The Make.com webhook setup requires no code. You configure a Shopify webhook in Settings, build an HTTP module in Make.com's visual drag-and-drop interface, and paste your API credentials. Most store owners complete the setup in under 20 minutes. No developer, no agency, no Shopify app installation required.

Does server-side tracking work with Shopify's native Maximum data sharing?Yes — the Make.com webhook method works independently of and alongside Shopify's native data sharing. You do not need to disable native CAPI. Running both adds redundancy: if one delivery method has a transient failure, the other ensures the event still reaches the platform. Use matching event_id values in both so platforms deduplicate correctly.

How much does Shopify server-side tracking cost?The Make.com webhook method costs $0/month for Shopify stores under approximately 250 orders per month, since each order consumes 4 Make.com credits (one per platform: Meta, Google, TikTok) and the free tier covers 1,000 credits monthly. Above 250 orders/month, the Make.com Core plan at $12/month covers 10,000 credits — sufficient for stores up to roughly 3,300 orders/month. Managed alternatives like Elevar (from $225/month) and Triple Whale (GMV-based) achieve the same tracking quality at significantly higher cost. The premium pays for managed onboarding and dashboards, not for superior API access.

What Event Match Quality (EMQ) score is good for Meta CAPI on Shopify?Meta scores Event Match Quality from 1 to 10. For Shopify stores using the Make.com webhook method, EMQ 7–8 is the realistic ceiling and represents very good performance — achieved by sending hashed email, phone, zip, IP, user agent, fbc and fbp. Scores of 9–10 are excellent but typically require logged-in customer data with full address fields. Anything below 5 indicates missing match keys: investigate email format (lowercase + trim before SHA-256), phone format (E.164 digits-only before SHA-256), and the external_id field (Shopify customer.id, hashed). Stores at EMQ 8+ consistently report 12–28% lower cost-per-purchase than equivalent stores at EMQ 5–6.

Why is my TikTok event match quality low even with server-side tracking?The single most common cause is sending the event name "Purchase" instead of CompletePayment. TikTok's Events API requires CompletePayment as the event name for purchase events — sending "Purchase" (which works for Meta) results in low Event Match Score and prevents purchase-campaign optimisation. Other common causes: missing hashed email, missing IP address (you must map order.client_details.browser_ip from the Shopify webhook payload, not the Make.com runtime IP), missing TikTok Click ID (ttclid) for paid traffic, and missing user agent. Sending all four high-impact signals (email, phone, IP/UA, external_id) typically lifts TikTok Event Match Score to 80–100.

Is Shopify server-side tracking free?Yes — the tracking itself is free to implement. The Make.com webhook method in this guide costs $0/month for stores under ~250 orders/month, because each order uses 4 Make.com credits and the free tier covers 1,000. Above that, Make.com Core is $12/month for 10,000 credits. The platform APIs — Meta CAPI, Google Enhanced Conversions, TikTok Events API — are all free to use. You only pay if you choose a managed tool: Elevar runs from $200/month and Triple Whale from $149/month, but they charge for dashboards and managed onboarding, not for better tracking access. The same events reach the same endpoints either way. See the free vs paid comparison for the full breakdown.

Shopify server-side tracking vs Elevar — what's the difference?Both send the same server-side events to the same destinations (Meta CAPI, Google, TikTok) — the difference is who builds and maintains the pipeline. Elevar is a managed service from $200/month: it provisions a server-side GTM container, supplies a pre-built Shopify data layer, monitors delivery with alerts, and handles refunds and order edits automatically. The free Make.com webhook method delivers the same events and the same Event Match Quality ceiling, but you build the scenario yourself in ~18 minutes and maintain it. Choose Make.com for zero cost and full control; choose Elevar if managed monitoring, automatic edge-case handling, and a reporting dashboard justify the monthly fee at your ad spend. For most stores under 1,000 orders/month, the Make.com method delivers the tracking quality without the recurring cost.

Do I need server-side GTM (sGTM) for Shopify server-side tracking?No. Server-side Google Tag Manager is one way to do server-side tracking, but it requires provisioning and paying for a Google Cloud tagging server and configuring containers — overkill for most Shopify stores. The Make.com webhook method skips GTM entirely: Shopify fires an order webhook directly to Make.com, which POSTs to each platform's API. You get the same server-to-server delivery with no server to host or maintain. sGTM earns its complexity only for large stores with dedicated analytics engineers needing custom tag logic across many destinations; for everyone else, the webhook method is simpler, free, and equally effective for conversion tracking.

RELATED GUIDES

More Free Shopify Tracking & Automation Guides

Shopify Agentic Storefronts 2026 — Sell on ChatGPT & Google AI Mode
Fix Google Apps Script Quota Errors Free — Complete Guide 2026
CAPI Shield — Free Pre-Built Server-Side Tracking for Shopify
Free TikTok Events API Blueprint on GitHub — Import in 6 Minutes
All Free Shopify Automation Guides — Replace $700/Month of Apps

Google Apps Script Quota Limits 2026 — Every Error, Every Fix

Luke Sandelands — Sat, 25 Jul 2026 21:06:33 +0000

If your automation just stopped mid-run, you have hit a quota limit. Here is exactly which one and how to fix it — free, no upgrade required, works at any order volume.

Quick Answer — The Numbers That Matter in 2026:

Both consumer (free) and Google Workspace accounts get a 6-minute maximum execution time per script run — the old 30-minute Workspace limit no longer applies. Consumer accounts are capped at 90 minutes of trigger runtime per day; Workspace accounts get 6 hours of trigger runtime per day. UrlFetch calls are capped at 20,000 per day on consumer accounts (100,000 on Workspace). These are hard limits that cannot be increased.

If you have ever seen "Service invoked too many times", "Exceeded maximum execution time", or "Could not obtain lock", you already know the symptom. This guide explains the exact numbers behind those errors, when they appear by account type, and what actually works when order or document volume gets serious.

What Are Google Apps Script Quotas?

Google Apps Script quotas are hard limits on how much work a script can do. They exist to protect shared infrastructure — stopping one workflow from consuming resources that affect thousands of other users. Quotas appear across four layers, and they all apply simultaneously:

User-level quotas: Tied to the Google account running the script. Consumer and Workspace accounts have different ceilings.
Project-level quotas: Tied to the Apps Script project itself. Concurrent executions are capped here.
Service quotas: Gmail, Sheets, Drive, UrlFetch, and other services each have their own daily limit.
Execution quotas: Limits on how long a single run can take and how much total runtime is consumed in a day.

The critical point is that these limits stack independently. A workflow can be fine on execution time but fail on service call rate — which is why the same script can work perfectly for a small operation and break as soon as volume rises.

Google Apps Script Limits & Official Documentation

These are the official limits as of 2026. Google rarely announces quota updates widely, which makes keeping track of real infrastructure caps vital.

Max Execution Time (6 Minutes): A single script run on a free or Workspace Google account is hard-stopped after 6 minutes. The 30-minute limit some older guides cite was retired — there is no longer any per-execution headroom from upgrading to Workspace.
Trigger Runtime per Day: Consumer accounts get 90 minutes total combined runtime of trigger-driven executions per day; Workspace gets 6 hours. Once exhausted, triggered scripts stop until the quota resets 24 hours after the first request. Manual runs do not count against this cap.
UrlFetch Calls per Day: Capped at 20,000 for Consumer and 100,000 for Workspace. Automations hit this ceiling faster than expected when checking external APIs (Shopify webhooks, tracking endpoints) on every row.
Document Service Calls: Capped at 30 per minute for Consumer accounts. Applies to calls made to Google Docs or Drive in any rolling 60-second window. Autocrat-style workflows hit this quickly.
Quota Reset Window: Per Google's documentation, quotas reset 24 hours after the first request — a rolling window, not a fixed midnight cutoff.

Consumer vs. Workspace — When to Upgrade?

Upgrading to Workspace does not raise the 6-minute per-execution ceiling. What Workspace does raise is the daily headroom: trigger runtime (90 min → 6 hr), UrlFetch calls (20,000 → 100,000), and email recipients (100 → 1,500).

Quota Comparison Table

Quota Type	Consumer (Free)	Google Workspace	Resets
Single execution time	6 minutes	6 minutes	Per run
Trigger runtime/day	90 minutes	6 hours	24h rolling
UrlFetch calls/day	20,000	100,000	24h rolling
Document creates/day	250	1,500	24h rolling
Email recipients/day	100	1,500	24h rolling
Concurrent executions	30	30	Per moment
Script properties size	500KB	500KB	Persistent

Why Quota Limits Break Your Automations

Quota failures are rarely random. They follow predictable patterns based on four root causes:

Burst Processing: Too many reads, writes, or document operations concentrated in one short window.
Trigger Overlap: Multiple time-based or event-based triggers fire before the previous execution finishes.
Large Batch Size: One job attempts to process more rows than a single 6-minute execution can handle.
Hidden Retry Loops: Failed executions trigger automatic retries, accelerating the failure spiral.

Quotas are a capacity problem, not a coding problem. You can reduce the pain with better architecture — but you cannot build unlimited scale on top of limits that Google has fixed at the infrastructure level.

Common Quota Errors and What They Mean

Error Message	Quota Breached	Immediate Cause
`Service invoked too many times`	Service call rate	Too many calls to Sheets, Docs, Drive, or Gmail in a short window
`Exceeded maximum execution time`	6-min execution ceiling	Single run took longer than 6 minutes — script hard-stopped mid-execution
`Could not obtain lock`	Concurrent execution	Two runs tried to access the same resource simultaneously
`Quota exceeded`	Daily service limit	`UrlFetch`, document creates, or email sends hit the daily cap

How to Stay Under Quotas Without Breaking Your Workflow

These six techniques reduce quota pressure and can sustain most medium-volume automations on consumer accounts:

Batch Smaller Chunks: Process 50–100 rows per run instead of everything at once.
Reduce API Calls Aggressively: Cache sheet values at the start using getValues() once, operate on the array in memory, then write back with a single setValues() call.
Stagger Triggers: Separate time-based triggers by at least 5–10 minutes to prevent overlapping executions.
Persist State with PropertiesService: Save progress checkpoints so a timed-out script can resume from where it stopped.
Add Exponential Backoff: When a service call fails, wait and retry with increasing delays.
Use LockService Deliberately: Acquire a lock at the start of any execution that touches shared data.

Why Autocrat Specifically Hits Quota Limits

Autocrat is one of the most popular document generation tools for Google Sheets — and one of the most quota-sensitive. If you are generating contracts, invoices, or certificates from Sheets rows, you will hit quota limits earlier than almost any other workflow.

Each Autocrat document generation triggers multiple service calls in sequence: it opens Drive, reads the template, creates a new document, writes merged data, converts to PDF, saves to Drive, and optionally sends via Gmail. That is 5–8 service calls per row. At 30 document service calls per minute, Autocrat can reliably process around 4–5 documents per minute — or roughly 25–30 in a single run before the service rate limit triggers.

The Structural Fix

The reliable solution is moving document generation off Google's shared execution environment entirely.

Instead of Autocrat running inside Apps Script on Google's public quota pool, the workflow should run through a dedicated Make.com scenario or direct API pipeline that calls the Google Docs API directly via a private HTTP connection. Direct API runs are not subject to Apps Script execution time limits or the 250-documents-per-day consumer limit.

DEV Community: Luke Sandelands

How to Recover Lost Shopify Conversions with CAPI Shield (Server-Side Tracking)

The Root Cause: The Browser Tracking Gap

The Solution: Server-Side Tracking

Enter CAPI Shield: A Zero-Cost Make.com Architecture

The Impact: High EMQ and Zero Monthly Fees

Wrap Up

Tidio for Shopify: Complete AI Live Chat Setup Guide (2026)

Why Tidio Works for Shopify Stores

Installation — 10 Minutes

Step 1: Install from the Shopify App Store

Step 2: Connect Your Shopify Store Data

Step 3: Configure the Chat Widget

Step 4: Set Up the Shopify Data Sidebar

Lyro AI Configuration — 20 Minutes

Step 1: Access the Lyro Configuration Panel

Step 2: Write FAQs for Actual Support Volume

Step 3: Upload Your FAQ Content

Step 4: Configure Escalation Rules

Step 5: Enable Lyro on Your Widget

Chatbot Flows for Common Queries

Fixing Shopify Google Ads Conversion Tracking: Server-Side Setup Without GTM

Why Browser Tracking Fails on Shopify

How Google Enhanced Conversions Works

The Architecture: Direct API Upload vs Server-Side GTM

Implementation Payload

How to Fix ‘Service Invoked Too Many Times’ in Google Apps Script 2026

What the Error Actually Means

The Root Cause in 95% of Cases: Row-by-Row Processing

Shopify Agentic Storefronts 2026 — Sell on ChatGPT & Google AI Mode (Setup Guide)

Shopify Agentic Storefronts 2026 — Sell on ChatGPT & Google AI Mode (Setup Guide)

Shopify Agentic Storefronts 2026 Sell on ChatGPT & Google AI Mode Complete Setup Guide

What Are Shopify Agentic Storefronts?

Who Is Eligible for Shopify Agentic Storefronts?

Which AI Platforms Does This Cover?

How to Set Up Shopify Agentic Storefronts (Step-by-Step)

The Knowledge Base App — What to Actually Write

1. FAQs — Write for the Questions AI Agents Get Asked

2. Return and Refund Policy (Detailed Version)

3. Brand Voice Guidelines

4. Shipping and Fulfilment Information

Replacing your tracking stack at the same time?

Optimising Your Product Data for AI Discovery

Product Title Formula

Product Description Requirements

Variant and Inventory Accuracy

Metafields for AI Context

Agentic Storefronts Limitations (March 2026)

How to Track Agentic Storefront Orders

Server-Side Tracking Setup (Required for Full Attribution)

What the Agentic Storefronts Dashboard Shows

Not Eligible Yet — 5 Things to Do Right Now

Want to replace your paid Shopify apps for free?

Shopify Agentic Storefronts — FAQ

Recover 20–40% of invisible Shopify conversions — free

Recover 20–40% of invisibleShopify conversions — free

Shopify Server-Side Tracking Explained in 60 Seconds

Quick answer table

What is Server Side Tagging (Shopify Server-Side Tracking)?

Server-side vs browser pixel: the architecture

Why Server-Side Tracking Is Non-Negotiable in 2026

How much data are you actually losing?

How iOS, Chrome and Safari Broke Browser Pixels: A Dated Timeline

April 2021 — iOS 14.5 and App Tracking Transparency

September 2021 — Safari ITP 2.3 enforcement on Shopify checkouts

October 2022 — iOS 16 link tracking parameter stripping

September 2023 — iOS 17 Link Tracking Protection

2024 — Google Consent Mode v2 mandatory in EEA

2025 — Chrome third-party cookie deprecation pivot

2026 — iOS 18 advanced fingerprinting protection and Apple Intelligence

Browser Pixel vs Server-Side CAPI vs Hybrid: Which Setup You Actually Need

Option 1 — Browser pixel only (Shopify default)

Option 2 — Server-side CAPI only (no browser pixel)

Option 3 — Hybrid: browser pixel + server-side CAPI with deduplication

The matrix

Event Match Quality Benchmarks: What "Good" Looks Like in 2026

The Meta EMQ scale, decoded

Match-key impact, ranked by lift

Google Enhanced Conversions match-rate benchmarks

TikTok Events API match scoring

Shopify Agentic Storefronts 2026
Sell on ChatGPT & Google AI Mode
Complete Setup Guide

Recover 20–40% of invisible
Shopify conversions — free