Integrations overview
How Nimriz uses the catalog, destinations, and actions to forward events to your analytics tools, CDPs, and ad platforms.
Use destinations when you want Nimriz activity to reach the systems your team already uses for analytics, attribution, and downstream automation.
Most destinations run server-side and asynchronously. Nimriz captures the event, prepares a privacy-safe payload, and delivers it in the background so redirects stay fast.
Destination model
Nimriz uses a CDP-style model with three layers:
- Catalog: browse destinations by job, such as analytics and CDP, ad conversions, pixels and retargeting, or automation and webhooks.
- Destination: configure one external destination with its credentials and workspace-level settings.
- Action: define what Nimriz should send to that destination, which events trigger it, how fields are mapped, and how it should be tested.
This lets one destination own more than one action. For example, you can send all click activity to one Segment action and keep a second action focused on conversions only.
What Nimriz can send
- Click, QR scan, card, and conversion events for analytics, CDP, and webhook-style destinations.
- Conversion events for supported ad platform conversion APIs.
- Client-side pixel fires through the tracking interstitial when a destination must run in the browser before redirect.
Destination categories
| Category | Typical destinations | Best for |
|---|---|---|
| Analytics and CDP | GA4, Segment, Amplitude, PostHog, Mixpanel | Sending Nimriz events into analytics pipelines and downstream CDP workflows |
| Ad conversions | Meta, Google Ads, LinkedIn, TikTok | Sending server-side conversion events for attribution and optimization |
| Pixels and retargeting | Meta Pixel, Google tag, LinkedIn Insight Tag, TikTok Pixel | Firing a browser-side pixel before redirect with the tracking interstitial |
| Automation and webhooks | Generic HTTP, Zapier, Make, n8n | Sending Nimriz events to custom endpoints and automation platforms using native apps or generic HTTP |
Setup flow
- Open Integrations in the dashboard.
- Start from Catalog and choose a destination.
- Create the destination with its credentials.
- Add one or more actions.
- Choose triggers and filters for each action.
- Review the mapped payload in the preview panel.
- Send a test event, then enable the destination.
Mapping and filters
Each action can define:
- Event triggers such as clicks, QR scans, card activity, or conversions.
- Include and exclude filters for touch type, domains, spaces, tags, countries, and bot traffic.
- Field conditions such as
utm_source equals google. - Mapping rules such as rename, include, exclude, static values, and templates.
Delivery model
Background delivery
Named destinations receive events through Nimriz's async delivery pipeline. Connector work does not run on the redirect request itself.
Tracking interstitial
Some ad pixels must execute in the browser. For those cases, Nimriz can serve a short interstitial page that loads the configured pixel and then redirects the visitor to the final destination. This adds a brief delay before redirect and is best used only when browser-side tracking is required.
Privacy and data handling
Nimriz never forwards raw IP addresses or the full User-Agent string. When a destination supports pseudonymous identity, Nimriz uses privacy-safe hashed identifiers and redacted event context derived from the original click.
Plan availability
| Plan | Destination limit | Monthly event volume | Notes |
|---|---|---|---|
| Starter | 0 | 0 | Destinations are not included |
| Plus | 0 | 0 | Destinations are not included |
| Growth | 2 | 10,000 | Core destinations for standard analytics workflows |
| Professional | 5 | 50,000 | Adds click-event webhooks and broader filtering and mapping controls |
| Enterprise | 10 | 500,000 | Adds the full destinations package including advanced ad platform support |
Integrations vs webhooks
- Use destinations when you want Nimriz to format and deliver events to a destination for you.
- Use webhooks when you want signed lifecycle events delivered to your own backend.
- Use the tracking interstitial only when a browser-side pixel must fire before redirect.
Automation platforms
Nimriz has native apps for automation platforms that connect using the same workspace API key and webhook infrastructure:
- Zapier: Instant triggers for all event types, link actions, and search steps. Set up Zapier
- Make: Instant webhook triggers and link modules for scenario automation. Set up Make
- n8n: Official community node with trigger and operations nodes. Set up n8n
These apps use the same event catalog and payload format as webhooks and outbound destinations, so the same event model works regardless of whether you use a native connector, an automation app, or a generic HTTP destination.