Zernio
APIFor you
Zernio
APIFor you
API Reference

Conversions API

List account conversion goalsGETList conversion actionsGETList associated campaignsGETList conversion destinationsGETList custom conversion goalsGETCreate website conversion actionPOSTCreate a conversion destinationPOSTCreate a custom conversion goalPOSTGet a conversion destinationGETGet attribution metricsGETGet Event Match QualityGETUpdate account conversion goalsPATCHUpdate a conversion action's settingsPATCHUpdate a conversion destinationPATCHUpdate a custom conversion goalPATCHDelete a conversion destinationDELETEAssociate campaignsPOSTAdjust uploaded conversionsPOSTRemove associated campaignsDELETERemove a custom conversion goalDELETESend conversion eventsPOST
Dashboard
OverviewPlatformsAPI ReferenceResources
Conversions API

List associated campaigns

Lists the LinkedIn campaigns that track a conversion rule, so you can spot newer campaigns that still need linking.

LinkedIn-only today. Returns the campaigns currently associated with this conversion rule. Auto-association on rule creation runs once at create time; campaigns created after the rule still need explicit association.

PlatformsLinkedIn
GET
/v1/accounts/{accountId}/conversion-destinations/{destinationId}/associations

Authorization

bearerAuth
AuthorizationBearer <token>

API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.

In: header

Path Parameters

accountId*string
destinationId*string

Query Parameters

adAccountId*string

Response Body

application/json

application/json

application/json

application/json

import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.conversions.listConversionAssociations({  path: {    accountId: 'account_abc123',    destinationId: 'destination_abc123',  },  query: {    adAccountId: 'adaccount_abc123',  },});console.log(data);
{  "platform": "linkedinads",  "associations": [    {      "campaignId": "string",      "conversionId": "string",      "associatedAt": 0    }  ]}
Was this page helpful?

List conversion actions

Lists the conversion actions in a Google Ads account, with the website tag snippets to install where available. Lists Google Ads conversion actions on the resolved customer, all types by default. Each action's `tagSnippets` (global site tag + event snippet) is included when Google has them for that action's type, e.g. `WEBPAGE`. Google-only; other platforms return `501`. Requires the Ads add-on. `adAccountId` (alias `customerId`) is optional: when omitted, it is resolved from the connection's accessible Google Ads customers, and the call fails with `400` when more than one is accessible (pass `adAccountId` to disambiguate). The list itself is cached for the quota window (1 hour fresh, up to 7 days last-good; the cache key does not vary on `type`). The response carries `cachedAt` and `stale`, set when a quota-exhausted call falls back to the last-good copy instead of a live read.

List conversion destinations

Lists where an ad account can receive conversion events (pixels, conversion actions or rules), so you know where to send them. Returns the list of pixels (Meta), conversion actions (Google), conversion rules (LinkedIn), pixels (OpenAI Ads, Reddit) or ad accounts (Pinterest) accessible to the connected ads account. Use the returned `id` as `destinationId` when posting to `POST /v1/ads/conversions`. For Google and LinkedIn, each destination's `type` reflects the conversion type (PURCHASE, LEAD, SIGN_UP, etc.), and the event type is locked to the destination. For Meta, OpenAI Ads and Reddit, `type` is absent: pixels accept any event name per request. For Reddit, the pixels of every ad account the connection reaches (only the scoped ones when the connection has an ad-account scope), each with the `adAccountId` that owns it. Reddit pixels are created in Reddit Ads Manager, not through Zernio. For LinkedIn, destinations are returned across every sponsored ad account the connected token can access; the `adAccountId` field on each destination identifies the parent ad account and is required for subsequent CRUD calls (update, delete, associations, metrics).