Connect LinkedIn Conversions API
Send LinkedIn conversion events through a trigger.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
access_token | Access token authorized for conversion tracking. |
conversion_id | Conversion ID. |
linkedin_version | Optional API-version override; leave the displayed default unless instructed. |
Connect
Open Integrations, find LinkedIn Conversions API, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
Verify the result
The check reads the configured conversion. It does not send a conversion event.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Confirm token access to the conversion and check whether an overridden API version is still supported.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.