Skip to main content

LinkedIn Ads

Fancified

LinkedIn Ads for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/linkedin-ads-ui npm install @particle-academy/linkedin-ads-ui
Node @particle-academy/linkedin-ads-js npm install @particle-academy/linkedin-ads-js
PHP 8.4+ particle-academy/linkedin-ads-php composer require particle-academy/linkedin-ads-php
Python 3.11+ fancy-linkedin-ads pip install fancy-linkedin-ads

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No LinkedIn Ads SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A LinkedIn Ads connection holds 4 values.

Two kinds of value, and mixing them up matters. A provider credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An account credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

Field Scope Secret Where it comes from
OAuth client ID per installation not secret From the LinkedIn Developer application's Auth tab; one value for the whole installation.
OAuth client secret per installation secret From the same application. Used by the host for code exchange and programmatic refresh, never sent to the Marketing API.
Member access token per connected account secret Per connected LinkedIn member. It expires after 60 days and only reaches Ad Accounts where that member has a sufficient role.
Programmatic refresh token per connected account secret Per connected member, available to approved Marketing Developer Platform partners. It keeps its original one-year expiry when reused.

Authorising

LinkedIn Ads uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

The refresh tokens do not rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.

The estate

LinkedIn Ads has a test estate on the same host, reached with credentials from a SEPARATE test account you register. Selecting sandbox mode uses those credentials.

LinkedIn's test estate is one API-created test Ad Account per developer application. It uses the same host and member OAuth flow, but every child campaign and creative inherits the account's test flag, creatives are never served, and campaigns are not billed. The account cannot later be converted between test and production.

What it can do

Actions

campaign_get — LinkedIn ad campaign

Retrieve one LinkedIn advertising campaign.

GET /rest/adAccounts/{adAccountId}/adCampaigns/{campaignId} · reads only — safe to replay

Input Required What it is
adAccountId yes The numeric Sponsored Account id from Campaign Manager; send digits only, without the urn:li:sponsoredAccount: prefix.
campaignId yes The numeric campaign id within that Ad Account; send digits only, without a sponsoredCampaign URN prefix.

Run it before you have credentials

Every operation ships a faker, whether or not LinkedIn Ads has a sandbox. Set a node's mode to fake and it returns the shape LinkedIn Ads actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/linkedin-ads; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-linkedin-ads 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-linkedin-ads 0.2.1
File Size Uploaded Provenance Actions
fancy_linkedin_ads-0.2.1.tar.gz 21.2 kB Without provenance Details for fancy_linkedin_ads-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-linkedin-ads 0.2.1
File Interpreter ABI Platform Actions
fancy_linkedin_ads-0.2.1-py3-none-any.whl Python 3 none any Details for fancy_linkedin_ads-0.2.1-py3-none-any.whl

Total release size: 42.7 kB

Release files / fancy_linkedin_ads-0.2.1.tar.gz

Download URL fancy_linkedin_ads-0.2.1.tar.gz
Size 21.2 kB
Tags Source
SHA-256 checksum
How to use checksums
b3fca9ee62d0ef4f46c73bedfee99bf5cb6ccb3cfc4fe640e5b603eb2c1b44fd
BLAKE2b-256 checksum
How to use checksums
73caf6e5000265c3c3e51939e213f4faa29fe63c22f89edba252faf11042ab43
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Release files / fancy_linkedin_ads-0.2.1-py3-none-any.whl

Download URL fancy_linkedin_ads-0.2.1-py3-none-any.whl
Size 21.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
81e75bab35fee173d94fd9e68452066c58b368b05e51ca7bc8d62b839d080dad
BLAKE2b-256 checksum
How to use checksums
bd4ca3a88810d785fac07a86d9fdc90038061ac6f5cf2982b1927d379df426c6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-linkedin-ads 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page