Meta Pixel & Conversions API

Nimriz offers two ways to send data to Meta:

1. Ad Pixel Tracking Interstitial: A brief, optional redirect page that fires the client-side Meta Pixel.
2. Conversions API (CAPI): A server-side integration that securely forwards conversion events directly to Meta's Graph API.

These can be used individually or together for ad campaign measurement. Review your Meta setup, notices, legal basis, and consent requirements before enabling either path.

Requirements

You must have a Growth plan or higher to connect Meta destinations. Server-side CAPI forwarding also requires conversion events to be available in your workspace.

Setup Meta Pixel (Tracking Interstitial)

The Ad Pixel Tracking Interstitial serves a lightweight HTML page containing your Meta Pixel script before redirecting the user to their final destination. This adds approximately 1.5 seconds of latency but allows the client-side pixel to load and fire.

1. Go to Integrations›Destinations›Browse catalog in the Nimriz dashboard.
2. Choose Ad Pixel Interstitial.
3. Set Platform to Meta.
4. Enter your Pixel ID (found in your Meta Events Manager).
5. Leave the Tracking interstitial toggle on only after confirming your campaign disclosure and consent flow where required, then click Test connection.
6. Continue through the Filter events and Review steps, then click Connect destination.

Note: This interstitial behavior applies to plain web redirects. For links resolving to a deep-link mobile app fallback, the interstitial is skipped to preserve deep-linking fidelity.

Setup Meta Conversions API

The Conversions API (CAPI) runs entirely server-side, meaning it doesn't affect redirect speed. When Nimriz receives a conversion event (e.g., from your backend via the Nimriz API), it forwards the payload to Meta.

1. In Meta Events Manager, go to Settings and generate a System User access token for the Conversions API.
2. In Nimriz, go to Integrations›Destinations›Browse catalog.
3. Choose Meta Conversions API.
4. Enter your Pixel ID and paste the System User token into Access Token.
5. Click Test connection, continue through the Filter events and Review steps, then click Connect destination.

Once configured, any recorded conversions in your workspace will automatically be formatted and dispatched to Meta's Graph API.

Frequently Asked Questions

Does the interstitial affect SEO?

Since the tracking interstitial introduces a brief HTML page with a meta refresh, it may affect how search engine crawlers index the final destination compared to a standard HTTP 301/302 redirect. It is recommended primarily for ad campaign links where attribution is the primary goal.

What data is sent to the Conversions API?

Nimriz forwards the conversion event fields configured for the action, such as event name, value, currency, click attribution identifiers where applicable, and redacted link context. Nimriz does not forward original IP addresses or complete User-Agent strings in the canonical server-side payload.

Standard privacy may include daily-salted pseudonymous hashes where supported. Strict privacy omits visitor hashes and selected granular fields such as city. You are responsible for confirming that Meta, your event mapping, and your campaign disclosures have the right legal basis and consent where required.

What should I avoid putting in campaign fields?

Do not place personal data, secrets, access tokens, or sensitive data in destination URLs, short-link paths, UTM fields, custom query parameters, pixel settings, or conversion payloads unless you have an appropriate basis and understand downstream processing.

Can I override the interstitial per link?

The interstitial is controlled by the Ad Pixel Interstitial destination's Tracking interstitial setting for the workspace; the redirect engine also supports a per-link override where one has been set on the link record.