Resources · Make integration

Segment Make integrationAutomate Segment with Make.

What if your other tools could feed Segment without a developer? The Segment Make integration gives you 5 action modules: identify people, record what they do, group them and merge identities. This page shows how to connect your account and build a first scenario.

Try the Segment integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Segment Make integration actually do?

The Segment Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) push data into Segment. Segment has no trigger in Make, so it always sits after something else: a new lead, a paid order, a support ticket. Make then tells Segment who the person is and what they did.

Profiles that stay complete. When a CRM or a form app gets a new contact, Identify hands that person to Segment, and Track records the action that brought them in. Marketing sees the sign-up without anyone exporting a file.

Accounts, not just people. A B2B team can attach each user to their company with Group, so reports roll up by customer account. When someone who browsed anonymously finally signs in, Alias ties the two identities together.

Offline events in the same stream. A refund processed by finance or a call logged by sales never touches your website. Make can send it through Track or, for a request the other modules do not cover, through Make a Tracking API Call.

What Make cannot do here: watch Segment. None of the 5 modules is a trigger, so a scenario never starts from a Segment event. The official help page also flags its content as AI-generated, so check anything critical against Segment's own documentation.

Segment also has a node in n8n: the Segment n8n integration covers it, and n8n vs Make helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Segment to Make?

  1. 01

    Grab your API key in Segment

    In your Segment workspace, open the event streams source you want to feed, click Settings, then the API Keys tab. Copy the key shown there. You also need an active Segment account with a Workspace API token.

  2. 02

    Open the connection window in Make

    Add any Segment module to your scenario and click Create a connection. A connection is your Segment account linked to Make once, then reused by all 5 modules. Give it a clear Connection name if you run several sources.

  3. 03

    Enter the credentials and save

    Enter the credentials you copied from your Segment account, or follow the on-screen instructions, and save. From then on every Segment module in any scenario can pick this connection from a list, with no need to paste anything again.

First scenario

Your first scenario: turn a new sign-up into a Segment profile

GoalWhen a new sign-up arrives in another app, Make identifies the person in Segment and records the sign-up as an event.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where sign-ups happen (a form tool or your CRM) and its trigger for new entries.

  2. 02

    Add Identify

    Click the + to the right of that trigger, search for Segment and choose Identify. Select your connection, or click Create a connection if this is the first time.

  3. 03

    Map the person

    Fill the Identify fields with data from the first module: Make shows the values each bundle (one item passing between modules, here one sign-up) carries, and you click to insert them.

  4. 04

    Add Track

    Add a second Segment module, Track, and map the same person plus a clear event name for the sign-up. Now Segment knows who the person is and what just happened.

  5. 05

    Test with Run once

    Create a test sign-up, then click Run once. Open the bubbles above each module to read the bundles they received, and check in Segment that the event arrived.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a scheduled trigger) and turn the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

The 5 Segment modules in Make

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

Segment1

Alias

Action

In Make“Associates one identity with another or merges two identities.”

Alias links one identity to another, or merges two of them, so the history of a visitor and the history of the account they later create end up on a single person in Segment.

When to use it
right after a login or a sign-up in another app, when you hold both the old and the new identifier for the same human.
Watch out
merging is hard to picture before it happens, so try it on a test identity and look at the result in Segment first.
Segment2

Group

Action

In Make“Associates an individual user with a group.”

Group attaches a user to a group, which in most B2B setups means their company, team or workspace. Your Segment reports can then speak in accounts as well as individuals.

When to use it
a deal closes in the CRM, or an invited colleague joins a customer account in your product, and you want that membership recorded.
Watch out
map the same user identifier as in Identify, or the membership ends up on someone else.
Segment3

Identify

Action

In Make“Identifies a user.”

Identify tells Segment who someone is. It is the module that turns a row in your CRM, a form entry or a new customer into a recognised user that later events can hang on.

When to use it
whenever a person appears or their details change in another tool, for example a new lead or an updated job title.
Watch out
map the same identifier in every scenario, otherwise the same person can show up twice in Segment.
Segment4

Make a Tracking API Call

Action

In Make“Performs an arbitrary authorized HTTP tracking API call.”

This module sends an authorized request of your own to Segment's tracking API, reusing the connection you already created. It is the escape hatch when the four ready-made modules do not match what you need to send.

When to use it
a call the tracking API accepts but Alias, Group, Identify and Track do not expose.
Watch out
you write the request yourself, so keep Segment's API reference open and test every change with Run once.
Segment5

Track

Action

In Make“Records a user's actions.”

Track records something a user did: a purchase, a demo booked, a subscription cancelled. Each call becomes an event on that person's timeline in Segment, next to what your website already sends.

When to use it
an action happens outside your site or app, in billing, support or sales, and your analytics would otherwise miss it.
Watch out
keep event names identical across scenarios, since a small spelling change creates a separate event in your reports.
Need help

Need help automating Segment with Make?

A person reads every message.

FAQ

Segment Make integration: common questions

01Is the Segment Make integration free?
Yes, on the Make side. Segment is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations: one module running on one bundle is one operation. Your Segment subscription is separate and follows Segment's own pricing.
02What does it take to connect Segment to Make?
An active Segment account with a Workspace API token, and a Make account. In Segment, open the event streams source you want to feed, go to Settings, then the API Keys tab, and copy the key. In Make, add a Segment module, click Create a connection, optionally name it, and enter the credentials you copied or follow the on-screen instructions. The connection is then available to all five Segment modules in every scenario you build.
03Does the Segment Make integration react in real time?
It depends on what starts the scenario, because Segment has no trigger in Make. All five modules are actions, so the scenario begins with another app: a CRM, a form tool, a payment app. If that first module is an instant trigger, the app calls Make through a webhook as soon as something happens. If it is a scheduled trigger, Make checks on the scenario schedule, every 15 minutes by default. You can also run a scenario on a plain schedule.
04What if the Segment module you need is missing?
Start with Make a Tracking API Call. It sends an authorized request of your choice to Segment's tracking API using your existing connection, which covers calls the four other modules do not offer. There is no module to read data out of Segment, so pulling reports back into another tool is out of reach with this app. For those cases, another app or a custom build is the route, and the team can help you pick one.
05Make or n8n for Segment: which one fits?
Both tools can send data to Segment, so the choice rests on your wider setup rather than on Segment itself. On the Make side you get five named modules (Alias, Group, Identify, Track and a tracking API call) inside a visual editor where each run shows the bundles it passed. n8n also has a Segment node. Compare the actions each one offers against the events you plan to send, then look at where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations