Conversion Exporter / Conversion Tasks / Conversion Task

Conversion Task

Last updated: February 12, 2026

Conversion Tasks are the “recipes” that tell Conversion Exporter what to export (orders or leads), how to format it, and how Google Ads should import it.
You’ll usually create one task per Google Ads conversion action (ex: “Purchase”, “Lead”, “Refund adjustment”).

Where to find it

Go to WP Admin → Conversion Exporter → Conversion Tasks and click Add New Conversion Task.

On the main list you can:

  • Enable/disable a task (toggle)
  • Edit / Delete
  • Regenerate CSV files (manual refresh)
  • See Last update and Last Google crawl (useful when Google fetches your hosted file)

Create a Conversion Task

1) General

  • Enable Conversion Task
    Turns the task on/off. Disabled tasks won’t regenerate exports.
  • Task name (required)
    Internal label in WordPress (example: WooCommerce Purchase Export).
  • Conversion URL (optional)
    For your reference (a link to the conversion setup in Google Ads, or the “thank you” URL).
  • Enable Consent (optional)
    Uses your global Consent settings (ConsentMagic integration) to decide which entries are allowed to be exported.

2) Google Ads format

  • Conversion format
    • Google Ads Data Manager format
      Use this if you connect the feed through Google Ads Data Manager.
    • Conversion Uploads format
      The “classic” Google Ads upload CSV (manual upload or scheduled fetch, depending on your setup).
  • Conversion Name (required)
    The exact conversion action name from Google Ads. Spelling and spaces must match perfectly, otherwise Google won’t map the rows correctly.

3) What data is exported

  • Source
    • WooCommerce: exports orders (purchases + adjustments when needed)
    • Form: exports captured form submissions (lead exports)
  • Order statuses to include (WooCommerce only)
    Choose which statuses count as a conversion (common: Processing, Completed).
    This lets you control when an order becomes eligible for export.
  • Include Value
    Adds the order value (or lead value if your setup supports it) to the export.
  • Include Converted Lead Data
    Adds user data fields for matching (Enhanced Conversions style data). This works best when SHA256 hashing is enabled in the plugin settings.
  • Only entries with GCLID
    Exports only rows that have a captured click ID (GCLID / GBRAID / WBRAID).
    Useful when you want strict “conversions from clicks” imports only.
  • Only orders not tracked by the PixelYourSite Google Tag (WooCommerce only)
    Prevents double-counting if you already track purchases online with PixelYourSite’s Google tag.

4) Backfill + incremental updates

  • Start generation from date (optional)
    Sets the first date included when the task generates CSVs (useful for backfills). Leave empty to include all available data.
  • Detect when the Google Ads crawler accesses the file and mark it as loaded
    If Google is fetching a hosted CSV, this helps the plugin track the fetch moment and keep “new since last fetch” exports clean.
    You’ll see the result in the task list as Last Google crawl.

5) Hosted feed security

If you use a hosted CSV URL (for scheduled fetch), the plugin can protect it with HTTP Basic Auth:

  • Username
  • Password

Use these credentials in the Google Ads fetch setup (so the Google bot can access the file securely).


Conversion Task templates (what “type” of upload it represents)

You’ll typically use one of these task types (shown in the task list as Template type):

  • Conversions from clicks (WooCommerce)
    Standard offline conversions attributed to ad clicks. Requires captured GCLID/GBRAID/WBRAID.
  • Conversions from clicks (Enhanced for leads) (Leads / Forms)
    Exports hashed first-party data (email/phone/name where available) to improve matching.
    Best for lead gen flows, especially when the click ID is missing.
  • Conversion adjustments(WooCommerce only)
    Updates an existing conversion using the Order ID, so Google Ads reflects reality:
    • Retractions: full refunds
    • Restatements: order total changes (partial refunds, edits)

Quick examples

A) WooCommerce purchase import (typical)

  • Source: WooCommerce
  • Statuses: Processing + Completed
  • Include Value: ON
  • Only entries with GCLID: ON
  • Only orders not tracked by PYS Google Tag: ON (if you already track online)

B) Lead export (forms)

  • Source: Form
  • Include Converted Lead Data: ON
  • Hashing (Settings): ON
  • Only entries with GCLID: usually OFF (so Google can match via hashed data)

C) Refund handling

  • Create a second task: Conversion adjustments
  • Purpose: retractions/restatements so ROAS stays accurate when orders change

If you want, upload the next screenshots for Form Tasks and I’ll write the matching docs section in the same style.