Practical troubleshooting for founders and growth teams to improve offline conversion accuracy, attribution, and revenue reporting for US stores.
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
Top failure points
Practical fixes
Funnel approach
Offline conversion tracking connects in-person, phone, and manually recorded sales back to paid-media interactions (clicks, impressions, and leads). For US Shopify merchants this affects CAC, LTV analysis, and channel-level profitability. Common issues with Shopify offline conversion tracking reduce attribution clarity and can inflate or under-report channel performance, making growth decisions noisy.
Quick note: In the United States, attribution windows and tax-tied values (sales tax) change reported conversion value. Use $ values and document whether totals include tax and shipping when validating imports.
| Flow | What is captured | Common failure |
|---|---|---|
| Client-side (browser) | Cookies, click IDs, UTM params, JS events | Ad-blockers, cookie consent, third-party cookie restrictions |
| Server-side (backend/SSG) | Order creation, server-stored click IDs, hashed identifiers | Incorrect capture at order creation, missing dedupe IDs |
If you want a quick overview of your platform mix before deep troubleshooting, review Prebo Digital's high-level services and where offline tracking fits into an overall growth stack on the Services page. For strategy context on how tracking aligns with revenue goals, see the team and approach on our About page.
Symptom: Offline orders show as direct or unknown in platform reporting. Root cause: gclid/fbclid not written to order meta or session expired before the order is recorded. Fix: Persist click identifiers at first interaction into local storage and copy them to order attributes when the order is created (or capture server-side at lead creation).
Symptom: Imports apply to the wrong day in Google Ads/Meta or appear outside the expected attribution window. Root cause: Upload timestamps use local store timezone or non-UTC formatting. Fix: Convert all event_time fields to UTC ISO 8601 before upload and document the time conversion in your ETL process.
Symptom: Conversion counts jump after manual upload. Root cause: Missing or mismatched deduplication keys (e.g., order_id vs platform event_id). Fix: Always send a stable dedupe key (Shopify order_id or a hashed order reference) and follow the ad platform's dedupe guidelines during import.
Symptom: High rejection rate on uploads or low matching rates. Root cause: Incorrect PII normalization or wrong hashing algorithm. Fix: Normalize emails to lowercase and trim spaces; apply SHA256 where required; confirm expected fields in the platform schema.
Symptom: Offline conversions are attributed differently across tools. Root cause: Platforms use different lookback windows (e.g., 7-day click vs 28-day click + view). Fix: Align internal reporting to a single source of truth, document platform windows, and use conversion modeling where necessary to reconcile gaps.
Example (US retail): A store averages $250 per POS order and enters phone orders into Shopify. If 15% of phone orders lack a stored gclid, and paid channels drive 40% of phone calls, you could be under-attributing roughly $1,500-$2,500 per week (estimate dependent on volume). Practical steps below reduce that leakage.
If you need a template or implementation checklist for Shopify server-side capture and upload workflows, our homepage has examples of how tracking fits into a broader growth system: Prebo Digital. For teams evaluating a tracking audit or growth retainer, the contact page explains how to request a technical review.
For US-focused stores, document your baseline match rates and $ leakage before and after fixes. This makes it possible to quantify improvements to CAC and channel-level profitability rather than relying on platform-reported vanity metrics.
Here's what sets us apart
Don't just take our word for it
Keep reading
