Analytics and CDP destinations
Forward click, scan, and conversion events to the tools your reporting stack already uses.
Integrations
Connect Nimriz to analytics, ads, automation, and reporting
Send click, scan, and conversion data to the systems your team already uses. Start with built-in mappings, add destination-specific filters, and keep delivery async and privacy-aware.
15+
Connectors
Async
Delivery model
Observed
Retry posture
Docs-backed
Setup path
Destination ecosystem
Analytics, ad attribution, automation, and recurring reporting
Connector catalog
One event model, multiple downstream destinations
Use named connectors where you want fast setup. Use generic HTTP and webhooks where you need custom workflows. Keep the same Nimriz event layer under all of it.
Ad platforms and retargeting
Measure downstream outcomes and build ad audiences using pixel injection or server-side Conversion APIs.
Automation and custom delivery
Trigger workflows, CRM updates, alerts, and downstream syncs without hand-formatting payloads for every system.
Reporting surfaces
Turn the same event layer into recurring reporting outputs for stakeholders who do not live inside the dashboard.
Why teams choose this model
Built for real event delivery, not just a logo wall
Server-side by default
Connectors run outside the redirect response path, so teams can forward events to analytics, ads, and automation stacks without slowing down the click experience.
Privacy-aware redaction
Destination-specific redaction rules keep raw IP and full User-Agent values out of outbound payloads while preserving the fields teams actually need for measurement.
Default mappings, with room to grow
Named connectors work out of the box, while higher plans unlock filters, mapping overrides, and custom payload composition when your stack needs more control.
Canonical event schema
Forward one normalized event shape
Nimriz normalizes click, scan, and conversion data first, then applies privacy redaction, per-destination mapping, and delivery rules on top. That keeps destinations consistent even when your stack expands.
Example event payload
Redaction and destination mapping happen after this layer
{
"event_type": "link.qr_scanned",
"event_id": "evt_01",
"timestamp": "2026-04-13T12:15:00Z",
"domain_name": "go.brand.com",
"short_code": "launch",
"touch_type": "qr_scan",
"country": "US",
"device_category": "mobile",
"referrer_host": "instagram.com",
"utm_source": "direct-mail",
"utm_campaign": "spring-launch",
"conversion_value": 149
}Need a destination setup that matches your stack?
Start with the public docs if you want the fastest path. If you have a custom workflow, a higher-volume feed, or a tool you want help wiring up, send us the stack details and expected flow.