A step-by-step framework to capture phone, in-store and manual sales from Shopify and attribute them to your paid and organic channels.

Image via 123RF
Fill out the form below and our team will get back to you within 24 hours
Here's what sets us apart from the competition
Find answers to common questions
Server-side tracking is recommended when you need more reliable event delivery, reduced loss from ad blockers or browser restrictions, and tighter control over data routing and PII. It is typically used alongside client-side tags to improve attribution accuracy and data governance.
Run tag and network debuggers, execute synthetic transactions through the full funnel, reconcile analytics events to backend order and revenue data, and set automated alerts for event drops or source discrepancies. Regular audits of event naming, parameter consistency, and ETL integrity help maintain long-term measurement quality.
We implement consent-aware tag firing, server-side proxies, and cookieless or modeled measurement techniques so key funnel signals are preserved without overriding user choices. All modeled data is labelled in reports to separate observed from inferred metrics.
A typical implementation maps enhanced eCommerce events to a consistent dataLayer, deploys GA4 via Google Tag Manager with optional server-side forwarding, and funnels raw events into BigQuery for attribution, reporting, and downstream ETL. This ensures events are structured for revenue-focused analysis rather than just traffic metrics.
We consolidate events through GA4, server-side tagging, and a central data pipeline (BigQuery/ETL) to reconcile platform conversions with backend revenue. Deterministic identifiers and consistent event schemas reduce discrepancies between platform-reported and first-party data.
In This Article
Capture identifiers
Server-side uploads
Reconcile and act
Offline conversion tracking on Shopify closes the attribution gap between recorded web conversions and revenue events that happen outside the checkout flow - phone orders, email invoices, in-person POS sales, or manually recorded B2B orders. For US-based founders and marketing teams, accurate offline conversion tracking improves CAC calculations, informs budget decisions across Google Ads and Meta, and protects your customer lifetime value assumptions.
This guide walks through steps to implement offline conversion tracking on Shopify using server-side uploads (Google Ads offline uploads or GA4 Measurement Protocol), Shopify order metadata, and clean attribution. Before you start, confirm:
To match offline events to ad clicks or sessions, capture identifiers at the point of first contact or checkout. Store gclid, fbclid, or other click IDs in an order-level metafield or note attribute when a visitor arrives with those parameters. If you use server-side tagging, also persist first-party identifiers (client id or user id) in your customer records.
Create a clear internal process to flag orders as offline conversions. That may be a specific order tag (e.g., offline-sale), a custom payment gateway label, or a metafield indicating 'sales_channel=offline'. Consistent tagging lets your ETL or upload script filter and process only the relevant orders for offline attribution.
Note: storing click identifiers and customer emails has privacy implications. Implement minimal retention, hashed identifiers where possible, and a consent-aware workflow respecting CCPA and other US privacy rules.
Want to see how these steps fit into a wider growth system? Explore our service overview for analytics and tracking to understand strategy and technical build options: Prebo Digital services.
Two common server-side options for offline conversion tracking on Shopify are:
For many Shopify stores, the most reliable path is a server that receives Shopify webhooks, enriches orders with stored click identifiers, hashes PII where required, formats conversion payloads, and uploads them via the ad platform API or the GA4 endpoint.
If you want an implementation blueprint or examples tailored to Shopify and server-side tracking, learn about our agency approach and frameworks: About Prebo Digital.
When preparing uploads, include these fields where possible: order_id, conversion_time (ISO 8601), conversion_value (US$), currency, gclid or click_id, and customer identifiers (email or phone) hashed with SHA256 when the platform requires. Hashing decreases risk while enabling deterministic matching.
Implement a scheduled batch job or near-real-time uploader. For reliability:
Shopify order tagged (offline) ↓Webhook → ETL server ↓Enrich with gclid / hashed email ↓Format payload → Upload to Google Ads or GA4 ↓Platform matches offline conversion → Attribution updated
After uploads, validate that conversions appear in the ad platform and reconcile totals against Shopify sales reports. Expect a partial match rate (varies by channel and how completely identifiers are captured). Use reconciled figures to update CAC and MER calculations - for example, adding $5,000 of offline attributed revenue to a $50,000 ad spend changes MER and LTV/CAC assessments.
In the United States, state privacy laws like CCPA impose requirements on personal data collection and deletion. When capturing and uploading PII (emails, phones), follow minimisation, support deletion requests, and retain hashes rather than raw values when platforms allow. If you use cookies or local storage to persist identifiers, ensure consent flows are implemented where applicable.
Test with controlled orders: create test orders that include a test gclid and a small order value, then follow them through tagging, webhook processing, upload, and platform matching. Maintain a checklist that verifies field formatting, hashing, timestamps, and timezone alignment (use UTC for uploads).
Operational success depends on repeatable processes: consistent order tagging, reliable webhooks/ETL, hashed identifiers, and reconciliation dashboards. For teams scaling tracking across channels and stores, consider a server-side tagging and data pipeline approach tied to your analytics and attribution strategy. Learn how a technical-first agency integrates tracking with revenue-focused growth systems: Prebo Digital homepage.
Scenario: A Shopify store receives phone orders and records them as offline sales. The team captures gclid at initial contact, tags the order offline-sale, and a webhook sends the order to an ETL service that hashes the customer's email and uploads the conversion to Google Ads with conversion_value $120. After uploads and a 72-hour match window, a portion of those offline orders are matched back to ad clicks, lowering effective CAC by reallocating spend toward channels driving high-value offline conversions.
To discuss how this maps to your store and platform mix, see our contact page for a technical audit request: Contact Prebo Digital. You can also Explore the framework or See a real-world example from similar implementations.
Here's what sets us apart
Don't just take our word for it
Keep reading