offline-conversion-upload

Match GCLID leads from Supabase to ServiceTitan jobs and generate a Google Ads CSV.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill offline-conversion-upload
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offline-conversion-upload
Source: https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit/tree/main/skills/offline-conversion-upload
Command: npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill offline-conversion-upload

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull offline conversion data from Supabase, match to ServiceTitan completed jobs, generate a CSV, and upload it to Google Ads via browser on a repeatable weekly cadence until API access is approved.

Core Features & Use Cases

  • GCLID-led matching: reconcile Supabase leads with ServiceTitan job records to produce accurate offline conversions.
  • CSV generation for Google Ads: produce the required upload format for Smart Bidding.
  • Browser-based upload workflow: supports manual Google Ads uploads when API access is restricted.
  • Weekly automation readiness: designed for repeatable weekly runs until GFV-335 is resolved.

Quick Start

Run the weekly offline-conversion-upload workflow to generate the upload CSV and initiate the Google Ads upload.

Frequently Asked Questions about offline-conversion-upload

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload offline conversions to Google Ads without API access?

To upload offline conversions without API access, generate a CSV file from matched GCLID data and manually upload it via the Google Ads browser interface. This workflow supports repeatable weekly runs while waiting for direct API integration approval.

What is GCLID matching for offline conversion tracking?

GCLID matching for offline conversion tracking reconciles Supabase lead records containing Google Click IDs with ServiceTitan completed jobs. This process verifies which ad clicks resulted in actual offline work to produce accurate conversion data for Google Ads.

How do I match ServiceTitan completed jobs to Supabase leads for Google Ads?

To match ServiceTitan completed jobs to Supabase leads, reconcile the records using the GCLID. The workflow queries a Supabase gclid_leads table and cross-references it with ServiceTitan job records to identify successful offline conversions.

Do I need a specific Supabase schema to track offline conversions?

Yes, you need a Supabase schema containing a gclid_leads table to track offline conversions. This table stores the Google Click IDs required to match incoming leads with completed ServiceTitan jobs for the final CSV generation.

Can I automate weekly offline conversion uploads to Google Ads?

You can automate weekly offline conversion uploads by running the workflow on a scheduled cadence to generate the required CSV. Until API access is approved, the final upload step remains a browser-based manual process within Google Ads.

Why are my offline conversions not working with Google Ads Smart Bidding?

Offline conversions may not work with Smart Bidding if the uploaded CSV lacks properly matched GCLID data. Ensure Supabase leads are accurately reconciled with ServiceTitan completed jobs and formatted correctly before browser-based upload.