---
title: "List LinkedIn conversion rules"
method: POST
path: "/api/v1/tools/linkedin_list_conversions/execute"
tags: ["LinkedIn Ads"]
---

# List LinkedIn conversion rules

`POST /api/v1/tools/linkedin_list_conversions/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/linkedin_list_conversions/execute`
- Auth: HTTP bearer

Lists the account's conversion rules with their type, tracking method, attribution windows, assigned value and — most importantly — which campaigns (ad sets in Campaign Manager) each one is attached to.
Use when: a campaign shows clicks but no conversions, before creating a WEBSITE_CONVERSION campaign, and whenever you are about to tell a user their ads are not working. On LinkedIn a rule reports nothing against a campaign it is not associated with, and new campaigns inherit no rules at all, so an unattached rule looks exactly like a failing campaign.
Do not conclude "the ads do not convert" until you have checked the campaign appears in a rule's campaign list here. Do not create a duplicate rule because an existing one looks unattached — attach it with linkedin_associate_conversion instead.
Returns one row per rule, plus a warning naming any rule attached to nothing.
If the account has no rules at all, conversion reporting is impossible and a WEBSITE_CONVERSION campaign cannot optimise — say so before anything is built.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object
    - `ad_account_id` string: LinkedIn ad account id — the numeric id from Campaign Manager, as a string ("506699162"). Omit it to use the primary account; pass it when the user manages several.
    - `enabled_only` boolean: Only rules that are switched on.
    - `limit` integer: Maximum rows to return (default 100).
    - `raw_data` boolean: Return compact JSON only (no markdown). Use when you will compute on the result.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)