SegMetrics

Connect AI agents to SegMetrics, marketing attribution for funnels, courses, and memberships. Agents sync contacts and orders, tag them, and read the attribution reports that show which ads produced revenue.

14 actions API key available

SegMetrics website ↗ Platform Documentation ↗ Capability data verified 2026-08-05

A scheduled sync starts, or an order arrives from the store, because SegMetrics has no triggers of its own

The upstream order is read with its UTM parameters, referring and opt-in URLs, IP, and affiliate

Get Contact confirms whether this buyer already exists and what attribution status they carry

Add or Update Contact writes the lead with its attribution data, then Add Purchase records the invoice in cents

Run Report Query re-reads the period under the agreed attribution model to confirm the revenue landed on the channel expected

The marketing owner receives the channel level movement the new revenue produced

When a refund arrives, the owner decides whether to delete the original purchase or record an offsetting entry

What This Integration Enables

SegMetrics answers which marketing actually produced the money, and the honest thing to say about any attribution tool is that its answer is only as good as what was written into it. This connector sits on both sides of that. It is a write surface. Add or Update Contact captures UTM parameters, referring and opt-in URLs, IP, and affiliate alongside tags and custom fields. Add Purchase records invoices with line items, and Add or Update Subscription captures billing terms so recurring revenue is tracked by acquisition source. Add or Update Product names the things being sold, and Record Ad Performance logs daily spend so cost per lead and return on ad spend are computed against imported revenue rather than guessed at. It is also a read surface. Get Report Data returns a saved report's KPIs, time series, and breakdown table. Get Report Contacts returns the individual customer journeys behind those numbers. Run Report Query executes ad hoc analyses across leads, revenue, ads, subscriptions, and funnels with a chosen attribution model and dimensional breakdowns.

An agent that holds both halves is powerful and worth being deliberate about, because it can write the evidence and then quote the conclusion. That is not a reason to avoid the pattern. It is a reason to keep the writes boring and the reads honest: import what actually happened, on a schedule, from the system of record, and let the reporting side describe it rather than shape it.

Two details to get right in the first hour. Monetary amounts are expressed in cents on invoice amount and paid, subscription amount, and ad spend, so a flow that passes dollars reports a hundred times the revenue and looks plausible doing it. And contact scoped actions accept either an email or a contact ID as the match key, which makes the sync resilient when the upstream system has one and not the other. There are no triggers on this connector. SegMetrics does not wake a flow up; the store, the payment processor, or a schedule does.

Without FlowRunner

Attribution ends at the signup Revenue is tracked in the store and leads in the marketing tool, and nothing joins them

Ad spend lives elsewhere Cost per lead is assembled by hand from a platform export and a revenue export

Reported numbers change quietly A refund sync rewrites a closed period and nobody who reported it is told

With FlowRunner

Revenue carries its source Purchases and subscriptions are recorded against the contact that already holds the UTM data

Spend sits beside revenue Daily ad performance is imported so cost per lead and return on ad spend are computed on one dataset

Retroactive changes are decisions A deletion that alters an already reported period is put to the person who reported it

Use Case Scenarios

Orders that arrive already attributed

An order completes in Shopify. The flow reads the order along with the UTM parameters and referring URL the store captured at signup. It calls Get Contact to see whether this buyer is already a known lead, then Add or Update Contact matched on email, so the attribution data lands on the existing journey rather than starting a new one. Add Purchase records the invoice with its line items and the amount in cents, and Add or Update Product ensures the products on those line items are named rather than appearing as bare SKUs in the revenue report. Where the purchase is a plan rather than a one off, Add or Update Subscription captures the billing cycle and frequency so recurring revenue is attributed to the campaign that acquired it, not to the month it renewed in.

Spend and revenue in the same dataset, daily

Cost per lead is a number most teams reconstruct once a month from two exports. A daily flow reads yesterday's spend and performance from Google Ads and Facebook and calls Record Ad Performance for each ad, which puts spend into the same place the imported revenue already lives. The agent then calls Run Report Query broken down by a dimension such as clicks.channel to read return on ad spend per channel under the attribution model the team agreed on. It posts the result to the marketing channel in Slack with the previous week beside it. Nothing about the spend gets changed by the flow. The point is that the comparison exists every morning instead of at month end.

Following a number back to the people behind it

A channel's revenue jumps and the reasonable first question is whether that is real. Get Report Data returns the saved report's KPIs and breakdown, and Get Report Contacts returns the actual contacts that make up those numbers over the date range, paginated up to 100 per page and expandable with related events, tags, orders, subscriptions, and lists. The agent pulls the contributing journeys, checks how many are distinct contacts rather than repeat purchases from a handful, and writes the list to Google Sheets for the analyst. A spike driven by four enterprise buyers and a spike driven by four hundred small ones are different events that produce the same chart, and the difference decides whether anyone should move budget.

Human-in-Loop Highlight

Delete Purchase removes a previously recorded invoice by its invoice ID so its revenue no longer counts toward attribution reports. In a refunds sync that sounds like the obvious call and it is the one worth stopping on, because it does not just correct a number going forward, it rewrites a period that has already been reported. The channel that was credited with that revenue loses it retroactively, the return on ad spend figure that justified last month's budget shift moves after the shift was made, and the board deck showing the old number now cites something SegMetrics no longer says. Nothing inside the platform records that the figure ever existed. There is a real alternative and it is a judgment rather than a rule: recording an offsetting entry keeps the original period reproducible and books the refund in the period it actually happened, which is what a finance team would expect and what a marketing team often does not want, because it leaves gross revenue looking healthier than net. Delete Contact is blunter still, removing the contact and its associated data, which is the entire customer journey that Get Report Contacts would have shown. So the agent handles the mechanical part and escalates the choice. It matches the refund to its invoice ID, calls Get Report Data for the affected period to establish exactly what would change, and asks the marketing owner: "Refund received against invoice 44127, 890.00 recorded in March. Deleting it moves March paid search revenue down 4 percent, and March was already reported. Delete the purchase, or record an offsetting entry in the current period?" That question has no automatable right answer, which is precisely why an agent should ask it. Framing this as human-in-the-loop is not a hedge, it is the reason the agent can be trusted with the other several thousand writes it makes without asking.

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

14 actions

Contacts and Tags

Add or Update Contact Creates a contact, or updates an existing one matched by email or contact ID, capturing attribution data including UTM parameters, referring and opt-in URLs, IP, and affiliate, plus tags and custom fields. Provide either an email or a contact ID. This is the action that ties a person to the marketing that produced them.
Get Contact Retrieves a single contact from the Reporting API by contact ID or email, including custom fields, tags, and attribution status, with an Include option to expand related events, orders, subscriptions, lists, and companies. Call it before a write when the flow needs to know whether it is creating or updating.
Delete Contact Permanently removes a contact and its associated data, identified by contact ID or email. The associated data is the journey, so this is not a light deletion.
Add Tags to Contact Assigns one or more tags to a contact matched by email or contact ID. Tags may be given as names or IDs and are created if they do not already exist, which makes it easy to introduce a tag by typo.
Remove Tags from Contact Detaches one or more tags from a contact matched by email or contact ID, with tags given as names or IDs.

Revenue

Add Purchase Records a purchase or invoice against a contact so revenue is attributed back to its marketing source, with line items describing the products purchased. Amounts are expressed in cents. Provide either an email or a contact ID.
Delete Purchase Removes a previously recorded invoice by its invoice ID so its revenue no longer counts toward attribution reports. It changes periods that have already been reported, which is why it belongs behind a decision rather than inside a loop.
Add or Update Subscription Records a recurring subscription against a contact, capturing billing terms so recurring revenue and lifetime value are tracked by acquisition source. Amounts are in cents and the billing interval is Billing Cycle multiplied by Frequency.
Cancel Subscription Removes a subscription record by its subscription ID, ending its contribution to recurring revenue reporting.
Add or Update Product Registers a product or updates its name so purchases and subscriptions attribute to something readable in revenue reports rather than to a raw identifier.

Ad Spend

Record Ad Performance Logs daily ad spend and performance metrics for an ad so cost per lead, return on ad spend, and channel attribution are calculated alongside imported revenue. Spend is expressed in cents, like every other amount in this connector.

Reporting

Get Report Data Retrieves a saved report by type and ID over a date range, returning its KPIs, time series graph datasets, and breakdown table. The read for leads, revenue, ad, or subscription analytics over a period.
Get Report Contacts Retrieves the customer journeys behind a saved report, meaning the individual contacts that make up its numbers over a date range. Paginated up to 100 per page and expandable with related events, tags, orders, subscriptions, and lists. Use it whenever a headline number needs to be checked against the people underneath it.
Run Report Query Executes an ad hoc analytics query without a saved report, returning fields, rows, and totals across leads, revenue, ads, subscriptions, and funnel analyses, with breakdowns by dimensions such as clicks.channel, a chosen attribution model, and filters. The attribution model is a parameter here, so a flow that reports a channel's performance should always state which model produced the figure.

Frequently Asked Questions

What can FlowRunner do with SegMetrics?

FlowRunner agents can run Add or Update Contact, Delete Contact, and Get Contact in SegMetrics, plus 11 more actions.

Does connecting SegMetrics to FlowRunner require OAuth?

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

Can SegMetrics trigger a FlowRunner workflow automatically?

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

Start building with SegMetrics

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

Start Building Free Talk to us