LinkedIn - Audiences
Keep suspicious clicks out of your LinkedIn retargeting audiences. This ensures Campaign Manager builds audiences only from visitors that ClickPatrol has classified as legitimate.
Important check#
Complete these steps before building clean audiences on LinkedIn:
- Set up the ClickPatrol Tag in Google Tag Manager
- Apply the LinkedIn UTM template to your ads by following the LinkedIn integration article
- Check that LinkedIn traffic appears under Reports in your ClickPatrol dashboard
- Place the LinkedIn Insight Tag in the same Tag Manager container
How LinkedIn differs from Meta and Google Ads#
With Meta and Google Ads, you send the ClickPatrol_Legitimate and ClickPatrol_Suspicious events to the platform, then use them to filter the audience. LinkedIn provides no equivalent option. It creates Matched Audiences from page visits and Website Actions recorded by the Insight Tag, or from server-side Conversions API signals. Because Campaign Manager cannot access events in the Tag Manager data layer, it has no field for refining an audience by ClickPatrol classification.
Filtering must happen one step sooner. Rather than firing the Insight Tag for every page view, fire it only after ClickPatrol classifies a visit as legitimate. The Insight Tag never receives suspicious clicks, which keeps them out of every audience LinkedIn creates from that tag.
Step 1: Fire the Insight Tag on clean traffic only#
Follow the setup from the Clean traffic pixel trigger article. The short version is:
- Create a Custom Event trigger in Tag Manager and use ClickPatrol_Legitimate as the event name. Keep regex matching turned off so suspicious traffic never activates the trigger.
- Under Tags, open your LinkedIn Insight Tag.
- Replace the current All Pages (or Page View) trigger with the ClickPatrol Legitimate trigger.
- Publish the container by clicking Submit.
Note: ClickPatrol events fire only for ad traffic containing the UTM and source parameters. As a result, gating the Insight Tag means it stops recording organic or direct visitors. This is the intended trade-off for a retargeting pool that contains only clean ad traffic. To include organic visitors in your LinkedIn audiences as well, leave the Insight Tag on All Pages and accept that those visits remain unclassified.
Step 2: Build the retargeting audience in Campaign Manager#
- Go to your ad account in LinkedIn Campaign Manager.
- In the left menu, click Plan, then select Audiences.
- Select Create audience, followed by Retargeting Audience.
- Choose Website as the source, then define your preferred page rules, such as all pages or your pricing page only. To retarget button clicks, you can instead build from Website actions under Data in the left menu.
- Use a name that makes the gate clear, such as CP Clean visitors 90d, then save the audience.
Every audience created this way contains clean ad traffic because the Insight Tag fires only for visits classified as legitimate. You do not need a separate suspicious audience for exclusions. Those visitors were removed before LinkedIn received them.
A Matched Audience must contain at least 300 members before ad sets can serve on it. Allow up to 48 hours for processing.
Step 3: Use the audience#
- Retargeting: show follow-up campaigns to legitimate visitors who have not converted yet.
- Predictive Audiences: provide the clean retargeting audience as source data, allowing LinkedIn to expand from real visitors rather than a bot-polluted pool.
- Exclusion: remove the audience from prospecting ad sets to avoid paying twice for people already in your funnel.
Monitor the traffic in ClickPatrol#
Your campaign name and ad id pass through the UTM template. In the ClickPatrol dashboard, you can therefore see the legitimate and suspicious traffic totals for each LinkedIn campaign. Check Reports for campaigns with a large suspicious share, then adjust their targeting in Campaign Manager.
Read Building audiences with ClickPatrol: best practices for the strategy behind prioritizing exclusions and using clean lookalike seeds.
Was this article helpful?
Let us know so we can improve our documentation
Need Help?
If something isn't working or you have questions, our support team is here to help you.
Contact Support