01
Async event delivery
Server-side destination delivery runs outside the redirect response path, so background delivery does not slow the click experience.
Integrations
Connect Nimriz to your data, workflows, AI tools, and backend.
Send normalized events to managed destinations, automate work across apps, connect MCP-compatible AI clients, or build directly with APIs and signed webhooks.
- 22Live destinations
- 4Public beta destinations
- 6Destination categories
- 4Connection paths
Event pipeline
Normalizedevent shape
3source types
1event schema
5/22featured / live
Ways to connect
Choose the path that matches your stack.
Destinations
Send normalized events to analytics, ad, CRM, alerting, and warehouse destinations.
Browse destinations →
Automation
Build workflows with Zapier, Make, and n8n using Nimriz triggers and actions.
Explore automation →
AI tools
Connect MCP-compatible AI clients to create links, inspect analytics, and check delivery health.
Explore AI tools →
Developer
Build with workspace APIs, Conversion API, and signed lifecycle webhooks.
Explore developer tools →
Managed outbound connections
Destinations catalog.
Browse live and public beta destinations for analytics, ads, CRM, alerts, and data platforms.
Google Analytics 4
Send Nimriz events to GA4 with the Measurement Protocol.
View integration →Twilio Segment
Forward Nimriz events into a Twilio Segment source.
View integration →Amplitude
Send Nimriz events into Amplitude.
View integration →Mixpanel
Track Nimriz events in Mixpanel.
View integration →PostHog
Send Nimriz events to PostHog.
View integration →GTM Server-Side
Send Nimriz events to a server-side GTM endpoint.
View integration →Meta Conversions API
Send conversion events to Meta.
View integration →Google Ads Conversions API
Send conversion events to Google Ads.
View integration →LinkedIn Conversions API
Send conversion events to LinkedIn.
View integration →TikTok Events API
Send conversion events to TikTok.
View integration →Ad Pixel Interstitial
Enable a tracking interstitial for pixel-based retargeting.
View integration →Generic HTTP
Send Nimriz events to any HTTP endpoint.
View integration →Slack
Post conversion and contact-save alerts into Slack channels.
View integration →Microsoft Teams
Post conversion and contact-save alerts into Microsoft Teams through Workflows.
View integration →Google Sheets
Append events to a customer-owned Google Sheet.
View integration →Amazon S3
Write partitioned NDJSON events to a customer-owned bucket.
View integration →BigQuery
Stream events into a customer-owned BigQuery table.
View integration →HubSpot
Send identified conversion activity to HubSpot CRM.
View integration →Customer.io
Send identified conversion activity to Customer.io.
View integration →Klaviyo
Send identified conversion activity to Klaviyo.
View integration →Airtable
Upsert mapped Nimriz events into a customer-owned Airtable base.
View integration →Notion
Create or update event pages in a customer-owned Notion data source.
View integration →Pipedrive
Create completed activities for identified conversions in Pipedrive.
View integration →Attio
Attach identified conversion notes to existing Attio records.
View integration →Discord
Post conversion and contact-save alerts into Discord channels.
View integration →Snowflake
Merge events into a customer-owned Snowflake table.
View integration →Destination delivery
Built for dependable event delivery.
02
Privacy-aware redaction
Per-destination rules keep raw IP and full User-Agent out of outbound payloads while preserving useful measurement fields.
03
Operational visibility
Delivery attempts, retries, and destination health give teams a clear view of how events move through their stack.
Canonical event schema
Forward one normalized event shape.
Every destination sees the same schema after normalization. Redaction and destination mapping happen after this layer, so adding a connector does not reshape upstream data.
- redactRaw IP and User-Agent are hashed before an outbound payload is built.
- mapRename, exclude, include, static, and template overrides per destination.
- filterFilter by event type, country, tag, space, or custom conditions.
- retryFailed deliveries retry with backoff and surface in the audit log.
event.json
link.qr_scanned
{ "event_type": "link.qr_scanned", "event_id": "evt_01HX3R...", "timestamp": "2026-04-13T12:15:00Z", "domain_name": "go.brand.com", "short_code": "launch", "short_url": "https://go.brand.com/launch", "touch_type": "qr_scan", "country": "US", "region": "NY", "device_category": "mobile", "browser_family": "Mobile Safari", "referrer_host": "instagram.com", "utm_source": "direct-mail", "utm_medium": "qr", "utm_campaign": "spring-launch", "variant_key": "B", "conversion_value": 149, "conversion_currency": "USD"}Ready to connect Nimriz to your stack?
Start with the connection path that fits your workflow, then use the docs for implementation details.
