Analytics and CDP connectors
Forward events to GA4, Segment, Amplitude, Mixpanel, PostHog, or GTM server-side with destination-native payload shapes already prepared for you.
Integrations & destinations
Available on supported plans
Send click and conversion data everywhere it matters
Connect Nimriz to analytics tools, CDPs, ad platforms, and downstream workflows from one destination layer. Use built-in mappings, filter what gets forwarded, and keep delivery async and privacy-aware.
15+
Connectors and destinations
Async
Delivery model
Built-in
Default mappings
app.nimriz.com/integrations
Destinations
Event flow, mapping, and delivery health
4 active
Google Analytics 4Analytics
Filter: qr_scan + campaign tags | Mapping: default + overrides
SegmentCDP
Filter: qr_scan + campaign tags | Mapping: default + overrides
Meta CAPIAds
Filter: qr_scan + campaign tags | Mapping: default + overrides
Generic HTTPWebhook
Filter: qr_scan + campaign tags | Mapping: default + overrides
Canonical event
"event_type": "link.qr_scanned"
"domain_name": "go.brand.com"
"utm_source": "direct-mail"
"country": "US"
Delivery queue
GA4 payload sent204
Segment track call200
Meta retry scheduled+60s
Default
Mappings
Per feed
Filters
Redacted
Privacy
Observed
Retries
What you get
- Send click, scan, and conversion events to tools such as GA4, Segment, Amplitude, Mixpanel, PostHog, Meta, Google Ads, and custom HTTP endpoints.
- Start with built-in connector mappings, then filter or customize what each destination receives without rebuilding the underlying event model.
- Keep outbound delivery privacy-aware with destination-specific redaction, queue-backed retries, and dashboard-visible health signals.
Availability
Available on supported plans
Destination counts, connector access, click-event webhooks, and mapping controls depend on your plan. Teams can start with defaults and unlock deeper customization as needed.
How it works
1
Choose a destination and add credentials
Pick the platform you want to connect, add the required credentials, and enable the destination for the workspace. Named connectors come with sensible defaults so setup stays fast.
2
Control what gets forwarded
Filter by touch type, domain, tag, space, country, or field conditions. Keep broad destinations simple and create focused feeds when a team needs campaign-specific or market-specific routing.
3
Validate, monitor, and iterate
Use test sends and delivery history to confirm payloads, then watch success rate, retry behavior, and recent failures from the integrations dashboard as campaigns scale.
Everything included
Ad Conversion APIs
Send conversion outcomes server-side to Meta, Google Ads, LinkedIn, and TikTok so campaign attribution survives cookie loss and browser restrictions.
Ad pixel injection
Use tracked interstitials and hosted surfaces to fire Meta, Google Ads, LinkedIn, TikTok, Microsoft, or other pixel scripts when client-side retargeting is the right fit.
Automation platforms
Use click-event webhooks, Zapier, Make, n8n, and generic HTTP destinations to trigger workflows, CRM syncs, notifications, and downstream data pipelines.
Generic HTTP destinations
Post events to any compatible endpoint with custom headers, payload templates, and property mappings when you need flexibility beyond named connectors.
Scheduled analytics reports
Turn the same analytics model into recurring daily, weekly, or monthly reports so stakeholders get updates without logging into the dashboard.
How one event fans out across the stack
A single branded short-link interaction can feed multiple downstream tools without changing the redirect path or hand-formatting payloads per platform.
Analytics feed
QR scans stream to GA4 for campaign reporting and to Segment for downstream warehouse sync.
Ad attribution
Qualified conversions forward server-side to Meta CAPI and Google Ads without relying on raw IP storage.
Automation
Click-event webhooks or generic HTTP destinations trigger Slack alerts, CRM updates, or ops workflows.
Control layer
Each destination can apply plan-aware mapping controls, filters, and delivery monitoring independently.
Why this matters beyond a connector checklist
- Most teams do not want to rebuild the same click payload three different ways just to keep analytics, ad attribution, and workflow automation aligned.
- Built-in mappings reduce setup time, while override controls keep advanced teams from getting stuck with rigid defaults.
- Privacy posture belongs in the forwarding layer so redaction rules apply consistently before data leaves Nimriz.
- Queue-backed delivery protects redirect performance while still giving teams observable retries, failure history, and replay-friendly operations.
Ready to try it?
Integrations & destinations — available on Nimriz today
Sign up and start using this feature alongside branded links, analytics, and the full Nimriz platform.