Pixels and retargeting
LiveFire a retargeting pixel in the browser before the visitor continues to the destination, with workspace defaults and per-link overrides that keep you in control.
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why Ad Pixel Interstitial with Nimriz
Some ad platforms still need a pixel to execute in the browser. For those cases Nimriz serves a lightweight interstitial page that loads your configured pixel, then forwards the visitor to the final destination. You decide where it applies: workspace-wide defaults with per-link overrides.
Server-side destinations cover most measurement without touching the redirect. The interstitial exists for the cases that genuinely require a browser pixel, and it is scoped deliberately instead of being forced onto every link.
Set the interstitial at workspace level and override it per link. Ad campaign links can carry the pixel while evergreen and SEO-relevant links keep an instant redirect.
When a link uses a mobile app deep-link fallback, the interstitial is skipped automatically so app routing fidelity is preserved.
Under the hood
Enable and configure workspace pixel and interstitial behavior where the plan and setup path support it.
Connector access, mapping controls, and event volume depend on plan. Use pricing and setup docs to confirm the right path before configuring production delivery.
Guided setup
Add the pixel and platform type in the interstitial settings for your workspace.
Enable the interstitial as a workspace default or only on specific links.
Open a test link, confirm the pixel fires, and verify the redirect lands correctly.
Check the ad platform reporting view to confirm pixel events are arriving as expected.
Nimriz uses destination-aware payloads and privacy-aware analytics language. Do not send secrets, raw personal data, or provider credentials in public links.
Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.
Analytics privacy docs
