Question from Reddit user:
Hi everyone! Currently running two Linkedin campaigns, promoting our company event to drive ticket sales. Is there any way to track which ticket sales have been a result of our Linkedin ads? We sell tickets through a third party site (Ticket Tailor) which makes this quite challenging.
Answer from Nabil:
The short answer is:
Tracking sales through a third-party ticketing site like Ticket Tailor is notoriously challenging because the site typically doesn’t allow you to directly install tracking pixels or often strips the crucial attribution data when users click from your ad to the site.
The standard solution of using the LinkedIn Insight Tag on the ticket purchase page is likely failing.
A superior, reliable solution is to implement a server-side data bridge using the Ticket Tailor API to extract the purchase data and sending it directly to LinkedIn via the LinkedIn Conversions API.
This method completely bypasses browser and cross-domain tracking limitations, ensuring you get accurate credit for every sale.
The long answer is:
Your difficulty in tracking sales that originate from LinkedIn Ads and happen on a third-party site like Ticket Tailor is a classic cross-domain tracking problem.
When a user clicks your LinkedIn Ad, they carry the LinkedIn click identifier (li_fat_id) to your landing page.
When they then click a link to the Ticket Tailor site, the browser’s security and privacy settings (like Intelligent Tracking Prevention or ad blockers) often prevent that identifier from being carried over, or the Ticket Tailor platform itself may not be configured to capture or pass it.
The result is that LinkedIn loses the signal and can’t attribute the final purchase conversion.
The best and most resilient solution, especially for third-party platforms with API access, is to pivot to server-side tracking.
This involves setting up a data flow using the Ticket Tailor API, a server-side container hosted on a platform like Stape or Google Cloud Platform, and the LinkedIn Conversions API.
The workflow is as follows: When a ticket is purchased on the Ticket Tailor site, their system (via its API) captures the transaction details.
You can configure a webhook or a scheduled process to actively pull this purchase data from the Ticket Tailor API.
This purchase data, which includes a unique transaction identifier, is then sent to your server container.
Separately, you should have your website, using Google Tag Manager, capture the original LinkedIn click ID (li_fat_id) and the user’s hashed email or phone number and send this first-party data to your server container.
The server container acts as a powerful data middleman: it matches the transactional data from the Ticket Tailor API with the session/user data collected by GTM and then forwards a high-quality Purchase event, along with the user data and the li_fat_id, directly to LinkedIn using the LinkedIn Conversions API.
Because this event is sent server-to-server, it is immune to browser restrictions and cross-domain issues, allowing LinkedIn’s systems to successfully match the conversion back to the original ad click and correctly attribute your sales.
This method provides the highest data accuracy, effectively solving your third-party tracking challenge.
About The Author
