Technical Guide

Hyros Offline Conversions: How the API Works

For paid media, the tracker's core value is feeding CRM outcomes back to Google and Meta more accurately than platform-native tracking can. We break down what the payload contains and what happens when no click ID exists.

Foundation

What an Offline Conversion Is

An offline conversion is a conversion event that happened outside the ad platform's direct visibility.

A form fill on your website is an online conversion that Google and Meta can track natively. A phone call that resulted in a booked appointment, a CRM stage change that indicates a qualified lead, or a payment collected two weeks after the initial click are offline conversions. The platform did not see them happen.

The offline conversion API lets you tell Google or Meta after the fact: this specific visitor, who came from this specific ad click, completed this specific action and it was worth this specific dollar amount. The platform uses that information to improve the algorithm's understanding of which clicks are worth bidding on. Offline conversion sync is a core part of our full Hyros implementation service.

Online vs offline conversions

TypeExamplesPlatform sees it?
OnlineForm fill, page visit, add to cartYes
OfflinePhone call, signed retainer, collected payment, CRM stageNot without API
Via HyrosAny downstream event from CRM, phone, payment processorSent via API

Free Tracking Audit

Find Out Where Your Tracking Loses Revenue

On a discovery call we review how your conversions reach Google Ads, from the first click to the closed sale, and tell you what we would fix first.

For advertisers spending $100K+/month. No cost, no obligation. A person reads every submission.

Request a Discovery Call →

Disclosure: LGG Media is a Hyros Certified Agency. We earn a commission when a client subscribes to Hyros through us. It does not change what we recommend.

API Structure

The Hyros Offline Conversion Payload

When Hyros sends an offline conversion to Google Ads or Meta, the payload contains three elements. Each serves a distinct function in the matching and optimization process.

1

Conversion name

The name of the conversion action configured in your ad platform. Tells the platform which conversion event this payload is reporting.

Examples: Signed Retainer, Policy Sold, SQL.

2

Click identifier

The direct link between the offline event and the specific ad click that generated it. Hyros stored this when the visitor first arrived from a paid click and retrieves it from the lead record when the offline event is ready to send.

By platform: gclid for Google Ads, fbclid for Meta Ads, msclkid for Microsoft Ads.

3

Conversion value

The dollar amount associated with the conversion. Can be a fixed value configured in Hyros or a dynamic value pulled from your payment processor, ERP, or CRM.

Fixed vs dynamic: fixed means every conversion equals $500; dynamic means actual revenue per event.

Requirements

Click ID Requirements and Expiration

For a click ID match to succeed, two conditions need to be met. Both are configuration issues we find regularly in accounts that were not set up with Hyros in mind from the start.

1 · Click ID must be captured at the moment of the visit

This requires auto-tagging to be enabled in Google Ads, which appends the gclid parameter to your destination URLs automatically. If auto-tagging is disabled, gclid parameters are not present and Hyros has nothing to capture.

Common failure: auto-tagging disabled in Google Ads account settings.

2 · Click ID must not have expired

Google Ads gclid parameters have a 90-day upload window. If you are trying to send an offline conversion for an event that happened more than 90 days after the original click, Google will reject it.

For businesses with very long consideration periods: build the offline conversion sync to fire at an earlier funnel stage rather than waiting for the final transaction.

What we check first in every account

  • Auto-tagging enabled in Google Ads.
  • URL parameters passing through landing page redirects.
  • gclid present in Hyros session records.
  • Click ID match rate vs PII fallback rate.
  • Conversion upload window vs average sales cycle length.
Fallback Matching

Hashed PII Fallback Matching

When a click ID is not available because it was not captured, or because the conversion came through a channel that does not use click IDs, Hyros can fall back to hashed PII matching.

In this case the offline conversion payload substitutes the click ID with a hashed version of the lead's email address or phone number. Google and Meta both support PII-based matching through enhanced conversions for leads and the Conversions API. The platform hashes your customer's data on their end using the same algorithm, then attempts to match it to a user in their system who clicked one of your ads.

PII matching is less precise than click ID matching because it relies on the platform being able to identify the person from their hashed contact information. If the person used a different email address when they clicked the ad versus when they submitted your form, the match will fail. Click ID matching does not have this problem because the click ID is tied to the specific click event, not to the person's identity.

Click ID vs PII fallback

FactorClick IDPII fallback
Match basisSpecific click eventHashed email or phone
PrecisionExactProbabilistic
Fails whenNot captured or expiredEmail mismatch between click and form
Platform supportGoogle, Meta, MicrosoftGoogle enhanced conversions, Meta Conversions API

What we monitor: click ID match rate vs PII fallback rate. A high PII fallback rate with a low match rate indicates that click IDs are not being captured correctly and needs to be addressed at the tracking layer.

Revenue Passback

Dynamic Conversion Values and Revenue Passback

The most significant bidding improvement from Hyros comes from passing dynamic conversion values rather than fixed values.

Fixed value

When you configure a conversion action with a fixed value of $500, you are telling the algorithm that every conversion is worth $500. The algorithm cannot distinguish between a $200 conversion and a $2,000 conversion. It optimizes for conversion volume, not conversion value.

Result: algorithm treats all conversions equally. No ability to bid toward higher-value outcomes.

Dynamic value via Hyros

When you pass dynamic values from Hyros, each conversion carries its actual worth. A $200 transaction sends $200. A $2,000 transaction sends $2,000. The algorithm learns that certain audiences, keywords, and creatives produce higher-value outcomes and adjusts bids accordingly.

Result: target ROAS bidding actually works. Algorithm optimizes toward revenue, not volume.

130%
Profit ROAS

National BNPL Tire Retailer

We built an integration with their ERP system to calculate profit per transaction, combining product margin and financing commission. The conversion value passed to Google was actual profit, not revenue. The algorithm stopped optimizing for transaction volume and started finding customers who produced the highest profit per transaction.

Read Case Study
4x
Ad spend scaled

Ecommerce Profit Attribution

Passing actual profit as the conversion value let the account scale to 4x ad spend while the algorithm concentrated budget on the highest-profit customers rather than the highest transaction count.

Read Case Study
Audience Sync

Audience Sync from Hyros Lead Records

Beyond offline conversions, Hyros can push audience data back to ad platforms. Lead records with specific attributes, CRM stages, or conversion events can be exported as custom audiences to Google and Meta.

This enables remarketing to prospects at specific stages in your sales funnel rather than everyone who visited a page. It also enables exclusion lists, removing converted customers from prospecting campaigns so ad spend is not wasted showing acquisition ads to existing clients.

The audience sync runs through the same lead record infrastructure as offline conversions. Because Hyros has a complete picture of where each lead is in the buying journey, the audiences it produces are more precise than audiences built from pixel data alone. Attribution percentage and bidding performance →

Audience use cases

  • Remarketing to leads at a specific CRM stage, qualified but not closed.
  • Exclusion lists to remove existing customers from prospecting.
  • Lookalike audiences seeded from closed-won leads only.
  • Re-engagement campaigns for leads that went cold.
  • Upsell campaigns to customers who bought a specific product.

Why this is more precise than pixel audiences: pixel audiences are built from page visits. Hyros audiences are built from lead records, which means they reflect actual buying intent signals, not just traffic patterns.

Free Tracking Audit

Build Offline Conversion Infrastructure That Actually Improves Bidding

Building the offline conversion infrastructure correctly from the start determines whether your bidding strategy improves over time or plateaus. LGG Media has been a Hyros Certified Agency since 2019, building offline conversion integrations across accounts spending at $100K+/day.

For advertisers spending $100K+/month. No cost, no obligation. A person reads every submission.

Request a Discovery Call →

Disclosure: LGG Media is a Hyros Certified Agency. We earn a commission when a client subscribes to Hyros through us. It does not change what we recommend.