Hyros

Feed Hyros ad attribution with clean conversion data. Agents push leads, sales, and sales-call events into Hyros so revenue is attributed to the right ad and campaign, and look up leads and order history to verify tracking was recorded.

5 actions API key available

Hyros website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A paid order lands in the storefront and the order webhook reaches FlowRunner

Get Lead looks up the customer by email to confirm Hyros already knows this contact

Create Lead registers the contact when the lookup comes back empty, carrying the originating IP so Hyros can match prior ad clicks

Get Orders confirms the order ID has not already been recorded against this customer

An order whose total disagrees with its line items, or whose currency does not match the store, goes to the marketing ops owner before anything is written

Track Order pushes the sale with its unique order ID, price, currency, and line items so revenue lands on the right ad

A confirmation posts to the revenue channel with the attribution source Hyros returned

What This Integration Enables

Attribution is a data-hygiene problem wearing an analytics costume. Hyros can only attribute revenue to the right ad if the leads, orders, and calls flowing into it are complete, deduplicated, and correctly identified, and most teams feed it through a patchwork of pixels and one-way integrations that nobody owns. FlowRunner treats the Hyros feed as a governed pipeline: agents register every new contact with Create Lead, report every sale with Track Order, log every booked and closed call with Track Call, and then read back with Get Lead and Get Orders to prove the data actually landed. - Push subscribers, opt-ins, and buyers into Hyros the moment they appear in your CRM, storefront, or billing system - Report purchases with unique order IDs so Hyros deduplicates and revenue is never double-counted - Feed call-center and booking activity into call-based attribution, from booked through closed won - Verify tracking after the fact, so a broken feed is a flagged exception rather than a quarter of skewed reports - Route anomalies through [human-in-the-loop](/concepts/human-in-the-loop) review before they contaminate attribution

Without FlowRunner

Attribution fed by pixels alone Revenue reporting depends on browser-side tracking that ad blockers and cookie churn quietly erode

One-way zaps nobody audits Events flow into the attribution platform through brittle point-to-point connections, and nobody notices when one stops

ROI decisions on unverified data Budget moves between campaigns based on reports no one can trace back to a checked event stream

With FlowRunner

Server-side events with identity attached Agents push leads and orders directly, keyed on email and order ID, so attribution does not hinge on a browser

A feed that checks itself Get Lead and Get Orders verify that what was sent actually recorded, and gaps surface as exceptions instead of silence

A person gates the anomalies Mismatched totals and suspect events wait for review, so the reports that move ad spend stay trustworthy

Use Case Scenarios

Every storefront sale attributed, exactly once

A new order fires from [Shopify](/integrations/shopify). The agent calls Get Lead with the customer email; if Hyros has never seen this contact, Create Lead registers them with their tags and originating IP so earlier ad clicks match. Then Track Order reports the sale with the Shopify order number as the unique order ID, the order total, currency, and each line item. Because Hyros deduplicates on that order ID, a webhook retry cannot double-count the sale. Refund events from the store do not silently vanish either: the agent flags them to the marketing ops owner, because revenue already attributed in Hyros cannot be recalled through this connector.

Booked calls become attribution events

A prospect books a demo through [Calendly](/integrations/calendly). The agent calls Create Lead so the contact exists in Hyros, then Track Call with the call date and the Booked stage. When the call outcome is logged in the CRM, a second pass updates the story: Track Call records Held, Closed Won, or Closed Lost, with a monetary value on the win. Ad spend that produces booked calls, not just form fills, finally shows up in the ROI report the way the funnel actually works.

The weekly attribution audit

On a Monday schedule, the agent samples the week's orders from [Stripe](/integrations/stripe), then calls Get Orders for each customer email and compares what Hyros recorded against what billing collected. Matches append to a reconciliation tab in [Google Sheets](/integrations/google-sheets); mismatches and absences post to [Slack](/integrations/slack) as a short exception list. When the list is empty, the team trusts the dashboard. When it is not, someone knows on Monday rather than at the end of the quarter.

Human-in-Loop Highlight

Track Order writes revenue into the reports that decide where next month's ad budget goes, and this connector has no action that takes an order back out. That asymmetry is the gate. When an agent prepares a backfill of historical sales, or an order arrives whose price disagrees with the sum of its line items, the batch stops and the marketing ops owner sees exactly what is about to be written: order IDs, totals, currencies, and the leads they attach to. Approve, and Track Order runs at machine speed. Reject, and nothing touches the attribution record. A wrong number here does not crash a workflow; it quietly moves real budget toward the wrong campaign, which is precisely the kind of mistake a person should get to veto.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Leads

Create Lead Creates or updates a lead (contact) in Hyros and attaches it to a tracked profile. Use this to push a new subscriber, opt-in, or contact into Hyros so their ad-attribution journey can be tracked. If a lead with the same email already exists, Hyros updates it. Supports multiple phone numbers, tags, and the lead's originating IP address, which Hyros uses to match the lead to prior ad clicks and page views.
Get Lead Retrieves a lead (contact) from Hyros by email address. Returns the lead's profile including name, tags, attribution source, and lifetime value when available. Use this to look up an existing contact or verify that a lead was successfully tracked.

Orders

Track Order Tracks a sale or order in Hyros and attributes revenue to the correct ad, campaign, and traffic source for the associated lead. Use this to report a purchase so it appears in Hyros ROI and attribution reports. Provide the customer email, a unique order ID, the order date, price, currency, and the individual line items purchased.
Get Orders Retrieves the orders and sales associated with a customer email address from Hyros. Returns each order with its amount, currency, date, line items, and attribution details when available. Use this to review a customer's purchase history or confirm that a tracked sale was recorded.

Calls

Track Call Tracks a sales-call event in Hyros and associates it with a lead for call-based attribution and reporting, covering booked, held, and closed calls. Use this to feed call-center or booking activity into Hyros so it can be tied to ad spend. Provide the lead's email, the call date, and optionally a stage and monetary value for the call.

Frequently Asked Questions

What can FlowRunner do with Hyros?

FlowRunner agents can run Create Lead, Get Lead, and Track Order in Hyros, plus 2 more actions.

Does connecting Hyros to FlowRunner require OAuth?

No. Hyros connects to FlowRunner with an API key, no OAuth flow required.

Can Hyros trigger a FlowRunner workflow automatically?

Hyros doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Hyros

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us