This guide uses the installation instructions generated by an Advarde conversion setup. The generated code contains the selected pixel and event names. Replace example action IDs with real stable IDs from your application before publishing it.
Prepare the setup
Open Conversion tracking, select the advertiser account, and choose Set up conversions. Select a preset, name the funnel, enter its website URL, and choose the existing tracking source when it is already installed on that website.
Review the included events and primary conversion. Create the reviewed setup, then open Installation and choose Google Tag Manager. Download the installation guide so the implementer has the same version you reviewed.
Install one base tag
Use the generated base snippet in a Custom HTML tag and fire it on the pages where this funnel is measured. Check for an existing direct installation or another tag that initializes the same helper. Avoid installing the generated helper twice.
The helper starts with measurement consent denied. Connect its setConsent behavior to both grant and withdrawal in your consent manager. A blocked event is not automatically replayed later. Test the actual consent lifecycle instead of adding an unconditional consent grant.
Connect successful business actions
Push the generated custom data-layer event only after the application confirms success. Use the conversion_name, conversion_id, and conversion_data variables described in the downloaded instructions. Configure the event tag from that same guide.
For an appointment, use the confirmed booking ID. A failed booking request must not emit a successful appointment event. On refresh or retries, keep the action identity stable and prevent unnecessary repeated sends.
// Illustrative application callback after a confirmed booking.
// Use the exact names and tag instructions in your generated guide.
dataLayer.push({
event: "buro_conversion",
conversion_name: "appointment_scheduled",
conversion_id: "booking_example_1042",
conversion_data: {}
});Preview, publish, and verify
Use GTM’s preview workflow to check the base tag, consent state, and event tag. Test a successful action, a rejected action, and a repeated confirmation. Publish the intended container version only after these checks pass.
Return to Advarde, choose Test events, and check recent browser receipts after a permitted action. The installation checkbox records your confirmation; it does not prove receipt or attribution. Keep the container version and test time with the setup record.
Sources and verification
Platform details checked on September 11, 2026. Your account may expose a different set of features. Examples are illustrative unless a dataset is explicitly supplied.