What is the LinkedIn Insight Tag and why audit it?

The Insight Tag is LinkedIn's account-wide tracking script — it powers conversion tracking, retargeting audiences, and demographic reporting. Because it's a single tag covering every campaign, one misfire takes out all of them at once, and because B2B click costs are high, the cost of a silent failure is disproportionate. Phloz records the tag on the account node, with a last-verified date, so verification can be a recurring, assignable task.

Does Phloz pull LinkedIn Ads performance data?

No. Phloz models the account and its Insight Tag as a tracked node — the agency documents and verifies the setup rather than syncing spend. The point of the page isn't another dashboard; it's knowing the B2B tracking has been checked before the client asks why leads dropped.

Why do LinkedIn and GA4 conversion numbers disagree?

Mostly attribution windows and view-through credit: LinkedIn counts conversions on a long post-click and post-view window and credits the LinkedIn touch, while GA4 uses its own model and lookback. A gap is expected. A large or growing gap usually means a tag or conversion-definition problem worth auditing — and a documented, recently verified setup is where that audit starts.

Paid

LinkedIn Ads integration for digital marketing agencies

LinkedIn is the channel B2B agencies cannot afford to mistrack — clicks are expensive, lead volume is low, and a single broken conversion means weeks of optimisation toward nothing. The LinkedIn Insight Tag and its conversion definitions are also the least-audited part of most B2B stacks, because the platform gets a fraction of the day-to-day attention Google and Meta do. Recording the account and its Insight Tag on the map, with a verification date, is how an agency makes checking that tag a routine instead of a reaction to lead reports going quiet.

How Phloz models LinkedIn Ads

What Phloz records about LinkedIn Ads on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

LinkedIn Ads account as a typed node with the account ID, the Insight Tag (partner) ID, and health status (working / broken / missing / unverified)
The audit flags a LinkedIn Ads account with no Insight Tag recorded
Graph relationships: which GTM container fires the Insight Tag, and whether the Conversions API (CAPI) path is wired alongside the browser tag
Last-verified date per account, flagged by the audit after 30 days without a check

Common LinkedIn Ads configuration gotchas

The configuration mistakes agencies most often make with LinkedIn Ads, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

One Insight Tag, many domains: the Insight Tag is account-wide, so a client running several domains needs the tag on every one — agencies routinely tag the main site and miss the booking or microsite subdomain, losing those conversions.
Conversion windows misread: LinkedIn's default windows are 30 days post-click and 7 post-view (each settable to 1, 7, 30 or 90), and view-through conversions count too, so LinkedIn-reported conversions routinely overstate vs GA4. Document the windows so the client isn't blindsided by the platform-vs-analytics gap.
CAPI not deduplicated: agencies adding the LinkedIn Conversions API alongside the Insight Tag without a shared event key double-count conversions — the same fix discipline as Meta CAPI applies here.

At launch (V1)

The LinkedIn Ads account appears as a typed node with the account ID, the Insight Tag (partner) ID as a field, a Conversions API on/off flag, and health status. Conversion definitions aren't modelled, and Phloz reads no LinkedIn data.

Not built yet

Read-only sync via the LinkedIn Marketing API: pull live conversion definitions and Insight Tag firing status into Phloz.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With LinkedIn Ads recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's LinkedIn Ads setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's LinkedIn Ads configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's LinkedIn Ads integration. Honest answers — same data we'd give a friend evaluating the integration.

What is the LinkedIn Insight Tag and why audit it?: The Insight Tag is LinkedIn's account-wide tracking script — it powers conversion tracking, retargeting audiences, and demographic reporting. Because it's a single tag covering every campaign, one misfire takes out all of them at once, and because B2B click costs are high, the cost of a silent failure is disproportionate. Phloz records the tag on the account node, with a last-verified date, so verification can be a recurring, assignable task.
Does Phloz pull LinkedIn Ads performance data?: No. Phloz models the account and its Insight Tag as a tracked node — the agency documents and verifies the setup rather than syncing spend. The point of the page isn't another dashboard; it's knowing the B2B tracking has been checked before the client asks why leads dropped.
Why do LinkedIn and GA4 conversion numbers disagree?: Mostly attribution windows and view-through credit: LinkedIn counts conversions on a long post-click and post-view window and credits the LinkedIn touch, while GA4 uses its own model and lookback. A gap is expected. A large or growing gap usually means a tag or conversion-definition problem worth auditing — and a documented, recently verified setup is where that audit starts.

Other paid and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever