What this checkpoint covers
Hennovrix Bridal is an invented bridal wear boutique. Brides book fittings in a third-party scheduling widget in a frame, pay a deposit on a payment provider's hosted page without the boutique's tag, and can sign in to move appointments. Its CRM also sends appointments to Meta. The questions apply the tutorial on ad platform tags from one data layer, the guide to tracking embedded widgets and hosted pages and the guide to User-ID and signed-in users.
Hennovrix Bridal: one month of appointments and sign-ins
| Measure | Figure |
|---|---|
| Appointments in the CRM | 312 |
| Meta appointments, pixel and server | 587 |
| Analytics appointments, from the widget's own measurement ID | 298, of which 263 on direct |
| Visitors who signed in at least once | 214 |
| Users in the interface after a User-ID launch: device-based / blended identity | 4,060 / 3,930 |
Task
- For each scenario, say what Hennovrix should change and which part of the event contract, the hop or the User-ID decision it protects, before opening the explanations.
- Then compare, and reopen the guide section behind any answer you got wrong or got right for the wrong reason.
Questions
- The agency wants a Meta tag on the "Book a fitting" button and a Google Ads tag on the widget's confirmation view, each built the way that platform prefers. What do you propose instead?
- Meta reports nearly twice the appointments the CRM holds. The pixel and the CRM each generate their own identifier. What fixes it, and which value do you use?
- The scheduling vendor offers a field for a measurement ID, documents a message to the parent page when a booking completes, and lets you set a return address. Which records the appointment, and how is the event named?
- A developer proposes adding the payment provider's domain to the cross-domain settings so deposits keep their source. What do you say?
- The marketing manager wants each signed-in bride's hashed email address sent as the User-ID to make user counts exact. Is a User-ID worth sending here, and with what value?
- After launch, users in the interface fall while sessions hold steady, and an analyst reports brides by counting distinct device identifiers in the export. What happened, and what is the right count?
- A visitor declines analytics and advertising, then signs in. The widget loads its own tracking and the CRM sends every booking to Meta. What must change?
Answers explained
- One business event mapped to every platform. The site pushes one event when the appointment is confirmed, and every tag reads it through a mapping table. A click counts attempts and a page view counts reloads; with one push, a gap between platforms is attribution, not tagging. See one business event, many platforms.
- One event ID, created with the appointment. Use the appointment reference: it is pushed through the Data LayerA structured object on a web page that passes values to a tag manager for tags to use. into the pixel's event ID field, and the server takes the identical value from the appointment record and sends it under the same event name, promptly and unchanged on retries. Two random values never match, so DeduplicationRemoving double counts when one conversion is reported by more than one source. fails. See sharing an event ID with server sends.
- The documented message or the return page, not the in-frame tag. That tag records the widget as its own visit without the source, which is why most bookings sit on direct. A listener that checks the sender's domain turns the message into the boutique's own event, named as any other appointment with a provider parameter; the measurement plan names one signal as the record. See recording the outcome where you control the code.
- No: the linker needs the tag on both sides. List the provider as an unwanted referral, return payers to a confirmation page, confirm non-returners from the order system with the same identifier, and store the visit's source against a reference passed to the provider. See keeping the source across the hop.
- For the CRM join, perhaps; for counting, hardly; with an email, never. Few brides sign in, so counts barely move, but a first-partyData a business collects directly from its own customers, visitors and users. join to the CRM shows which channels bring brides who buy. A hash still identifies the person: send the CRM's internal client number, stable everywhere, on every signed-in page, cleared at sign-out. See when a User-ID is worth sending.
- The reporting identity now blends signed-in identifiers. A bride on a phone and a laptop becomes one user, so
users fall and per-user rates rise; the view changed, not the data, so label user figures with the identity. In
the export, distinct
user_pseudo_idcounts browsers; distinctuser_idcounts signed-in people. See what changes in reports and the export. - Honour the choice everywhere. Set the User-ID only when analytics consent is granted. Google's tags have Consent ModeA Google tag feature that adjusts what tags collect according to the visitor's consent choices. checks built in; the others need consent settings requiring advertising consent. Pass the consent state into the widget where the vendor documents a way, or load it only after consent, as whoever owns privacy decides. The server never sees the banner, so store consent with the appointment reference and send Meta only what it allows. See consent inside third-party tools.
Where to go next
Answers that went astray on the contract, the event ID, the widget or the deposit hop point to the cookery school data layer exercise, where the same two guides meet a booking widget and a voucher checkout. Those on the User-ID point to the export work of the advanced analytics level. The second module opens with the wine club consent and retention exercise.
