Part of Website and builder
Why add your own tags
TripNerve already counts visits and leads for you under Analytics. Your own tags matter when you spend money on ads. Google Ads and Meta need to know which clicks became an enquiry so they can bid for more people like that, and an agency you work with may want everything in its own Google Analytics property.
In the website's Analytics and ads panel there are three fields: Google Analytics 4 measurement ID (G-XXXXXXXXXX), Google Tag Manager container ID (GTM-XXXXXXX) and Meta Pixel ID (a number). Each field says where to find the ID. You can paste the whole install code from Google or Meta instead, and TripNerve picks out the ID. An ID in the wrong format is flagged and not saved.
Consent first
Many trekkers come from the EU and the UK, where tracking cookies need consent. Your tags load only after a visitor presses Accept on the cookie banner. The banner names your company and the tools you added, in the site's language, and a Cookie choices link in the footer reopens it later. If someone who accepted changes to Decline, TripNerve clears the GA4, Google Ads and Meta cookies and reloads the page so the tags stop.
TripNerve's own analytics tag also runs on every published company site under Google Consent Mode, with storage denied until the visitor accepts, which is why the banner shows on every site and names TripNerve as well as your company.
The events your site sends
Without conversion events, a tag only sees page views and you are left guessing which ad brought the Annapurna enquiry. TripNerve sends an event to each tag the visitor allowed when a form goes through successfully:
- Enquiry sent: generate_lead (lead_type enquiry) in GA4, enquiry_submitted in Tag Manager, Lead in Meta
- Booking request sent: generate_lead (lead_type booking_request) in GA4, booking_request_submitted in Tag Manager, Schedule in Meta
- Newsletter sign-up: sign_up in GA4, newsletter_signup in Tag Manager, CompleteRegistration in Meta
- Trip name and number of travellers go with enquiry and booking events where known
No double counting
Because TripNerve's own tag and yours can both be on the same page, they are kept apart. Your Tag Manager container reads its own data layer and your GA4 tag its own, so neither sees the other's events and an enquiry is never counted twice in your property. TripNerve's container receives its copy of the events whatever tags you add.
Tag Manager events carry trip_name and, for booking requests, travellers as data layer variables. You can pass them on to Google Ads as the conversion's label, or build a trigger that fires only for Everest enquiries if that is the campaign you are measuring.
Your own tags load only after consent. TripNerve's own visit counts, under Analytics, need no cookies and count every visitor, so they will always be higher than what GA4 or Meta show. Use your tags to steer ads, and TripNerve's Analytics for the true totals.
What to do in each tool
In Google Analytics, mark generate_lead as a key event, then import it into Google Ads as a conversion. In Tag Manager, build a custom event trigger on enquiry_submitted or booking_request_submitted and fire your Google Ads or LinkedIn tags from it. In Meta Events Manager, Lead and Schedule appear as standard events you can optimise ad sets for. Meta's page views are sent on each page, including pages opened without a full reload.
Worked example
Measuring a Manaslu campaign on Meta
Khumbu Path spends USD 600 on Instagram ads in September 2026 for its 16-day Manaslu Circuit at USD 1,690 a person, aimed at trekkers in Germany and the UK.
| Step | Where | Result |
|---|---|---|
| Add Meta Pixel ID | Analytics and ads panel | Loads after Accept |
| Optimise for Lead | Meta Ads Manager | Ads shown to people likely to enquire |
| Visitors who accept cookies | Banner | 62% of ad visitors |
| Enquiries from the ad | Meta: Lead events | 11 |
| Booking requests | Meta: Schedule events | 3, for 7 travellers |
Meta reports 11 Lead events and 3 Schedule events. Because only visitors who accepted cookies are tracked, the real totals are higher: the company's own Analytics page, which counts without cookies, shows 17 enquiries and 4 booking requests from social media that month. At USD 600 for 21 leads, each lead cost about USD 29.
Two of the booking requests are for the Saturday 10 October departure. The office accepts them in TripNerve and arranges payment by bank transfer as it always has, since TripNerve doesn't take payments, and the campaign runs again for spring.
Common mistakes
Pasting the ID in two places
If your Tag Manager container already fires GA4, don't also add the GA4 ID, or page views count twice in your property.
Not marking key events
generate_lead arrives in GA4 but counts as a conversion only after you mark it as a key event and import it into Google Ads.
Expecting every visitor in GA4
Visitors who decline cookies aren't tracked by your tags. Use TripNerve's Analytics page for the full count.
Pasting tags into an embed
An embed element runs in a sandboxed frame of its own, so a tag pasted there can't see your pages or the lead events. Use the three fields instead.

