Tracking V2: set up Google Analytics and ad providers
Tracking V2 transmits purchases, payments and cancellation or refund events from edoobox. Steps up to booking are recorded in the browser. Find configuration under Settings → Google & E-Commerce → Server-side Tracking V2.
Google Analytics, Microsoft Ads and ChatGPT / OpenAI Ads can be activated separately. Microsoft or OpenAI do not require an additional active Google integration. A provider’s availability and credentials depend on the relevant external account.
Prepare the switch
- Identify the person responsible for the website, consent banner and analytics.
- Note the tracking destinations and existing purchase tags used. Check which must be replaced during migration.
- For Google, prepare the V2 web GTM container and website context. For iframe embedding, follow the iframe and consent guide.
- Before enabling Google V2, disable previous edoobox purchase triggers in Tag Manager for the same account. Otherwise the same booking may be counted repeatedly as a purchase.
Previous Google sending remains in place until the activated Google V2 configuration is saved. A GTM server container is not required for direct GA4 sending. If the interface reports the feature as not yet available, have edoobox support clarify account availability.
Set up Google Analytics V2
- Open the web data stream of the desired GA4 property and copy the GA4 measurement ID starting with
G-. - In the same data stream, create a secret for edoobox under Measurement Protocol API secrets. The official route goes through Admin, Data streams, the stream and ‘Create’. See Google: Prepare Measurement Protocol.
- In edoobox, enable Use new tracking integration and Enable Google Analytics V2.
- Enter measurement ID and GA4 API secret. The secret belongs exclusively in the designated credential field.
- Export the GTM V2 container and complete website setup.
- Confirm the prepared V2/consent settings and disabled previous purchase triggers. Click Save tracking settings.
For a new setup, edoobox sends directly to GA4 using Measurement Protocol. The existing web Google Tag Manager continues to handle the browser funnel.
Set up Microsoft Ads
- Obtain the Microsoft UET tag ID and the Microsoft Conversions API token belonging to that tag in your authorised Microsoft advertising account.
- In edoobox, enable Microsoft Ads and enter the numeric tag ID and token.
- In Microsoft Ads, configure appropriate conversion goals for the events supplied. Purchase, payment, cancellation and refund are transmitted as separate custom events.
- Save the configuration and check consent, website helper and initial events.
Do not additionally count payment or cancellation as a purchase. Sending a cancellation/refund does not automatically correct an original purchase in Microsoft Ads.
The Check saved Microsoft configuration button checks completeness of the saved configuration. It does not confirm online access, ownership of the tag or actual receipt.
Set up ChatGPT / OpenAI Ads
- Have the OpenAI Ads pixel ID and corresponding Conversions API key ready. A key for advertising account management serves a different purpose.
- In edoobox, enable ChatGPT / OpenAI Ads and enter pixel ID and Conversions key.
- Save and use Check saved OpenAI configuration. The check uses validation mode and stores no conversion event.
- Then check a controlled booking case and its attribution in the advertising account.
A purchase is transmitted as order_created. Payment, cancellation and refund are separate custom events. They do not automatically correct the original conversion value. Authorised Ads API access is required.
Consent and saved credentials
Google events require appropriate analytics consent and a permitted browser context. Advertising events require consent for ad_storage and ad_user_data. An activation switch does not replace this consent.
Transmit enhanced user data is an additional option. It permits eligible normalised and hashed customer data only with the required advertising consents. Review the option with the person responsible for your data processing.
After saving, credential fields show only whether credentials are stored. Leave a field empty to retain existing credentials. A new value replaces them upon saving; Remove saved credentials explicitly removes them.
Previously configured advanced Google sending routes
For existing configurations, the interface may still show Own server GTM container or Google Data Manager API. These saved routes remain until you deliberately select Switch to direct GA4 sending.
- Server GTM: requires a separately published receiving solution at an HTTPS address with the path
/edoobox/analytics/v2/eventsand the matching access key. A normal web GTM container is insufficient. - Data Manager: requires property ID, OAuth client ID, client secret and refresh token, plus a Google configuration enabled for it.
Have the person managing the integration check these advanced routes. Entering a receiving URL does not provide a server of your own.
Check the result
- Save all changes. Connection checks use the saved values.
- Read the feedback and any warnings. Even a successful Google check does not yet prove visibility in reports.
- Perform a controlled booking with consent and, under Recent events, check provider, event, booking, status and time.
- Compare actual reports in the destination system. Also test refusal and withdrawal of consent.
Next: Set up the website and iframe · Events and troubleshooting · Previous Google integration
Distinguish saving, technical availability and checking
General V2 availability and activation of individual providers must be available in the account. A locked switch cannot be unlocked by entering other tokens. Note the displayed message and have availability clarified.
Connection checks are disabled while changes are unsaved. Save first, check the response and then restart the check. The Google check validates event format; it confirms neither ownership of the measurement ID nor validity of the API secret. Afterwards, check controlled actual receipt in the intended property. See also Google’s event validation guidance.