LinkedIn Conversions API

The LinkedIn Conversions API allows you to send conversion events directly from Nimriz to LinkedIn without relying exclusively on client-side tracking.

Review your LinkedIn setup, notices, legal basis, and consent requirements before enabling this destination.

Requirements

You must have a Growth plan or higher to connect the LinkedIn Conversions API destination. Server-side CAPI forwarding also requires conversion events to be available in your workspace.

Nimriz manages the LinkedIn OAuth app. You authorize the LinkedIn ad account and select the conversion rule settings Nimriz should use.

Setup

1. In your LinkedIn Campaign Manager, navigate to Analyze > Conversion Tracking.
2. Create a new conversion or view an existing one, and note its conversion rule ID.
3. In Nimriz, go to Integrations›Destinations›Browse catalog.
4. Choose LinkedIn Conversions API.
5. Enter your Conversion Rule ID. Optionally add your Sponsored Account URN.
6. Continue through the Filter events and Review steps, then click Connect destination.
7. Open the destination detail page, click Connect provider, sign in to LinkedIn, and authorize Nimriz for conversion delivery.
8. After the provider status is connected, use Send test event to verify delivery.

Once active, any recorded conversion event (via the Nimriz API or post-back webhook) will be transmitted to LinkedIn as a server-side conversion payload.

Existing LinkedIn destinations that were configured with a manually supplied access token continue to run during the transition. New dashboard setup uses managed provider authorization instead of pasted provider tokens.

Privacy Notes

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.

Treat LinkedIn click IDs and similar identifiers as purpose-bound attribution identifiers. 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.