Nimriz

Integrations

Connect branded link infrastructure to your reporting stack.

Send click, scan, and conversion data from campaign links to the analytics, ads, automation, and warehouse systems your team already uses. Built-in mappings, destination filters, async delivery, privacy-aware redaction.

Browse the catalogView integration docs
  • 12Live destinations
  • 5Connector categories
  • AsyncDelivery model
  • HashedIP & UA logging

Connector catalog

One event model, many destinations.

Live destinations have setup paths today. Unavailable entries stay unlinked until setup docs and review are ready.

Analytics and CDP

7 destinations

Send click, scan, and conversion events to product analytics tools and CDPs.

Live

Google Analytics 4

Send Nimriz events to GA4 with the Measurement Protocol.

Review setup path →
Live

Twilio Segment

Forward Nimriz events into a Twilio Segment source.

Review setup path →
Live

Amplitude

Send Nimriz events into Amplitude.

Review setup path →
Live

Mixpanel

Track Nimriz events in Mixpanel.

Review setup path →
Live

PostHog

Send Nimriz events to PostHog.

Review setup path →
Live

GTM Server-Side

Send Nimriz events to a server-side GTM endpoint.

Review setup path →
Not available

Heap

Auto-capture behavior alongside link, scan, and conversion events.

Ad conversions

8 destinations

Forward conversions to ad platforms via server-side Conversion APIs.

Live

Meta Conversions API

Send conversion events to Meta.

Review setup path →
Live

Google Ads Conversions API

Send conversion events to Google Ads.

Review setup path →
Live

LinkedIn Conversions API

Send conversion events to LinkedIn.

Review setup path →
Live

TikTok Events API

Send conversion events to TikTok.

Review setup path →
Not available

Microsoft UET

Server-side UET conversions for Microsoft Advertising.

Not available

Pinterest Conversions

Forward conversion events to Pinterest for ad measurement.

Not available

Reddit Conversions API

Server-side conversions for Reddit ad campaigns.

Not available

Snap Conversions API

Server-side conversion events for Snapchat advertising.

Pixels and retargeting

1 destination

Inject tracking pixels via a privacy-aware interstitial for audience building.

Live

Ad Pixel Interstitial

Enable a tracking interstitial for pixel-based retargeting.

Review setup path →

Automation and webhooks

4 destinations

Trigger workflows, CRM updates, alerts, and downstream syncs.

Live

Generic HTTP

Send Nimriz events to any HTTP endpoint.

Review setup path →
Not available

Slack

Post conversion and high-value click alerts into Slack channels.

Not available

HubSpot

Sync card contact saves and conversions into HubSpot CRM.

Not available

Salesforce

Push leads and conversions into Salesforce as standard objects.

Warehouses and exports

4 destinations

Recurring reporting and warehouse-bound exports built on the same event layer.

Not available

Snowflake

Native Snowflake share for the Nimriz event tables.

Not available

BigQuery

Streaming inserts into a BigQuery dataset for downstream analysis.

Not available

Databricks

Delta Lake destination for Databricks-based analytics teams.

Not available

Amazon S3

Partitioned Parquet exports to a customer-owned S3 bucket.

  • Google Analytics 4: supports Link click, QR scan, Card view, Conversion
  • Twilio Segment: supports Link click, QR scan, Card view, Conversion
  • Amplitude: supports Link click, QR scan, Card view, Conversion
  • Mixpanel: supports Link click, QR scan, Card view, Conversion
  • PostHog: supports Link click, QR scan, Card view, Conversion
  • GTM Server-Side: supports Link click, QR scan, Card view, Conversion
  • Meta Conversions API: supports Conversion
  • Google Ads Conversions API: supports Conversion
  • LinkedIn Conversions API: supports Conversion
  • TikTok Events API: supports Conversion
  • Ad Pixel Interstitial: supports
  • Generic HTTP: supports Link click, QR scan, Card view, Conversion
  • Heap: supports Link click, QR scan, Conversion
  • Microsoft UET: supports Conversion
  • Pinterest Conversions: supports Conversion
  • Reddit Conversions API: supports Conversion
  • Snap Conversions API: supports Conversion
  • Slack: supports Link click, Conversion
  • HubSpot: supports Card view, Conversion
  • Salesforce: supports Card view, Conversion
  • Snowflake: supports Link click, QR scan, Card view, Conversion
  • BigQuery: supports Link click, QR scan, Card view, Conversion
  • Databricks: supports Link click, QR scan, Card view, Conversion
  • Amazon S3: supports Link click, QR scan, Card view, Conversion

Automation setup guides

Connect workflow tools beside the destination catalog.

Automation and webhooks

Zapier

Connect Nimriz to Zapier triggers and actions using the native app setup path.

Open guide →

Automation and webhooks

Make

Automate workflows with the Nimriz custom app on Make using docs-backed modules.

Open guide →

Automation and webhooks

n8n

Route Nimriz events into n8n workflows using the integration setup docs.

Open guide →

Automation and webhooks

Webhooks

Manage webhook endpoints, signed deliveries, retries, replay paths, and event schemas using the docs.

Open guide →

Why this catalog model

Built for real event delivery, not a logo wall.

01

Async event delivery

Connectors run outside the redirect response path, so forwarding to analytics, ads, and automation never slows the click experience.

02

Privacy-aware redaction

Per-destination rules keep raw IP and full User-Agent out of outbound payloads while preserving the fields teams need for measurement.

03

Reviewed destination details

Setup docs, plan relevance, supported events, and claim review pass before a destination gets promoted to a public detail page.

Canonical event schema

Forward one normalized event shape.

Every destination sees the same schema after normalization. Redaction and per-destination mapping happen after this layer, so adding a new connector never reshapes upstream data.

  • redactRaw IP and User-Agent are hashed before any 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.
Read the overviewAPI reference
event.json
link.qr_scanned
 1{
 2  "event_type":           "link.qr_scanned",
 3  "event_id":             "evt_01HX3R...",
 4  "timestamp":            "2026-04-13T12: 15: 00Z",
 5  "domain_name":          "go.brand.com",
 6  "short_code":           "launch",
 7  "short_url":            "https://go.brand.com/launch",
 8  "touch_type":           "qr_scan",
 9  "country":              "US",
10  "region":               "NY",
11  "device_category":      "mobile",
12  "browser_family":       "Mobile Safari",
13  "referrer_host":        "instagram.com",
14  "utm_source":           "direct-mail",
15  "utm_medium":           "qr",
16  "utm_campaign":         "spring-launch",
17  "variant_key":          "B",
18  "conversion_value":     149,
19  "conversion_currency":  "USD"
20}

Need a destination that’s not in the catalog?

Generic HTTP and webhooks cover most custom workflows. If you have a higher-volume feed or a tool you want help wiring up, send us the stack details and expected flow.

Email integration requestContact us

Related next steps

Google Analytics 4

Review a live integration landing page and setup path.

Developers

Review API, webhooks, authentication, and implementation docs.

Analytics integration use case

See how marketing teams route link events into analytics tools.