Lynkarr Support
Contact us Sign in

Support / Analytics and reports

Putting your own advertising tag on a page

Meta, Google Ads, TikTok and LinkedIn on the pages we host — where it works, where it cannot, and the one thing that fails silently.

Where it works

On the pages we serve for you: digital cards, landing pages and forms. Settings, then Your advertising tags, and paste the ID.

**Not on a code that points at your own website.** We cannot add anything to a page we do not serve, so a tag for your site has to go on your site. A redirect also runs no JavaScript at all, which is why nobody can honestly fire a pixel on one without putting a loading page in front of your visitors — and we would rather not.

What audience you actually get

People who opened your page here. The cookie is written while the visitor is on our domain rather than yours, so it is not the same identifier your own site's pixel writes.

That is worth knowing before you build a campaign on it. It is a real audience — everyone who scanned your code and looked at the page — but it is not the same list as your website visitors, and it will not merge with it.

The one that fails silently

**Google remarketing will not collect visitors in Europe.** Google requires consent signals for EEA and UK traffic, and we do not send them.

Nothing will look broken. No error, no warning in your dashboard, no message in Google Ads. The list simply never grows, and if most of your scans are European it may never grow at all. We would rather you knew that now than after a month of wondering.

Robots never fire a tag

A link shared in Slack, Teams or WhatsApp is fetched by that service before any person clicks it, and email systems scan links for safety when the message arrives. None of them fires your pixel.

This is deliberate. An audience full of data-centre robots is worse than an empty one, because you pay to advertise to it.

We take an ID, not a script

Paste the number, not the code block your ad platform offers you. Some tools accept a whole script; running somebody else's script on a page we also serve for other customers is not something we are willing to do, so we build the tag ourselves from the ID you give us.

Meta calls its ID a **dataset** now rather than a pixel. It is the same number.

What this means for privacy

Our own analytics still set no cookie and store no address. A tag you add is yours — it collects for your ad platform under your own arrangements with them, and whether you need a consent notice is a question about your advertising rather than about us.

What a scan records →The reporting centre →Conversion tracking →
Still stuck? Tell us what happened — we read every message. lynkarr.com