Twilio Segment

Nimriz integrates with Twilio Segment through the HTTP Source API. You set up a Twilio Segment destination once, then add one or more actions to control which Nimriz events should reach that source.

Requirements

You must have a Professional plan or higher to use the Segment integration.

Configuration

To connect Nimriz to Segment, you need the Write Key from a Segment Source.

1. Create a Source in Segment

1. In your Segment workspace, go to Connections → Sources.
2. Click Add Source and choose HTTP API (under Server sources).
3. Give it a name like "Nimriz".
4. Copy the Write Key displayed in the settings.

2. Set up Segment in Nimriz

1. In Nimriz, open Integrations.
2. Go to Catalog and choose Twilio Segment.
3. Enter your Write Key and save the destination.
4. Add an action such as Send event.
5. Choose which event types should trigger the action.
6. Review the payload preview, send a test event, then enable the connection.

Event Payload

By default, Nimriz sends a track call with event names such as Link Clicked, QR Scanned, or the conversion name you configured.

Nimriz uses an obfuscated daily-salted hash of the visitor's IP address (ip_hash) as the anonymousId for Segment tracking, allowing Segment to stitch sessions together pseudonymously. If you enforce Strict Privacy Mode on your workspace, the payload falls back to a synthetic per-click ID instead.

All non-PII canonical schema fields (such as short_url, domain_name, country, device_category, and utm_*) are mapped into the Segment properties object automatically. You can add mapping overrides per action when you need different property names or static values.

Troubleshooting

If events are not appearing in the Segment Source Debugger:

1. Open the Segment destination in Nimriz.
2. Open the action you want to verify.
3. Check the trigger filters and payload preview.
4. Use Send test to this action to confirm the Write Key and payload are accepted.