Discovery wizard

After the scan, TrackingCoder runs you through a short discovery wizard. It's the "consultant" layer — the bit that decides which selector to attach to, what form plugin to wire into, what event name to push to GA4, and which advanced parameters (like time-on-page or scroll depth at click) to include.

The flow, top to bottom

• Pick a scenario. The list is scoped to your stack — e.g. e-commerce sites see add_to_cart / purchase / view_cart, content sites see scroll_depth / video_engagement. See the glossary for what scenarios and channels are; a full catalogue doc is coming soon.
• Pick a destination channel. GA4 is the default. Other supported destinations: Meta Pixel, Google Ads, LinkedIn Insight, Microsoft Ads. You can generate the same event into multiple channels by re-running the wizard per channel — TrackingCoder will skip its own credit charge for the channel-specific tag if you've already paid for the scenario itself.
• Discovery questions. 2–4 questions, always plain English. Examples: "Which button text triggers this?", "Does the form redirect to a thank-you page or stay inline?", "What's the URL pattern of pages this should fire on?".
• Optional advanced parameters. Tick any of: hour_of_day, scroll_at_event, time_on_page, traffic_source, prev_page, device_category, page_section, day_of_week, etc. See Advanced parameters.
• Optional Consent Mode v2. If you need GA4 + Google Ads consent signalling, tick the box. Costs +1 credit. See Consent Mode v2.
• Channel ID. If we detected it on the scan (or you have one in the ID Vault for this domain) it's pre-filled. Otherwise you paste it.

Visual element picker

For click-based scenarios (button_click, phone_click, etc.) the wizard offers a visual element picker — a screenshot of your page with clickable hotspots over real elements. Pick the button you're tracking and TrackingCoder reads its selector, text, href, and parent context to build the cleanest possible GTM trigger. No CSS selector wrangling on your part.

Page scope

Most scenarios offer a page-scope question: fire on every page or fire only on a specific URL pattern. The codegen emits a GTM trigger condition that matches accordingly.

Common questions

Can I skip a step? No — each answer narrows the next question or affects the generated code. The wizard is short on purpose; there's no fluff to skip.

What if my form plugin isn't in the list? Pick "Other". TrackingCoder falls back to a universal native-submit listener that catches ~95% of form plugins, plus a dedup guard against the plugin firing multiple success signals for one submission.

I clicked the wrong element in the picker. Hit back, re-pick. The picker is interactive, not destructive.