Advanced Tracking Setup: GTM, Stape Server-Side Tracking, Cookiebot, GA4, Google Ads & Bókun Widget Intent Tracking

We are looking for an advanced tracking specialist to set up clean, consent-compliant, server-side tracking for three tourism websites. This is not a basic GA4 or Google Tag Manager task. We need someone with real experience in Web GTM, GTM Server Container, [login to view URL] server-side tracking, Cookiebot CMP, Google Consent Mode V2, GA4 event tracking, Google Ads conversion tracking, WordPress tracking cleanup, event deduplication, Tag Assistant testing, and GA4 DebugView validation. The websites in scope are [login to view URL], [login to view URL], and tourismiceland.co.uk. [login to view URL] is excluded from this project for now because we are building an internal booking engine and do not want to include it in this phase. The required tracking architecture is: Website → Web GTM → Stape Server GTM → GA4 / Google Ads. Cookiebot must control consent before analytics and advertising tags fire. Each website must have only one Web GTM container installed directly in WordPress. No direct GA4, Google Ads, Google tag, Meta Pixel, or other tracking code should be installed directly in WordPress. The freelancer must audit the current tracking setup, remove duplicate or direct tracking codes, confirm one clean Web GTM container per website, configure Web GTM tags, triggers, and variables, create or configure GTM Server Containers, connect the server containers with [login to view URL], configure custom tracking subdomains, configure GA4 events and parameters, configure Google Ads conversions, configure Cookiebot CMP, configure Google Consent Mode V2, set up event deduplication between browser and server events, test everything in GTM Preview, Google Tag Assistant, GA4 DebugView, and Google Ads, and provide full handover documentation. The required Stape custom tracking subdomains are [login to view URL], [login to view URL], and track.tourismiceland.co.uk. The freelancer must provide the required DNS records before implementation. For [login to view URL], the required tracking events are phone_click, whatsapp_click, email_click, generate_lead, santorini_enquiry, transfer_enquiry, private_charter_enquiry, and bokun_widget_click. The Bókun widget click must be tracked only as a secondary booking-intent event. It must not be counted as a confirmed booking, purchase, revenue event, or primary Google Ads conversion. The event name should be bokun_widget_click. This event is useful to understand booking intent only, not completed sales. Primary Google Ads conversions for [login to view URL] should be generate_lead, santorini_enquiry, transfer_enquiry, and private_charter_enquiry. Secondary conversions should be phone_click, whatsapp_click, email_click, and bokun_widget_click. For [login to view URL], the required tracking events are phone_click, whatsapp_click, email_click, contact_form_submit, private_tour_enquiry, family_tour_enquiry, luxury_tour_enquiry, group_tour_enquiry, tailor_made_enquiry, generate_lead, and booking_intent_click. The website has multiple enquiry forms, so all form submissions should use the main GA4 event generate_lead, with parameters to separate each form. Required parameters are form_name, form_type, page_url, and business_unit. Example form_name values are contact_form, private_tour_enquiry, family_tour_enquiry, luxury_tour_enquiry, group_tour_enquiry, and tailor_made_enquiry. Primary Google Ads conversions for [login to view URL] should be generate_lead, private_tour_enquiry, family_tour_enquiry, luxury_tour_enquiry, group_tour_enquiry, and tailor_made_enquiry. Secondary conversions should be phone_click, whatsapp_click, email_click, and booking_intent_click. For [login to view URL], the required package funnel events are search_package, select_package, select_hotel, select_add_ons, continue_to_payment, and purchase. The required lead events are phone_click, whatsapp_click, email_click, generate_lead, quote_request, private_group_form_submit, package_enquiry, tailor_made_enquiry, and contact_form_submit. The purchase event must include transaction_id, value, currency, item_name, item_id, item_category, and booking_type where available. If these values are not available from the current website, the freelancer must clearly explain what developer support is needed. Primary Google Ads conversions for [login to view URL] should be purchase, generate_lead, quote_request, private_group_form_submit, and package_enquiry. Secondary conversions should be phone_click, whatsapp_click, email_click, search_package, select_package, select_hotel, select_add_ons, and continue_to_payment. All GA4 event names must use clean lowercase format with underscores only. Correct examples are phone_click, whatsapp_click, email_click, generate_lead, quote_request, search_package, select_package, select_hotel, continue_to_payment, purchase, and bokun_widget_click. Do not use event names with spaces, commas, slashes, random capital letters, or names like search_flight/hotel, explore_tour, select_hotel, Book Package Now, or GTM - Purchase. Cookiebot must be installed and configured properly. Google Consent Mode V2 must be configured with analytics_storage, ad_storage, ad_user_data, and ad_personalization. Analytics and advertising tags must respect user consent. The setup must be tested in Cookiebot, GTM Preview, Google Tag Assistant, GA4 DebugView, and Google Ads. The server-side tracking setup must include Web GTM container configuration, GTM Server Container configuration, [login to view URL] server hosting, custom tracking subdomains, GA4 server-side routing, Google Ads server-side conversion routing, event deduplication between browser and server, clean event parameters, and consent-aware tracking. The final handover must include a full tracking implementation map, GTM Web container export JSON for each website, GTM Server container export JSON for each website, screenshots of all GTM tags, triggers, and variables, Stape server container details, Stape custom domain and DNS records, Cookiebot setup screenshots, Consent Mode V2 validation screenshots, GA4 event list, GA4 DebugView proof, Google Ads conversion action screenshots, primary and secondary conversion list, Tag Assistant proof for each website, final QA report confirming no duplicate tracking, and confirmation that no direct tracking code is installed in WordPress. Important restrictions: do not install tracking codes directly in WordPress except the approved Web GTM container. Do not install GA4 directly in WordPress. Do not install Google Ads tags directly in WordPress. Do not install Meta Pixel directly in WordPress. Do not mark page views as primary conversions. Do not mark WhatsApp clicks as primary conversions. Do not mark phone clicks as primary conversions. Do not mark Bókun widget clicks as primary conversions. Do not count Bókun widget clicks as purchases. Do not include [login to view URL] in this project. We are running active Google Ads campaigns, so the setup must be done carefully. We cannot afford duplicate conversions, broken tags, wrong primary conversions, or messy tracking. The objective is clean tracking for better reporting, better Google Ads optimisation, and future Meta marketing setup. Meta Pixel and Meta CAPI are not included in this phase, but the setup should be prepared so Meta can be added later through GTM / Stape without rebuilding everything. Please apply only if you have real experience with [login to view URL] server-side tracking and Cookiebot Consent Mode V2. In your application, please answer the following questions: How many [login to view URL] server-side tracking projects have you completed? Can you set up GTM Server Container, not only Web GTM? Can you configure Cookiebot with Google Consent Mode V2? Can you configure event deduplication between browser and server events? Can you show proof or screenshots of similar work? Can you provide GTM Web and Server export JSON files after completion? Can you work with WordPress websites? Can you test with Tag Assistant and GA4 DebugView? Can you configure Google Ads primary and secondary conversions? What access do you need? What is your fixed price? How many working days do you need? Will you provide full handover documentation?

Project ID: 40614641