DEV Community: Luke Sandelands

6 Reasons Your Meta Conversions API Events Don't Match (and How to Check Yours)

Luke Sandelands — Tue, 29 Sep 2026 15:12:07 +0000

Server-side tracking is meant to fix the conversions a browser pixel loses. But a Conversions API event only helps if Meta can match it to a person, and a lot of setups send events that are accepted, counted as received, and then do much less than they should.

I build server-side tracking for Shopify stores, and the same six mistakes come up again and again. Every rule below comes from Meta's own Conversions API parameter documentation, read on 28 September 2026.

1. `event_time` is in milliseconds

Meta wants a Unix timestamp in seconds. JavaScript's Date.now() returns milliseconds, so it's the single most common bug:

event_time: Date.now()                    // wrong: 1727600000000
event_time: Math.floor(Date.now() / 1000) // right: 1727600000

A quick check: a timestamp in seconds has 10 digits. Thirteen digits means milliseconds.

2. Customer data is hashed before it's formatted

Meta requires email, phone, name, city, state, zip and country to be SHA-256 hashed. What catches people out is that Meta matches on the hash of the formatted value, and hashing doesn't forgive formatting:

sha256('Buyer@Example.com ') !== sha256('buyer@example.com')

Both are valid-looking 64-character hashes, so nothing flags the first one as wrong. Format first, then hash. Meta's rules:

Field	Format before hashing
`em`	Trim spaces, lowercase
`ph`	Digits only, no leading zeros, country code included
`fn`, `ln`	Lowercase, no punctuation
`ct`	Lowercase, no punctuation, special characters or spaces
`st`	Lowercase; US states as the 2-letter code
`zp`	Lowercase, no spaces or dashes; first 5 digits for US zips
`country`	Lowercase ISO 3166-1 alpha-2, such as `gb`

The UK phone trap. +44 (0)7700 900123 becomes 4407700900123 if you only strip symbols and leading zeros. The zero after the country code is a national prefix that isn't dialled internationally, so the number should be 447700900123. If your store sells in the UK, remove it before hashing.

3. Fields that must stay raw get hashed too

It's tempting to hash everything "to be safe". Meta says not to hash four fields:

client_ip_address
client_user_agent
fbc (the click ID cookie)
fbp (the browser ID cookie)

Meta uses these as they are. A hashed IP address is just a meaningless string.

4. Website events are missing the page URL or user agent

For events with action_source: "website", Meta requires both event_source_url and user_data.client_user_agent. Server-side setups often drop them, because the server never sees the browser. The fix is to capture both in the browser at checkout and pass them to your server with the order.

action_source itself is required on every event, as is user_data.

5. `event_id` is missing, or doesn't match the Pixel

Meta marks event_id as optional, but recommends it for deduplication. If the browser Pixel and your server both send the same purchase, give them the same ID so Meta can treat them as one event:

// Server
event_id: `order_${orderId}`

// Browser Pixel, same purchase
fbq('track', 'Purchase', { value, currency }, { eventID: `order_${orderId}` });

Without a shared ID, you're relying on Meta to work out that two events are the same purchase.

6. Old events are retried in a batch

If any event in a request is more than 7 days old, Meta returns an error for the whole request and processes none of its events. A retry queue that keeps resending one stale event can take good events down with it. Drop anything older than 7 days before it reaches the batch.

A Purchase event that gets all six right

import { createHash } from 'node:crypto';

const sha256 = (v) => createHash('sha256').update(v).digest('hex');
const email = (v) => v.trim().toLowerCase();
const phone = (v) => v.replace(/[^0-9]/g, '').replace(/^0+/, ''); // must already include the country code

const event = {
  event_name: 'Purchase',
  event_time: Math.floor(Date.now() / 1000),       // 1. seconds
  event_id: `order_${order.id}`,                    // 5. same ID as the Pixel
  action_source: 'website',
  event_source_url: pageUrl,                        // 4. captured in the browser
  user_data: {
    em: [sha256(email(order.email))],               // 2. formatted, then hashed
    ph: [sha256(phone(order.phone))],
    client_ip_address: clientIp,                    // 3. raw
    client_user_agent: userAgent,                   // 3. raw, and 4. required
    fbp,                                            // 3. raw
    fbc,                                            // 3. raw
  },
  custom_data: {
    value: Number(order.total),                     // required for Purchase
    currency: order.currency,                       // required for Purchase
  },
};

Check a payload in 10 seconds

I turned these checks into two free tools:

In the browser: paste an event into the Meta Conversions API payload validator. It runs locally, so nothing you paste is sent anywhere, and it has a formatter that applies Meta's rules and hashes the result.
In the terminal or CI: the open-source shopify-capi-validator package runs the same checks and exits with code 1 on any failure, so it can block a bad deploy.

npx shopify-capi-validator --payload ./event.json

If you're sending Shopify orders server-side for the first time, the server-side tracking setup guide covers the whole flow, and the EMQ score estimator shows what the customer data you send means for match quality.

Shopify to GA4 without GTM: native events plus a server-side Measurement Protocol fallback

Luke Sandelands — Sat, 26 Sep 2026 10:02:43 +0000

Google Analytics 4 installs on Shopify free through the official Google and YouTube sales channel, which handles browser-side event tracking without code or Google Tag Manager. Because browser events are lost to iOS and ad blockers, a Make.com webhook sending purchase events server-side completes the picture. Total setup takes under 20 minutes.

Questions this guide answers

How do I set up Google Analytics 4 on Shopify for free?

Install the Google & YouTube sales channel from the Shopify App Store (free) and connect your GA4 property during setup. Shopify automatically sends key ecommerce events (page_view, view_item, add_to_cart, begin_checkout, and purchase) to GA4 without any additional configuration. For more complete purchase data recovery, add a Make.com webhook that sends server-side purchase events to GA4's Measurement Protocol. The entire setup is free and requires no code or Google Tag Manager.

Do I need Google Tag Manager to connect Shopify to GA4?

No. Shopify's native Google & YouTube sales channel connects directly to GA4 without Google Tag Manager. GTM is an option for stores that need custom event tracking beyond Shopify's standard ecommerce events, but for the standard purchase, add-to-cart, and checkout events that most stores need, the native integration is sufficient and requires no technical setup.

What events does Shopify send to GA4 automatically?

When connected via the Google & YouTube sales channel, Shopify automatically sends the following GA4 events: page_view (every page load), view_item (product page views), add_to_cart (cart additions), begin_checkout (checkout started), add_payment_info (payment step), and purchase (order completed). These cover the complete ecommerce funnel without any additional configuration.

Why is my GA4 showing fewer purchases than Shopify?

GA4 purchase events are sent by the browser-based Shopify pixel, which is subject to iOS tracking restrictions, ad blockers, and cookie limitations. Stores with significant iOS traffic, users of privacy browsers, and customers using ad blockers will show fewer purchases in GA4 than Shopify actually recorded. The server-side fix is Make.com sending purchase events to GA4's Measurement Protocol directly: bypassing browser restrictions entirely.

Is Google Analytics 4 free for Shopify stores?

Yes. Google Analytics 4 is permanently free for standard use. There are no tier limits on the free version that would affect normal Shopify store analytics. Google Analytics 360 (the paid enterprise version) adds higher sampling thresholds and SLA guarantees: relevant only for extremely high-traffic stores. For the vast majority of Shopify stores, GA4 free provides complete analytics at no cost.

What is the difference between GA4 and Google Ads conversion tracking for Shopify?

GA4 is an analytics platform that tracks user behaviour across your entire Shopify store (sessions, page views, product views, cart events, and purchases) for analysis and reporting. Google Ads conversion tracking is specifically for attributing purchases back to Google Ads clicks to measure campaign performance. They are separate systems. GA4 can be linked to Google Ads to import key events as conversions, but setting them up separately ensures each works correctly. This guide covers GA4; the Google Ads conversion tracking setup is covered in a separate guide.

How long does it take to set up GA4 on Shopify?

The native GA4 setup via the Google & YouTube sales channel takes approximately 5 minutes. The additional server-side Make.com layer for complete purchase data recovery takes approximately 10 minutes. The full setup (native layer plus server-side layer plus verification) is complete in under 20 minutes with no technical skills required.

The full guide, with every step, source and date: Set Up Google Analytics 4 on Shopify Free 2026 — No Code

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

I replaced $700/month of SaaS with Google Apps Script. Here's what broke first.

Luke Sandelands — Mon, 14 Sep 2026 16:06:55 +0000

A while back I looked at a stack of SaaS subscriptions that were, between them, doing something fairly unglamorous: moving rows of data from one system into another and doing arithmetic on them. The combined bill was around $700 a month.

So I rewrote the lot in Google Apps Script and a webhook layer. It worked immediately, which was the problem — it worked at ten events a day and quietly stopped working at four hundred, in ways that produced no error email and no obvious symptom.

Here are the four things that broke, in the order they broke, and what actually fixed them.

1. Per-call service quotas, not row counts

The first version looked like every Apps Script tutorial:

function logEvents(events) {
  const sheet = SpreadsheetApp.getActiveSheet();
  events.forEach(e => {
    sheet.appendRow([e.id, e.timestamp, e.amount, e.source]);
  });
}

This is fine for ten rows and fatal for a thousand. appendRow is a service call, and Apps Script quotas count service calls, not rows. Four hundred appends is four hundred round trips to the Sheets backend, each with its own latency, and you hit Service invoked too many times for one day long before you hit anything resembling a real data volume.

One call instead of four hundred:

function logEvents(events) {
  if (!events.length) return;
  const sheet = SpreadsheetApp.getActiveSheet();
  const rows = events.map(e => [e.id, e.timestamp, e.amount, e.source]);
  sheet
    .getRange(sheet.getLastRow() + 1, 1, rows.length, rows[0].length)
    .setValues(rows);
}

Same output, one service call. This single change took a script that died daily to one that hasn't hit a quota in months.

The general rule: in Apps Script, anything that touches SpreadsheetApp, DriveApp, GmailApp or UrlFetchApp inside a loop is a bug waiting for volume. Build the array in memory, write once.

2. Duplicate writes, because webhooks retry

Every webhook provider retries on non-2xx, and some retry on timeout even when your handler succeeded. If your endpoint takes 30 seconds because of point 1 above, you will get the same event twice, and you will write it twice.

You need idempotency, and you need it at the write layer rather than the transport layer — you cannot control how many times you get called, only what you do about it.

function handleEvent(event) {
  const cache = CacheService.getScriptCache();
  const key = 'evt_' + event.id;

  if (cache.get(key)) return;        // already processed
  cache.put(key, '1', 21600);        // 6h TTL, the cache maximum

  writeEvent(event);
}

CacheService is the right tool here rather than PropertiesService, because it expires on its own and you are not trying to keep a permanent ledger — you are trying to survive a retry storm that lasts seconds. For anything needing a longer window, reconcile against the sheet itself on a nightly trigger and dedupe on the ID column.

One caveat worth knowing: CacheService is best-effort and can evict early under pressure. It is a retry guard, not a correctness guarantee. If duplicates are genuinely unacceptable, you need the nightly reconciliation as well.

3. Concurrent executions racing for the same row

Two webhooks arriving 200ms apart both call getLastRow(), both get 4,102, and both write to row 4,103. One of them wins. The other event is gone, with no error anywhere.

This is the failure mode that cost me the most time, because it produces silent, occasional data loss that you only notice weeks later when a total doesn't reconcile.

function writeEvent(event) {
  const lock = LockService.getScriptLock();

  try {
    lock.waitLock(30000);            // throws if it can't acquire
    appendRows([event]);
  } catch (e) {
    console.error('Lock timeout, requeueing: ' + event.id);
    queueForRetry(event);            // don't silently drop it
    return;
  } finally {
    lock.releaseLock();
  }
}

getScriptLock() rather than getUserLock() — the lock needs to span every execution of the script, not every execution by a given user. And note the finally: an early return inside the try block without releasing the lock will stall every subsequent execution for the full 30 seconds.

4. The six-minute wall

Apps Script kills any execution at six minutes. If you are backfilling, migrating, or processing a queue that grew overnight, you will hit this, and the execution dies mid-write with no transaction to roll back.

The pattern is checkpointing: process until you are near the limit, save your position, schedule a continuation, exit cleanly.

const MAX_RUNTIME_MS = 4.5 * 60 * 1000;   // leave 90s of headroom

function processQueue() {
  const start = Date.now();
  const props = PropertiesService.getScriptProperties();
  let cursor = Number(props.getProperty('cursor') || 0);

  const items = getQueue();

  while (cursor < items.length) {
    if (Date.now() - start > MAX_RUNTIME_MS) {
      props.setProperty('cursor', String(cursor));
      scheduleContinuation();
      return;
    }
    processItem(items[cursor]);
    cursor++;
  }

  props.deleteProperty('cursor');            // finished cleanly
}

function scheduleContinuation() {
  ScriptApp.newTrigger('processQueue')
    .timeBased()
    .after(60 * 1000)
    .create();
}

There's more to this than one code block holds once you're processing a backlog rather than a steady queue — batch sizing, resumability after a failed continuation, and reconciling a partial run. I wrote those up separately in scalable Google Sheets automation for high-volume workflows.

Two things that bite people here. The headroom matters — if your per-item work takes eight seconds, a 30-second buffer isn't enough and you'll die mid-item. And time-based triggers are themselves a quota'd resource, capped at 20 per script, so delete the trigger once it has fired or you will accumulate orphans until trigger creation starts failing.

function deleteTriggersFor(handlerName) {
  ScriptApp.getProjectTriggers()
    .filter(t => t.getHandlerFunction() === handlerName)
    .forEach(t => ScriptApp.deleteTrigger(t));
}

The backoff you need for external calls

Worth adding for anything calling an external API, since transient 429s and 503s will otherwise surface as permanent failures:

function fetchWithBackoff(url, params, maxAttempts = 5) {
  for (let attempt = 0; attempt < maxAttempts; attempt++) {
    const res = UrlFetchApp.fetch(url, {
      ...params,
      muteHttpExceptions: true
    });
    const code = res.getResponseCode();

    if (code < 400) return res;
    if (code < 500 && code !== 429) return res;   // real client error, don't retry

    const backoff = Math.pow(2, attempt) * 1000;
    const jitter = Math.floor(Math.random() * 1000);
    Utilities.sleep(backoff + jitter);
  }
  throw new Error('Max retries exceeded: ' + url);
}

The jitter is not decoration. Without it, every one of your parallel executions retries at exactly the same moment and you rebuild the thundering herd you were trying to avoid.

What I'd tell myself at the start

The SaaS tools I replaced were not charging $700 a month for the arithmetic. They were charging for the four things above — retry handling, deduplication, concurrency safety, and job continuation — which is genuinely the hard part and which is invisible until you are running at volume.

That doesn't make the replacement a bad trade. It cost me maybe 40 hours of debugging spread over a few months, against roughly $8,400 a year, and I now own the thing outright and can read every line of it. But it's a real trade, not a free lunch, and anyone who tells you a Sheets-and-webhooks stack "just replaces" a SaaS subscription has not yet run it at four hundred events a day.

If you're doing something similar: write these four patterns in before you have the volume that proves you needed them. The failures are silent, and by the time you notice, the missing data is already weeks old.

What's the most annoying quota wall you've hit in Apps Script? I'm fairly sure I haven't found all of them yet.

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

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

CAPI Shield is a free Make.com scenario that takes each paid Shopify order from a webhook and sends it to Meta's Conversions API as a Purchase event, so iOS, Safari and ad blockers cannot stop it. This page is the setup. If your Meta results dropped and you do not yet know why, start with the ROAS guide.

Questions this guide answers

What is the Shopify CAPI?

The Shopify CAPI refers to server-side Conversions API implementation for Shopify: sending purchase events from Shopify's servers directly to Meta CAPI, Google Enhanced Conversions, or TikTok Events API. It bypasses iOS privacy restrictions and ad blockers that block browser pixel tracking, covering purchase events that would otherwise be missed.

What is Shopify server-side tracking?

Server-side tracking sends Shopify conversion events directly from your server to ad platforms, bypassing the browser entirely. iOS restrictions, ad blockers, and cookie expiry cannot interfere. CAPI Shield implements this free via Make.com webhooks: the webhook fires from Shopify's backend the moment an order is paid, completely independent of browser behaviour.

How to set up Shopify server-side tracking free?

Use CAPI Shield: a free Make.com scenario that routes Shopify order webhooks to Meta Conversions API. Sign up for Make.com free, create a scenario with a Webhooks trigger, add the Meta Conversions API request, create a Shopify Order Payment webhook pointing to your Make.com URL, and test with a sample order. Takes 6 minutes, no code required, free forever on Make.com's free tier.

What is Google Enhanced Conversions and how does it work with Shopify?

Google Enhanced Conversions is Google's server-side conversion tracking system. It supplements your standard Google Ads conversion tags by sending hashed first-party customer data (email, phone, name) alongside each conversion event. Google uses this to match conversions to Google accounts with greater accuracy, improving Smart Bidding and Performance Max optimisation even when cookies and pixels are blocked by iOS or ad blockers. CAPI Shield's Google branch is not a working route to it as shipped: it uploads a click conversion keyed on a Google click ID, and Shopify's order data has no field for one. Google is also moving this upload method, offline click conversion import, out of the Google Ads API and into its Data Manager API, and Make's Google Ads module now warns that uploads may fail for developer tokens that have not recently sent click conversions. Its two consent fields must be set to match your own consent setup.

What is Meta CAPI and how does it work with Shopify?

Meta Conversions API (CAPI) is a server-to-server connection that sends Shopify purchase events directly to Meta without going through the browser. CAPI Shield sets this up free using Make.com, sending hashed email, phone, name, IP and user-agent with every event: the match-key set Meta scores Event Match Quality against, and a larger one than the browser pixel carries.

How much conversion data am I losing without server-side tracking?

We do not publish a number, because the honest answer is specific to your store: the loss is driven by how much of your traffic is mobile and iOS, and how many of those visitors decline tracking. Measure yours instead. The Shopify vs Meta Attribution Gap Calculator turns your Ads Manager conversion count and your Shopify order count into your own gap; the Meta EMQ Score Estimator scores the match quality of what you are currently sending; and the Shopify iOS Attribution Gap Benchmark publishes the sourced figures behind the mechanism. After CAPI Shield deployment most stores see an immediate increase in reported conversions in Meta Events Manager within 24–48 hours.

Does CAPI Shield replace my Meta Pixel?

No. CAPI Shield works alongside your existing Meta Pixel, not instead of it. The pixel still captures upper-funnel events like ViewContent and AddToCart. CAPI Shield adds server-side Purchase events on top. Both fire simultaneously and Meta deduplicates them automatically using the event_id included in every server event.

What is the difference between CAPI Shield and Elevar or Northbeam?

Elevar's Core plan is $225/month, and Northbeam lists its Starter plan at $1,500 with every plan quoted through a sales call. CAPI Shield uses Make.com to achieve the same server-side event forwarding for free. The core technical outcome, server-side purchase events reaching Meta CAPI, is identical. Elevar and Northbeam add analytics dashboards on top. If you only need conversion recovery, CAPI Shield is the free equivalent.

Will CAPI Shield improve my ROAS?

Indirectly, yes. CAPI Shield gives Meta complete purchase data. Advantage+ Shopping uses conversion signals to optimise delivery. Most stores see measurable ROAS improvement within 14–21 days as the algorithm relearns with full data.

What is Event Match Quality and why does it matter?

Event Match Quality (EMQ) is Meta's 0–10 score for how well server-side events are matched to Meta user accounts. Scores above 7.0 indicate strong matching. CAPI Shield sends hashed email, phone, name, IP and user-agent with every event. More match keys give Meta more to match on, which is what the score measures. We have not sampled EMQ across stores, so we do not publish a typical score: the EMQ estimator projects a range from your own parameter set.

Is CAPI Shield GDPR compliant?

The data flows through your own Make.com workspace. CAPI Shield hashes all personally identifiable information (email, phone, name) before transmission using SHA-256, as required by Meta's Conversions API specification. Ensure your store's privacy policy covers server-side tracking data sharing.

How long does CAPI Shield setup take?

Most stores are fully live within 6 minutes. The Make.com scenario takes 3–4 minutes to configure. The Shopify webhook takes under 2 minutes. Testing takes 1–2 minutes. No developer, no code, no infrastructure required.

Why is Shopify's built-in CAPI not enough?

Shopify's native CAPI is still browser-triggered: the thank-you page Web Pixel must execute before the server event fires. If a browser blocks the Web Pixel, the server event may not fire. CAPI Shield uses a server-to-server webhook that fires from Shopify's backend the moment payment is confirmed, regardless of browser behaviour, and it sends a larger match-key set than the native integration does. We have not benchmarked the two side by side, so we put no scores on either.

Does this work with TikTok Ads as well?

Yes. The same Make.com scenario can route events to Meta CAPI and TikTok Events API from one webhook. Most stores start with Meta, then add TikTok as a second branch if they advertise there: using the same webhook trigger, no additional Shopify setup required.

Which Graph API version does CAPI Shield use?

The Meta request names a Graph API version in its URL. Meta retires each version about two years after release, and requests to a retired version fail. Check the version in your scenario's URL against Meta's Graph API changelog and update it before it expires, then send one test order to confirm events still arrive.

What happens if I want to remove CAPI Shield?

Delete the Make.com scenario and the Shopify webhook. Nothing is installed on your Shopify store. Data stops flowing immediately. No residue, no lock-in, no cancellation fees.

The full guide, with every step, source and date: Meta CAPI for Shopify — CAPI Shield, Free Server-Side Setup

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

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

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

Tidio installs on Shopify from the App Store, and its Lyro AI answers order-status, shipping and product questions automatically. Tidio says Lyro resolves 67% of conversations instantly (tidio.com); that is Tidio's figure, not one we measured. The free plan covers live chat, a basic bot and Shopify order lookup. Full setup, including Lyro training, takes about 30 minutes.

Questions this guide answers

Is Tidio free for Shopify?

Yes. Tidio's free plan includes live chat, basic chatbot flows, and 50 one-time Lyro AI conversations (a trial allowance, not a monthly one). Whether that is enough depends on how many conversations your store handles each month, not on its revenue. Paid plans extend the Lyro AI conversation limit and add advanced features.

Can Tidio replace Gorgias for Shopify?

Yes, for most stores. Tidio says Lyro resolves 67% of conversations instantly (tidio.com). Lyro handles order status, shipping questions and product FAQs without human intervention. Gorgias lists its Starter plan at $40/month billed monthly, of which $10 is the helpdesk and $30 its AI Agent (gorgias.com/pricing, read 25 September 2026). Tidio's free tier is permanently functional, not a crippled trial.

How does Tidio Lyro AI work?

Lyro AI is a generative language model trained on your FAQ content and Shopify product catalogue. It reads customer queries and responds using your knowledge base content, resolving queries without human agents. Unresolved queries are escalated to a human agent automatically. Setup involves uploading FAQ content in the Lyro configuration panel.

Does Tidio integrate with Shopify orders?

Yes. Tidio's native Shopify integration pulls live order data (order status, tracking numbers, fulfilment status, and purchase history) directly into the chat sidebar. Both Lyro AI and human agents can see this data without switching systems.

What is the Tidio Lyro AI resolution rate?

Tidio says Lyro resolves 67% of conversations instantly (tidio.com). That is Tidio's own figure, not one we measured. Your rate depends mostly on how complete the knowledge base is and how queries are routed, which is what the weekly tuning routine in this post works on.

The full guide, with every step, source and date: Tidio for Shopify: Free AI Live Chat Setup Guide 2026

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

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

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

Google Ads under-reports Shopify purchases because its conversion tag fires in the browser, where iOS restrictions and ad blockers stop it. A server-side upload through a Make.com webhook can add hashed customer email, but Shopify's order data carries no Google click ID, so what Google can match depends on how your conversion action is set up.

Questions this guide answers

Why is my Shopify Google Ads conversion tracking wrong in 2026?

Three causes account for most Google Ads attribution gaps on Shopify in 2026: iOS Link Tracking Protection stripping gclid click IDs from URLs before customers open them in Safari, Mail, or Messages; Safari Intelligent Tracking Prevention (ITP) clearing attribution cookies before the purchase completes; and ad blockers preventing the gTag from loading. Server-side Google Enhanced Conversions fixes all three because events are sent from Shopify's server to Google directly, bypassing the browser.

What is Google Enhanced Conversions for Shopify?

Google Enhanced Conversions is Google's server-side conversion tracking supplement. It sends hashed first-party customer data (email, phone, name) alongside each conversion event via API. Google uses this to match conversions to signed-in Google accounts with greater accuracy, improving Smart Bidding and Performance Max optimisation even when cookies and gclid are blocked. For Shopify stores, it carries purchase events that the browser-based gTag misses when iOS and Safari strip the click ID or clear the cookie. We have not measured what share of events that is, and are not aware of a published figure for Google Ads specifically, so this page does not quote one.

How do I set up Google Ads conversion tracking on Shopify for free?

The free two-layer approach: first, ensure the Google & YouTube sales channel is installed in Shopify for baseline browser-side tracking. Then add Google Enhanced Conversions via Make.com: create a Make.com free account, add a Webhooks module as the trigger, create a Shopify Order payment webhook pointing to your Make.com URL, add an HTTP module calling the Google Ads Conversions API endpoint, and hash customer email and phone with SHA-256. Full setup takes 6 minutes. No code, no GTM, no paid apps.

What is GCLID and why does it matter for Shopify Google Ads?

GCLID (Google Click ID) is the unique identifier Google appends to your ad URLs when someone clicks an ad: for example, ?gclid=CjwKCAjw8. Shopify's thank-you page uses this ID to attribute the purchase back to the specific Google Ads click. When iOS Link Tracking Protection or Safari ITP strips or clears the gclid, the conversion is unattributed. Google's Enhanced Conversions adds hashed customer data to help Google match purchases. A server-side upload built on Shopify's Order payment webhook has no gclid to send, because Shopify's order data has no field for one, so whether Google matches it depends on how your conversion action is set up.

Do I need Google Tag Manager for Shopify Google Ads conversion tracking?

No. The Make.com approach sends Google Enhanced Conversions events directly to the Google Ads Conversions API via HTTP request: no Google Tag Manager container required. GTM is one implementation route. Direct server-to-server API calls via Make.com are simpler and more reliable for Shopify stores because the entire flow operates without a browser.

What is the difference between standard conversion tracking and Enhanced Conversions?

Standard Google Ads conversion tracking fires a browser-based gTag when the order confirmation page loads. It fails when iOS or Safari blocks the gclid, when ad blockers prevent the gTag from loading, or when the browser session expires before the customer reaches the thank-you page. Google Enhanced Conversions supplements this by sending hashed customer data server-to-server, independently of browser state. Running both simultaneously gives Google the most accurate conversion picture.

How do I fix Google Ads showing fewer conversions than Shopify?

If Google Ads reports significantly fewer conversions than Shopify shows orders for the same period, you are losing attribution due to iOS restrictions or ad blockers. A server-side upload via Make.com runs independently of the browser, but it only helps if Google can match what it sends: Shopify's order data has no Google click ID, so the upload carries hashed customer email alone, and whether Google accepts that depends on how your conversion action is set up.

Will server-side Google Ads tracking improve my Smart Bidding performance?

Yes. Smart Bidding, Target ROAS, and Performance Max all optimise based on the conversion signals Google receives. When real conversions are invisible due to browser-based tracking failures, the algorithm is bidding on incomplete data: underbidding on high-intent traffic and over-bidding on low-converting segments. Completing conversion data with server-side Enhanced Conversions typically improves Smart Bidding performance within 14–21 days as the model relearns with full data.

Does this work alongside my existing Google Ads conversion tag?

Yes. Google Enhanced Conversions is designed to supplement, not replace, your existing conversion tags. The browser-side gTag continues to fire as normal. The server-side Enhanced Conversions layer adds hashed customer data on top. Google automatically deduplicates events using the order ID, so the same purchase is not counted twice. Running both layers together gives maximum conversion accuracy.

How much does it cost to fix Google Ads conversion tracking on Shopify?

The complete free setup costs $0/month. The Make.com free plan (1,000 credits/month (formerly called operations)) covers Enhanced Conversions for stores processing under 500 orders per month. Above that, Make.com Core at $9/month covers 10,000 credits. Every paid alternative, Stape ($17/month billed yearly), Littledata ($159+/month), Analyzify ($145–$275/month), charges a monthly subscription for the same server-side outcome Make.com delivers free.

Is this GDPR compliant?

All customer PII (email, phone, name) is hashed with SHA-256 inside Make.com before transmission to Google, as required by Google's Enhanced Conversions specification. The hashed data flows through your own Make.com workspace. Ensure your privacy policy discloses that hashed customer data is shared with Google for conversion matching purposes.

The full guide, with every step, source and date: Fix Shopify Google Ads Tracking — Free Setup 2026

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

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

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

Google Apps Script stops any single execution after six minutes, on consumer and Workspace accounts alike. Daily quotas depend on the account: triggers may run for 90 minutes a day on a consumer account and six hours on Workspace. No setting or support request raises them, which is why heavy Autocrat and Sheets automations eventually fail.

Questions this guide answers

What is the Google Apps Script execution time limit in 2026?

Both consumer (free) and Google Workspace accounts are capped at 6 minutes per execution in 2026: the 30-minute Workspace limit cited by older guides no longer applies. Scripts that exceed the limit are hard-stopped mid-run: no graceful shutdown, no warning, just termination.

What is the daily runtime limit for Google Apps Script in 2026?

Google's official quota for triggers total runtime is 90 minutes per day on consumer accounts and 6 hours per day on Workspace accounts. This applies to trigger-driven executions; manual runs are not counted. The quota resets 24 hours after the first request.

What is the Google Apps Script UrlFetch daily limit?

Consumer accounts can make 20,000 UrlFetch calls per day. Google Workspace accounts get 100,000 per day. If your automation calls external APIs on every order, this limit can be exhausted faster than expected on high-volume days.

Have Google Apps Script quotas changed for 2026?

The core limits, 6-minute execution (both consumer and Workspace) and 90-minute daily trigger runtime on consumer accounts, have remained consistent into 2026. Google does not announce quota changes prominently. If you are seeing new failures, it is more likely that your volume has grown into the limits rather than that Google has tightened them.

Can Google Apps Script quotas be increased?

Not by request or configuration. Google publishes one set of figures for consumer accounts and a higher set for Google Workspace accounts, so moving to Workspace raises the daily quotas, such as trigger runtime and URL Fetch calls. The six-minute limit per execution is the same on both. To work beyond it, move the work outside Apps Script, into Make.com or a dedicated API layer.

Why does my script work in the morning but fail in the afternoon?

This is the clearest sign of a daily quota problem. Trigger-driven automations are exhausting the 90-minute daily trigger runtime (consumer) in the first half of the day, leaving nothing for afternoon processing. The quota resets 24 hours after the first request, which is why timing shifts day to day.

Why does the same script work one day and fail the next?

Variable load. A day with higher order volume or more form submissions hits limits that a quieter day never reached. The script did not change: the pressure on its quota allowance did.

Is Apps Script still useful for automation in 2026?

Yes: as a lightweight trigger and orchestration layer for simple spreadsheet actions and low-volume workflows. It becomes a liability when it is the execution engine for mission-critical, high-volume processing. For those cases, Make.com is the right tool.

The full guide, with every step, source and date: Google Apps Script Quotas 2026 — Every Limit Explained

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

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

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

Shopify Agentic Storefronts connect your catalog to ChatGPT, Google AI Mode, Microsoft Copilot and Meta from one admin setting. Since 24 March 2026 the channels split: Google, Copilot and Meta complete checkout inside the AI surface, while ChatGPT redirects shoppers to your own Shopify checkout, which is why most limits apply to only some channels.

Questions this guide answers

What are Shopify Agentic Storefronts?

Shopify Agentic Storefronts connect your product catalog to AI assistants (ChatGPT, Google AI Mode and Gemini, Microsoft Copilot, and Meta surfaces such as Muse) through one setting in your Shopify admin, with no separate integration per platform. What each channel then does with a shopper differs: Google, Copilot and Meta complete the purchase inside their own interface, while ChatGPT sends the shopper to your own Shopify checkout. Announced in Shopify's Winter '26 Edition on 10 December 2025 and generally available to eligible merchants from 24 March 2026.

Does ChatGPT still let customers buy without leaving the chat?

No. OpenAI retired Instant Checkout on 24 March 2026, and Shopify’s documentation now describes ChatGPT as a discovery-focused referrer: shoppers complete the purchase on your own Shopify checkout, opened in the ChatGPT in-app browser or a new tab. This matters more than it sounds. Because the transaction happens on your checkout, the product-type restrictions, fulfilment restrictions and pixel restrictions that apply to direct checkout do not apply to ChatGPT traffic at all: your normal checkout rules and your client-side pixels work as they always have. Guides published before 24 March 2026 describe the opposite arrangement.

Am I eligible for Shopify Agentic Storefronts?

Eligibility is per channel, not one blanket rule, and it stacks two separate conditions: where your store is based, and where you sell. ChatGPT and Microsoft Copilot accept a store based in any country provided it sells to customers in the United States; Meta accepts one that sells to customers in the United States, Canada or Mexico. Google AI Mode and Gemini require the store itself to be based in the United States and to sell to customers there, and direct checkout renders only for US-based customers, with everyone else redirected to the store. So a UK-based store cannot use Google, but can use ChatGPT and Copilot if it sells to US customers, and Meta if it sells to customers in the US, Canada or Mexico. Google is still rolling out, and its product discovery runs on Google Merchant Center, which Shopify feeds through the Google & YouTube sales channel. Agentic storefronts are active by default for eligible stores; the setting lives under Sales channels, then Agentic.

How much does the Shopify Knowledge Base app cost?

It is free. The Shopify Knowledge Base app is published by Shopify, launched on 16 May 2025, and its App Store listing shows no paid tier and no Plus-only pricing. Guides quoting a monthly fee for standard plans appear to be describing third-party knowledge-base apps instead. The app is not visible on your storefront: your FAQs serve as a data source that AI platforms read when answering questions about your products.

Which products cannot be sold through Agentic Storefronts?

Subscriptions, product bundles, customizable products and B2B-only products are not supported in agentic storefront direct checkouts. Local delivery, pickup in store and pickup points are not available as delivery methods, and custom checkout fields, checkout upsells, checkout validations, a subset of accelerated checkout options and requiring customer sign-in do not work either. Every one of those restrictions applies to the direct-checkout channels only: Google, Copilot and Meta. ChatGPT sends shoppers to your own checkout, where none of them apply.

Do discount codes work in agentic checkout?

Yes. Shopify’s documentation states that automatic discounts and discount codes you set up are both supported in agentic storefront direct checkouts. Several widely-shared guides claim the opposite; that claim does not match Shopify’s current documentation.

Will Google Analytics and my Meta pixel track agentic orders?

Not in direct checkout. Shopify states that Google Analytics and custom pixels will not fire there: only server-to-server pixels for the started and completed events. So an order placed inside Google AI Mode, Copilot or Meta reaches your Shopify admin but arrives in GA4 and Meta Ads Manager with no client-side event behind it. If you buy ads and measure return on ad spend from browser pixels, those orders look like they came from nowhere. Server-side tracking is the fix, and it is worth having in place before you enable the channels rather than after. ChatGPT is unaffected: that checkout is yours, so your pixels fire normally.

Does Shopify charge a fee for selling through AI channels?

No. Shopify’s documentation states there are no fees associated with selling in ChatGPT, in Google AI Mode and Gemini’s direct checkout, or in agentic storefront direct checkouts generally. You pay your standard payment processing fees and nothing further. Shopify also offers a separate free Agentic plan aimed at merchants who do not use Shopify as their primary storefront; it excludes the Online Store, gift cards, manual orders and Shop post-purchase offers.

Is Perplexity a Shopify agentic channel?

No, despite appearing in Shopify’s December 2025 launch announcement. In-chat buying on Perplexity runs on PayPal Instant Buy, those orders are managed through PayPal rather than your Shopify admin, and merchants apply to the Perplexity Merchant Program separately. Perplexity is no longer listed as an Agentic Storefronts channel in Shopify’s help documentation. Guides presenting it as a Shopify channel with redirect checkout are describing an arrangement that does not exist.

My store is not eligible yet. Is any of this worth doing now?

Yes, because discovery already happens without it. AI assistants crawl the web and read Shopify Catalog regardless of your agentic settings: what the feature adds is the checkout, not the visibility. Four things pay off immediately: install and populate the free Knowledge Base app, complete your product data so AI assistants can match products to conversational queries, add FAQPage structured data to your content, and get server-side tracking working so you have no attribution gap on the day the channels switch on.

The full guide, with every step, source and date: Shopify Agentic Storefronts — Eligibility & Limits 2026

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

Shopify Server-Side Tracking Setup — Step by Step

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

Setting up Shopify server-side tracking means connecting a Shopify orders/paid webhook to a free Make.com scenario: the webhook fires when an order is paid, Make.com hashes the customer data with SHA-256, then posts the event to Meta Conversions API, Google Enhanced Conversions, and TikTok Events API. A full three-platform build takes about 18 minutes, no code required.

Questions this guide answers

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?

We publish no recovery percentage, and no honest one exists as an industry figure: what server-side tracking recovers is whatever your browser pixel was losing, which is set by your own mobile/iOS traffic mix and consent rate. Measure it as Additional Conversions Reported in Meta Events Manager, or with the attribution gap calculator, and see why the 20–40% estimate was retracted. 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; that is Meta's figure across its advertisers, not a measurement of your store.

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 uses 4 Make.com credits (the webhook trigger plus one each for Meta, Google and TikTok) and the free tier covers 1,000 credits monthly. Above that, the Make.com Core plan at $9/month covers 10,000 credits: enough for roughly 2,500 orders/month at 4 credits each (make.com/en/pricing, read 25 September 2026). Managed alternatives like Elevar (from $225/month) and Triple Whale (priced by store revenue) 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. The score rises with the number of match keys an event carries. The Make.com webhook method sends 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).

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. Send all four high-impact signals (email, phone, IP/UA, external_id): that is the full set TikTok calculates the score from. We publish no figure for what it scores; read yours in TikTok Events Manager.

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 $9/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 $225/month and Triple Whale prices by store revenue, 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 $225/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.

The full guide, with every step, source and date: Shopify Server-Side Tracking Setup — Step by Step

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

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

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

Questions this guide answers

What is the Google Apps Script execution time limit in 2026?

What is the daily runtime limit for Google Apps Script in 2026?

What is the Google Apps Script UrlFetch daily limit?

Have Google Apps Script quotas changed for 2026?

Can Google Apps Script quotas be increased?

Why does my script work in the morning but fail in the afternoon?

Why does the same script work one day and fail the next?

Variable load. A day with higher order volume or more form submissions hits limits that a quieter day never reached. The script did not change: the pressure on its quota allowance did.

Is Apps Script still useful for automation in 2026?

The full guide, with every step, source and date: Google Apps Script Quotas 2026 — Every Limit Explained

Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.

DEV Community: Luke Sandelands

6 Reasons Your Meta Conversions API Events Don't Match (and How to Check Yours)

1. event_time is in milliseconds

2. Customer data is hashed before it's formatted

3. Fields that must stay raw get hashed too

4. Website events are missing the page URL or user agent

5. event_id is missing, or doesn't match the Pixel

6. Old events are retried in a batch

A Purchase event that gets all six right

Check a payload in 10 seconds

Shopify to GA4 without GTM: native events plus a server-side Measurement Protocol fallback

Questions this guide answers

How do I set up Google Analytics 4 on Shopify for free?

Do I need Google Tag Manager to connect Shopify to GA4?

What events does Shopify send to GA4 automatically?

Why is my GA4 showing fewer purchases than Shopify?

Is Google Analytics 4 free for Shopify stores?

What is the difference between GA4 and Google Ads conversion tracking for Shopify?

How long does it take to set up GA4 on Shopify?

I replaced $700/month of SaaS with Google Apps Script. Here's what broke first.

1. Per-call service quotas, not row counts

2. Duplicate writes, because webhooks retry

3. Concurrent executions racing for the same row

4. The six-minute wall

The backoff you need for external calls

What I'd tell myself at the start

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

Questions this guide answers

What is the Shopify CAPI?

What is Shopify server-side tracking?

How to set up Shopify server-side tracking free?

What is Google Enhanced Conversions and how does it work with Shopify?

What is Meta CAPI and how does it work with Shopify?

How much conversion data am I losing without server-side tracking?

Does CAPI Shield replace my Meta Pixel?

What is the difference between CAPI Shield and Elevar or Northbeam?

Will CAPI Shield improve my ROAS?

What is Event Match Quality and why does it matter?

Is CAPI Shield GDPR compliant?

How long does CAPI Shield setup take?

Why is Shopify's built-in CAPI not enough?

Does this work with TikTok Ads as well?

Which Graph API version does CAPI Shield use?

What happens if I want to remove CAPI Shield?

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

Questions this guide answers

Is Tidio free for Shopify?

Can Tidio replace Gorgias for Shopify?

How does Tidio Lyro AI work?

Does Tidio integrate with Shopify orders?

What is the Tidio Lyro AI resolution rate?

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

Questions this guide answers

Why is my Shopify Google Ads conversion tracking wrong in 2026?

What is Google Enhanced Conversions for Shopify?

How do I set up Google Ads conversion tracking on Shopify for free?

What is GCLID and why does it matter for Shopify Google Ads?

Do I need Google Tag Manager for Shopify Google Ads conversion tracking?

What is the difference between standard conversion tracking and Enhanced Conversions?

How do I fix Google Ads showing fewer conversions than Shopify?

Will server-side Google Ads tracking improve my Smart Bidding performance?

Does this work alongside my existing Google Ads conversion tag?

How much does it cost to fix Google Ads conversion tracking on Shopify?

Is this GDPR compliant?

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

Questions this guide answers

What is the Google Apps Script execution time limit in 2026?

What is the daily runtime limit for Google Apps Script in 2026?

What is the Google Apps Script UrlFetch daily limit?

Have Google Apps Script quotas changed for 2026?

Can Google Apps Script quotas be increased?

Why does my script work in the morning but fail in the afternoon?

Why does the same script work one day and fail the next?

Is Apps Script still useful for automation in 2026?

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

Questions this guide answers

What are Shopify Agentic Storefronts?

Does ChatGPT still let customers buy without leaving the chat?

Am I eligible for Shopify Agentic Storefronts?

How much does the Shopify Knowledge Base app cost?

1. `event_time` is in milliseconds

5. `event_id` is missing, or doesn't match the Pixel