Twilio Segment
Forward Nimriz events to Twilio Segment for downstream warehouse, CDP, and automation workflows.
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
- In your Segment workspace, go to Connections → Sources.
- Click Add Source and choose HTTP API (under Server sources).
- Give it a name like "Nimriz".
- Copy the Write Key displayed in the settings.
2. Set up Segment in Nimriz
- In Nimriz, open Integrations.
- Go to Catalog and choose Twilio Segment.
- Enter your Write Key and save the destination.
- Add an action such as Send event.
- Choose which event types should trigger the action.
- 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 does not forward original IP addresses or complete User-Agent strings to Segment. In standard privacy, Nimriz may use a daily-salted pseudonymous hash as Segment's pseudonymous event identifier where supported. In strict privacy, visitor hashes are omitted and Nimriz uses a synthetic per-click identifier for required destination identifier fields.
Canonical schema fields such as short_url, domain_name, country, device_category, and utm_* are mapped into the Segment properties object automatically. Strict privacy may omit selected granular fields such as city. You can add mapping overrides per action when you need different property names or static values.
Review your Segment source, downstream destinations, notices, and legal basis before enabling forwarding. Do not place personal data, secrets, access tokens, or sensitive data in UTMs, custom parameters, destination URLs, or conversion payloads.
Troubleshooting
If events are not appearing in the Segment Source Debugger:
- Open the Segment destination in Nimriz.
- Open the action you want to verify.
- Check the trigger filters and payload preview.
- Use Send test to this action to confirm the Write Key and payload are accepted.
Related next steps
Ready to test this setup?
Create an account to try the workflow, or compare plans when the setup needs higher limits, integrations, or team controls.