Skip to main content
Yes — you can run your own Google Analytics, Google Tag Manager, or other third-party tracking on an inploi-hosted careers site. inploi careers sites can load custom scripts, so any tracking, tag management, or marketing pixel you already use can be added alongside inploi’s built-in analytics. These are your tools, on your accounts. inploi does not create or manage Google Analytics properties, Tag Manager containers, or third-party tracking accounts on your behalf — you own and configure those with the provider, and we add the code that connects them to your careers site. In other words: you bring the tracking, inploi provides the place to put it.
Third-party scripts run directly on your live careers site. A snippet that is misconfigured, points at the wrong container, or conflicts with the page can slow the site down or stop parts of it working — including navigation and the application flow. Because of this, we recommend asking inploi to add and test tracking for you rather than pasting scripts in yourself. Contact your CSM to get started.

​
What you can add

Anything that is delivered as a standard HTML snippet or script tag, for example:
  • Google Analytics 4 (the gtag.js snippet)
  • Google Tag Manager (container snippet)
  • Marketing and advertising pixels (for example LinkedIn, Meta, or a media agency’s tag)
  • Other analytics or tag-management tools that provide an embed snippet
In each case you provide the snippet or the account identifier (such as your GA4 measurement ID or GTM container ID) from your own provider account.

​
How it works

inploi careers sites include a custom code feature that injects your scripts into the site’s HTML. It has two places code can go, matching the two snippets most tracking tools give you:
FieldWhere it loadsTypical use
End of <head> tagIn the page head, on every loadGoogle Analytics gtag.js, the main Google Tag Manager snippet, most tracking scripts
End of <body> tagAt the end of the page bodySecondary snippets, such as Google Tag Manager’s <noscript> fallback
Custom code can be applied in two scopes:
  • Site-wide — under Settings → Company settings → Custom code, so the tracking loads on every page of your careers site. This is the usual choice for analytics and tag management.
  • A single page — in a page’s settings in the CMS, so the code loads only on that page. Useful for a tag that should only run on one campaign or landing page.
Custom code is an advanced, access-restricted feature, which is another reason it is usually set up with inploi’s help.

​
Page-level tracking vs event-based tracking

It’s important to be clear about what custom code does and does not capture on its own.
  • Page-level tracking — this is what custom code enables. When a candidate visits a page on your careers site, the script loads and records the page view in your tracking tool. This covers the standard behaviour of Google Analytics, Google Tag Manager, and most marketing pixels: page views, sessions, and navigation across the site.
  • Event-based tracking — capturing specific candidate actions, such as starting or completing an application, is not automatic. These events happen inside the inploi SDK, so sending them to your own tracking tool (for example as GA4 events or Tag Manager dataLayer pushes) has to be configured by inploi. Request this through your CSM, describing which events you want to capture and where they should be sent.
Adding a Google Analytics or Tag Manager snippet through custom code gives you page views out of the box. It does not, by itself, forward application-start, application-complete, or other candidate events — those need inploi to wire them up.

​
Getting tracking added

Because badly configured tracking can break a live site, the recommended route is to have inploi implement it for you:
1
Set up the tool on your side
2
Create or open your account with the provider (for example Google Analytics or Google Tag Manager) and get the snippet or identifier you want to use — such as your GA4 measurement ID or GTM container ID.
3
Send it to inploi
4
Share the snippet or ID with your CSM, along with whether it should run across the whole site or on a specific page — and whether you also want specific candidate events (such as application starts or completions) forwarded to your tracking tool.
5
We add and test it
6
inploi adds the code to the right place, publishes it, and checks that the site and application flow still work and that data is reaching your tracking tool.
Third-party tracking you add sets its own cookies and is governed by that provider’s privacy and cookie policies, not inploi’s. The inploi cookie banner controls inploi’s own built-in analytics — it does not automatically manage consent for scripts you add through custom code. If you operate in a region that requires consent (such as the UK or EU), make sure any tracking you add is handled in line with your consent obligations, and that your cookie policy lists the third-party cookies it sets. This is another good reason to plan the setup with inploi rather than adding scripts in isolation. For how inploi’s own cookies and consent work, see Cookies.

​
Do you even need it?

inploi careers sites already include built-in analytics through the inploi SDK — page views, job views, application starts and completions, and UTM and campaign attribution — all viewable in Studio Insights without any extra setup. Many customers find this covers their careers site reporting on its own. You can still run your own tracking alongside it — for example to feed a wider marketing dashboard. If you do, use the same UTM naming conventions across both so the data lines up. See Analytics and tracking and UTM and campaign tracking.