Coming soon · LinkedIn Ads integration

LinkedIn Ads integration — coming soon

Native API integration for LinkedIn Ads is in active development. Until then, you can attribute every LinkedIn Ads dollar today with a two-step UTM-and-pixel bridge: tag your LinkedIn Ads URLs with the UTM template below, paste the Admaxxer pixel on your storefront, and our 30-platform smart-referrer classifier (per GL#361) auto-attributes revenue with 365-day first-touch persistence.

Star the integration on /integrations FAQ

The bridge — use our pixel + UTM tagging today

Three steps. About five minutes total.

Step 1 — Install the Admaxxer pixel

If you haven't already, drop the Admaxxer pixel into your storefront's <head>. Works on Shopify, WooCommerce, BigCommerce, Squarespace, Wix, Webflow, and any custom storefront. See install instructions for 35+ platforms.

Step 2 — Tag every LinkedIn Ads URL with UTMs

In the LinkedIn Ads UI, append these query parameters to every destination URL:

Example tagged URL:

https://yourstore.com/b2b-pricing?utm_source=linkedin&utm_medium=cpc&utm_campaign=b2b-icp-2026-q2&utm_content=hero-creative

Step 3 — Revenue auto-attribution kicks in

The first time a visitor lands on your site from a tagged LinkedIn Ads URL, the Admaxxer pixel writes the UTM tuple into localStorage for 365 days. Our pixel already captures li_fat_id from LinkedIn Ads click URLs (per GL#361) — even before native integration ships. When the visitor checks out — even months later, even from a different device that we stitch via email_hash — the order is attributed back to the original LinkedIn Ads campaign on the visitor_payments row.

Tag once, our 30-platform classifier (including AI-chat referrers) does the rest.

What's already working today via UTMs

What native integration will add when shipped

UTM tagging gets you accurate revenue-side attribution today. Native API integration adds spend-side reconciliation and platform-side reporting depth:

LinkedIn Ads specifics

LinkedIn appends a li_fat_id parameter on every Sponsored Content click — Admaxxer's pixel already captures this and writes it onto the visitor_payments row at payment time (per GL#361). UTM tagging adds campaign-level breakdown on top of the click-ID. For LinkedIn organic posts, the classifier maps linkedin.com referrers to utm_source=linkedin&utm_medium=social automatically. Note: Admaxxer's LinkedIn integration roadmap is independent of any LinkedIn DM / messaging tooling — all LinkedIn API code goes through Unipile per the Unipile Rule.

Frequently asked

Why is LinkedIn click-ID coverage already working before native ships?
Per GL#361, the Admaxxer pixel captures 12 click-IDs on every visitor_payments row at payment time — including li_fat_id. So even without the native API integration, every LinkedIn Sponsored Content click that converts in the next 90 days carries the click-ID back to the order row. Native integration adds the spend side; revenue-side attribution is already at full fidelity.
What if my LinkedIn ads land on a non-customer-domain (microsite or LinkedIn Lead Gen Form)?
Lead Gen Forms submit data inside LinkedIn before the user ever lands on your site, so the pixel can't attribute that conversion path. For form-fill campaigns, run a redirect to your storefront with the UTM tuple in the URL — that way the click-through gets pixel-tagged. For pure form fills, native integration (when shipped) will be the canonical attribution path.
Can I see B2B cohort LTV from LinkedIn today?
Yes. Cohort LTV by acquisition campaign is computed from visitor_payments rows where attributed_utm_source='linkedin' (or where li_fat_id is non-empty for click-ID-based cohorts). The 7/30/90-day windows work identically to Meta and Google cohorts.
Does the AI agent know about LinkedIn campaigns?
Once native ships, the agent's get_account_insights and list_campaigns tools will gain a third platform alongside Meta and Google. Until then, the agent can analyze LinkedIn-attributed revenue via query_metrics on visitor_payments — but it can't pause or scale LinkedIn campaigns through Admaxxer yet.

Next steps