Resources · Make integration

SegMetrics Make integrationAutomate SegMetrics with Make.

Your SegMetrics reports are only as good as the data that reaches them. The SegMetrics Make integration gives you 10 action modules to push contacts, orders, subscriptions, tags and ad results without code. This page shows how to connect your account and build a first scenario.

Try the SegMetrics integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SegMetrics Make integration do for you?

The SegMetrics Make integration lets a Make scenario (the automation you build in Make, a chain of modules) write data into your SegMetrics account. Each module is one brick of that chain: here, all 10 are actions that add, update or delete contacts, orders, subscriptions, tags or ad performance.

Ad spend next to revenue. Your ad platform reports what a campaign cost, SegMetrics reports what leads bought. Record Ad Performance adds the results for a given day, so both sides of the equation sit in one account.

Customers who arrive already sorted. A signup lands in your form tool or your shop. Add/Update a Contact creates the person in SegMetrics, then Add Tag to Contact labels the source so your segments are right from the first day.

Revenue that matches billing. When a sale or renewal happens in your checkout, Add/Update an Order and Add/Update a Subscription keep the purchase history current. A refund can be cleaned up with Delete an Order.

One thing Make cannot do here: SegMetrics has no trigger module, so it never starts a scenario on its own. Another app, or the schedule of Make, starts the flow. For anything outside the 10 modules, Make an API Call reaches the SegMetrics API with the same connection. If you hesitate between tools, read our n8n vs Make comparison and the Make pricing breakdown. For a guided start, see the Make training.

Connect

How do you connect SegMetrics to Make?

  1. 01

    Copy your SegMetrics API key

    You need an active SegMetrics account and its API key. In SegMetrics, click the Gear icon at the top right of the screen, open Account Settings and copy the key you find there.

  2. 02

    Add a SegMetrics module in Make

    Open your scenario in Make, add any SegMetrics module and click Create a connection. A connection is your SegMetrics account linked to Make once, then reused by every SegMetrics module.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you manage several accounts; this field is optional. Paste the API key, confirm, and Make now lists what it can read from SegMetrics.

First scenario

Your first scenario: new leads land in SegMetrics already tagged

GoalWhen a new lead appears in the app where you collect signups, Make adds the contact to SegMetrics and tags it with its source.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your leads arrive, since SegMetrics itself has no trigger.

  2. 02

    Add the contact module

    Click the + on the right of that first module, search for SegMetrics and choose Add/Update a Contact. Select your connection, or create it now with the API key.

  3. 03

    Map the lead data

    Fill the module with values from the first module: each new lead reaches it as a bundle, one item passed from module to module. Pick the SegMetrics integration that should receive the contact.

  4. 04

    Tag the new contact

    Add Add Tag to Contact after it and map the contact from the previous step. Choose a tag that names the source, so your SegMetrics segments can separate this channel.

  5. 05

    Test with Run once

    Click Run once and create a test lead. Read the bundles each module received, then check that the contact and its tag show up in SegMetrics.

  6. 06

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.

Modules

The 10 SegMetrics modules, one by one

SegMetrics gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SegMetrics1

Add Tag to Contact

Action

In Make“Adds tag to the contact.”

Puts a tag on a contact that already exists in SegMetrics, which gives your reports a clean way to group people by source, offer or campaign without touching the contact record itself.

When to use it
right after a contact is created or updated in the same scenario, to label where that person came from.
Watch out
the contact must be known to SegMetrics first, so place this module after Add/Update a Contact.
SegMetrics2

Add/Update a Contact

Action

In Make“Adds a contact to the specified SegMetrics integration or updates an existing one.”

Creates a person in the SegMetrics integration you pick, or refreshes that person when they are already there. One module covers both cases, so you avoid building a search and a branch.

When to use it
a form submission, a new customer in your shop or a CRM change that SegMetrics should reflect.
Watch out
each contact processed costs one operation, the unit Make counts on your plan.
SegMetrics3

Add/Update an Order

Action

In Make“Adds an order to the specified SegMetrics integration or updates an existing one.”

Records a purchase in the chosen SegMetrics integration, or corrects an order it already holds. That is what lets SegMetrics tie revenue back to the lead and the channel behind it.

When to use it
a payment clears in your checkout or billing tool and you want the sale counted in your attribution.
Watch out
the doc does not say whether an order needs an existing contact, so sending the contact first in the same flow is the safe choice.
SegMetrics4

Add/Update a Subscription

Action

In Make“Adds a subscription to the existing contact. If the subscription id already exist, it will be updated.”

Attaches a recurring plan to an existing contact. If SegMetrics already has a subscription with the same ID, the module updates it rather than creating a duplicate, which keeps renewals and plan changes tidy.

When to use it
a customer starts, upgrades or renews a plan in your billing app.
Watch out
map the same subscription ID every time for one plan; a new ID creates a second subscription.
SegMetrics5

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a person from SegMetrics for good, which helps you honor a removal request or clear test records out of your reports. Nothing in Make brings the contact back once the module runs.

When to use it
a customer asks to be forgotten, or a test lead slipped into production data.
Watch out
run it once on a test contact first and put a filter before it, since a wrong mapping deletes the wrong person.
SegMetrics6

Delete an Order

Action

In Make“Deletes an invoice.”

Takes an order out of SegMetrics so your revenue figures stop counting a sale that did not really happen. Make names it Delete an Order, and its short description in the directory speaks of deleting an invoice.

When to use it
a refund, a chargeback or a duplicate order created by a test run.
Watch out
deleting it lowers the revenue attributed to the lead, so keep a copy elsewhere if you audit numbers later.
SegMetrics7

Delete a Subscription

Action

In Make“Deletes a subscription.”

Erases a subscription from SegMetrics, which keeps recurring revenue from showing plans that no longer exist. The contact itself stays in place, only the plan disappears.

When to use it
a subscription was created by mistake, or your billing app removes a plan entirely rather than marking it as cancelled.
Watch out
for an upgrade or a renewal, Add/Update a Subscription is the better choice, because deletion wipes the history of that plan.
SegMetrics8

Delete a Tag

Action

In Make“Deletes a tag.”

Deletes a tag in SegMetrics, handy when a campaign label no longer means anything and clutters your segment filters. It is the cleanup counterpart of Add Tag to Contact.

When to use it
after renaming a source or merging two campaigns, to drop the obsolete label.
Watch out
the documentation does not say whether it removes the tag from one contact or from the whole account, so test it with Run once on a test contact.
SegMetrics9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the SegMetrics API to your scenario, using the connection you already created. You write the request yourself, and Make handles the authentication for you.

When to use it
a SegMetrics feature you need has no dedicated module among the other nine.
Watch out
you need the SegMetrics API documentation to know the endpoint and the expected body, since Make gives no form for them.
SegMetrics10

Record Ad Performance

Action

In Make“Adds the performance for a specific day.”

Stores the results of your ads for a specific day in SegMetrics, so cost and reach sit beside the leads and sales they produced. This is the module that makes return on ad spend readable in one place.

When to use it
an ad platform or a spreadsheet holds daily campaign figures that SegMetrics does not receive on its own.
Watch out
the module records performance for one specific day, so plan one run per date you send.
Need help

Need help automating SegMetrics with Make?

A person reads every message.

FAQ

Questions people ask about SegMetrics and Make

01Is the SegMetrics Make integration free?
Yes, on the Make side. SegMetrics is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. You still need your own SegMetrics subscription, whose pricing is set by SegMetrics.
02What does it take to connect SegMetrics to Make?
An active SegMetrics account and its API key. In SegMetrics, the Gear icon at the top right leads to Account Settings, where you copy the key. In Make, add any SegMetrics module, click Create a connection, optionally fill Connection name, then paste the key. That connection is reused by all 10 SegMetrics modules, so you only do this once per account. If Make refuses the key, copy it again from Account Settings and check that your SegMetrics account is still active.
03Does SegMetrics have a trigger in Make?
No. All 10 SegMetrics modules are actions, so SegMetrics cannot start a scenario by itself. You begin the scenario with the trigger of another app, such as the tool where your leads or sales appear, and SegMetrics receives the data further down the chain. You can also start from the schedule on the first module, which Make sets to every 15 minutes by default and which you can change. Either way, the first SegMetrics module you place still needs the connection described above.
04What if a SegMetrics module is missing in Make?
Use Make an API Call. It sends any request to the SegMetrics API with the connection you already set up, so you reach endpoints the other nine modules do not cover. You will need the SegMetrics API documentation to write the request. Also keep in mind that Make labels its SegMetrics documentation as AI-generated, so confirm important details with SegMetrics. Test the call with Run once on a test record before you switch the scenario on.
05Is Make or n8n better for SegMetrics?
It depends on what you already run. On Make, SegMetrics comes with 10 ready modules covering contacts, orders, subscriptions, tags and ad performance, plus Make an API Call for the rest. Check first whether n8n has a SegMetrics node: many apps have one, but it is not a given. If your other automations already live in one tool, keeping SegMetrics there usually means fewer accounts to maintain. Our n8n vs Make comparison, linked above on this page, lists the criteria that matter.
Same platform

Other docs you might need on this stack.

Browse all integrations