Our tag on your pages, or on a page we host, is what turns clicks into arrivals and outcomes on your dashboard. Without it those figures read none recorded.
Put this on every page of your site, before the closing body tag, or add it as a Custom HTML tag in Google Tag Manager. It sets no cookie, and we never store a visitor's IP address, name or email: each visitor is counted by a code that changes every day. As it comes, it keeps nothing in the visitor's browser: each visit is credited from the ad link it arrived on.
To credit a booking made on a later visit to the ad that brought them, the tag can keep the ad's details in the visitor's browser for 30 days. UK law needs the visitor's consent for that, so it only happens when your site asks for it: add data-store="on" to a tag that loads only after they say yes (in Google Tag Manager, fire it on your consent trigger), or call tf('consent') on each page once they have agreed, before reporting a booking. Our privacy policy describes what the tag collects; link to it from yours.
<script src="https://itinexads.com/t.js" data-key="demo-visit-wrenmoor-coast" async></script>When an inquiry or a booking happens, tell the tag from your own code: tf('inquiry'), tf('booking', {value: 1200, currency: 'GBP'}) or tf('call'). Or use a thank-you page rule below, which needs no code.
Give us your own pixel ids and the people our campaigns reach become audiences in your own ad accounts: the people who saw or clicked your ads (the ad network fires your pixel when an ad is seen or clicked; in the UK and Europe, only where the reader has agreed to it), and the people who read a page we host for you, with a lead event on the thank-you so you can leave out the people who already asked. The audiences build where you already advertise. We keep none of it.
Meta · seen · https://www.facebook.com/tr?id=7342918650012&ev=itinex_ad_view&noscript=1Meta · click · https://www.facebook.com/tr?id=7342918650012&ev=itinex_ad_click&noscript=1Google Ads · seen · https://googleads.g.doubleclick.net/pagead/viewthroughconversion/118273645/?guid=ON&script=0Google Ads · click · https://googleads.g.doubleclick.net/pagead/viewthroughconversion/118273645/?guid=ON&script=0&label=LdCJ2ta4XqAZEOa&value=1¤cy_code=USDLinkedIn · seen · https://px.ads.linkedin.com/collect/?pid=5120344&fmt=gifLinkedIn · click · https://px.ads.linkedin.com/collect/?pid=5120344&fmt=gifIn Meta, make a website custom audience on the event itinex_ad_view or itinex_ad_click. In Google Ads, a “website visitors” audience on your tag fills by itself. Visitors who click through to your own site arrive tagged utm_source=itinex, so an audience rule on that string catches them too.
A visit to a page whose address starts with the path counts as that outcome, once per visitor per day. The simplest way to count inquiries without touching code.
/thank-youAn inquiry/brochure/sentAn inquiryIf you send visitors on to others, such as member hotels and tour operators, list their sites here. A click from a page with our tag to one of them counts as a partner referral, once per visitor per partner a day, with no code on your side. Clicks to sites not on the list are not kept. To have the dashboard call your results partner referrals, choose it under What you count in Settings.
Our ads already carry these. If you send traffic to the same page from anywhere else, use the plain address, so your own traffic is never counted as ours. They also carry Google Analytics tags (source itinex, medium paid_native, the campaign reference), so our visitors show as one line in your own analytics to check ours against. A page address that has its own utm_ tags keeps them, and gets none of ours.
Fall on the Wrenmoor Coast · VW-0310
https://visitwrenmoor.example/fall?tf=VW-0310&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0310The lighthouse trail, one weekend at a time · VW-0311
https://visitwrenmoor.example/lighthouse-trail?tf=VW-0311&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0311Harbor towns, and what comes off the boats · VW-0312
https://visitwrenmoor.example/harbor-towns?tf=VW-0312&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0312Wrenmoor Food Festival, October 9 to 11 · VW-0313
https://itinexads.com/l/wrenmoor-food-festival?tf=VW-0313&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0313The coast road, by bike or by car · VW-0314
https://visitwrenmoor.example/coast-road?tf=VW-0314&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0314Winter storm-watching breaks · VW-0315
https://visitwrenmoor.example/storm-watching?tf=VW-0315&tfd={platform}&tfs={site}&tfi={campaign_item_id}&tfc={click_id}&utm_source=itinex&utm_medium=paid_native&utm_campaign=VW-0315L-7K3MQ2 · inquiry · Sep 22, 2:05 PM · VW-0313
March 2027 · 2 adults
L-9BQ4HT · inquiry · Sep 20, 1:05 PM · VW-0313
Flexible on dates · 2 adults, 1 child
L-2XPM7D · brochure request · Sep 18, 12:05 PM · VW-0313
A trip in the next few months · October 2026
L-5RTW8N · inquiry · Sep 16, 11:05 AM · VW-0313
April 2027 · 4 adults