Skip to main content
Workiz → CriteoIntegration guide

Connecting Workiz to Criteo

Workiz is built for phone-heavy trades — locksmiths, garage doors, junk removal — where the call is the funnel and the website is a phone number with pictures around it. Criteo is a retargeting and commerce media network built on product-level data, which means its feed matters as much as its conversion events. The join between them succeeds or fails on one thing: whether the Criteo user identifier and product IDs reaches the Workiz job before the conversion happens, because Criteo can only match a conversion it can tie back to a click it recognizes.

Free30 minutesNo obligation

Specific to this pair

Workiz and Criteo: retargeting without a catalog or a session

Criteo is close to the worst fit: Workiz jobs have no catalog or shopping session. For slower quoted jobs like garage door replacement, use the website tag with the quote request form as the conversion and no product IDs. Don't build a fake service catalog or upload paid jobs, and judge spend on quote requests that became paid Workiz jobs.

Criteo's model needs a product catalog and a shopping session, and a Workiz business has neither. A lockout, a broken garage door spring or a junk pickup is an urgent single purchase decided on the phone within minutes; there is no product browsing to retarget and usually no return visit to the site before the job is done. Criteo is close to the worst fit in this list.

Retargeting can still make sense for the slower jobs some Workiz businesses quote, such as garage door replacement or a large cleanout. If so, keep it to the website tag and treat the quote request form as the conversion, with no product IDs. Do not build a fake catalog of services to make transaction events resolve; it adds work and gives Criteo credit it cannot have earned through an emergency phone call.

Do not upload paid Workiz jobs to Criteo as transactions. Criteo's view-through windows would attribute emergency calls to whatever banner the caller last loaded, and the reported value would look strong for reasons unrelated to the ads. Judge any Criteo spend on quote requests that became paid jobs in Workiz, matched by hand at low volume.

Workiz → Criteo · what breaks

Why this join usually fails — Workiz → Criteo

  1. 01

    The Criteo user identifier and product IDs never reaches Workiz

    The session that led to the call lasts seconds and ends when the phone app opens. Only number insertion bridges it.

  2. 02

    Calls counted instead of jobs

    Wrong numbers, price checks, existing customers and suppliers all ring the same line. In emergency trades the call-to-job rate can be well under half, and it differs by campaign.

  3. 03

    Product IDs that do not match the feed

    Criteo resolves conversions against your catalogue. If the IDs in your purchase events differ from the IDs in your feed — a common outcome when the feed is generated by a different system — the conversion resolves poorly and the reported value is wrong.

  4. 04

    Nothing reconciles afterwards

    Criteo reports conversions on its own attribution windows, which include view-through. Reconcile against your own order records and be explicit that view-through credit is included — otherwise the comparison will never balance.

Workiz → Criteo · the fix

What working looks like

  • The Criteo user identifier and product IDs on every job

  • Conversions arriving in Criteo

    Conversions appear in Criteo's reporting attributed to its own view- and click-through windows, which are worth understanding before comparing anything.

  • Reconciled against the source

Workiz → Criteo · architecture

How Workiz and Criteo actually connect

  1. 1

    Workiz holds the truth

    The call recording and the job are already linked inside Workiz. What is usually missing is the link from the call back to the campaign that produced it.

  2. 2

    Criteo needs a click to match

    Criteo needs the transaction with its product IDs, quantities and values, matched to your catalogue feed. Identity resolution is Criteo's side of the problem; feed consistency is yours.

  3. 3

    The identifier is the bridge

    The Criteo user identifier and product IDs, captured at the visit and carried into the Workiz job.

  4. 4

    The event source decides reliability

    Send jobs marked done and paid, at the collected amount.

  5. 5

    Deduplication at the destination

    Criteo deduplicates on the transaction identifier. Sending the same order from both a tag and a server integration without a shared ID counts it twice, and on a retargeting network that inflates the metric the whole channel is judged on.

Workiz → Criteo · normal or broken

Working vs. broken, side by side

Normal, not a fault

  • The Criteo user identifier and product IDs present on the job

  • Sent from the Workiz job record

  • Deduplicated correctly

    Criteo deduplicates on the transaction identifier. Sending the same order from both a tag and a server integration without a shared ID counts it twice, and on a retargeting network that inflates the metric the whole channel is judged on.

  • Reconciles with the source

Actually broken

  • The Criteo user identifier and product IDs missing on most records

    The session that led to the call lasts seconds and ends when the phone app opens. Only number insertion bridges it.

  • Sent from the browser

    Wrong numbers, price checks, existing customers and suppliers all ring the same line. In emergency trades the call-to-job rate can be well under half, and it differs by campaign.

  • Counted twice, or not at all

    Criteo resolves conversions against your catalogue. If the IDs in your purchase events differ from the IDs in your feed — a common outcome when the feed is generated by a different system — the conversion resolves poorly and the reported value is wrong.

  • Nobody has reconciled it

Workiz → Criteo · diagnose

Diagnostic order — Workiz → Criteo

  1. 01

    Count jobs carrying the Criteo user identifier and product IDs

  2. 02

    Follow one real conversion end to end

  3. 03

    Measure call-to-job rate per campaign

    It is the multiplier between what you are reporting and what you are earning, and it is rarely the same across sources.

  4. 04

    Compare product IDs in a real conversion against the catalogue feed

    They must match exactly. This single check explains most Criteo value discrepancies.

  5. 05

    Read the match rate, not the success message

    Criteo reports conversions on its own attribution windows, which include view-through. Reconcile against your own order records and be explicit that view-through credit is included — otherwise the comparison will never balance.

Workiz → Criteo · prove

How it gets proven — Workiz → Criteo

Source of truth

Workiz jobs marked done and paid, joined to the call that booked them.

  • The Criteo user identifier and product IDs confirmed present on a live job.
  • Product IDs in a live conversion confirmed to match the catalogue feed exactly.
  • Paid completed jobs reconciled against imported conversions, with raw call volume reported separately.

Workiz → Criteo · free audit

What we check in the free audit

  • Count jobs carrying the Criteo user identifier and product IDs
  • Follow one real conversion end to end
  • Measure call-to-job rate per campaign
  • Compare product IDs in a real conversion against the catalogue feed
  • Read the match rate, not the success message

Checked against

Workiz jobs marked done and paid, joined to the call that booked them.

Get my free conversion tracking audit

Free30 minutesNo obligation

Workiz → Criteo · when not to buy

When you don't need this — Workiz → Criteo

  • Measure identifier coverage yourself first — pull your last hundred jobs and count how many carry the Criteo user identifier and product IDs.
  • If you already answer every call and convert nearly all of them, call volume is a fine proxy and the join is not worth building.
  • If you do not sell products with a catalogue, Criteo's model does not fit and the effort is misdirected.

Workiz → Criteo · what we deliver

What gets built — Workiz → Criteo

  • Identifier capture into Workiz

    Use dynamic number insertion with a pool large enough that numbers are not recycled within your booking window.

  • Event source: the Workiz job record

    Send jobs marked done and paid, at the collected amount.

  • Dispatch to Criteo

    Server-side transaction events with product IDs matching the catalogue feed, plus the feed itself kept in sync.

  • Reversals where they exist

    Cancelled and unpaid jobs reverse.

Written guarantee

95%+ tracking accuracy

Measured against Workiz jobs marked done and paid, joined to the call that booked them.. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Workiz → Criteo questions, answered

Not for emergency work, which has no browsing to retarget. It can play a small role for quote-based jobs, measured on quote requests.

Free · 30 min

Get Workiz and Criteo joined properly

Free30 minutesNo obligation