Associate campaigns with a conversion destination
Associate one or more campaigns with this conversion rule. Returns a per-campaign success/failure result so callers can retry only the rows that failed (e.g. wrong campaign type for the rule's objective).
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
1 <= items <= 100Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.ads.addConversionAssociations({ path: { accountId: 'account_abc123', destinationId: 'destination_abc123', }, body: { adAccountId: 'adaccount_abc123', campaignIds: [ 'campaign_abc123', ], },});console.log(data);{
"platform": "linkedinads",
"succeeded": [
"string"
],
"failed": [
{
"campaignId": "string",
"reason": "string"
}
]
}{
"error": "Unauthorized"
}Soft-delete a conversion destination DELETE
LinkedIn-only today. LinkedIn does not expose hard-delete on conversion rules — what their UI calls "delete" is the same `enabled: false` flip we apply here. The rule remains fetchable via GET with `status: 'inactive'`; the unified discovery endpoint hides it by default. `adAccountId` may be passed as a query parameter (recommended) or as a JSON body field for clients that can send DELETE bodies.
Boost post as ad POST
Creates a paid ad campaign from an existing published post. Creates the full platform campaign hierarchy (campaign, ad set, ad).