Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

AI in Marketing › Expert

Checkpoint: Proving AI-Written Queries, Tags and Technical Work

Scenario questions set at an invented group of veterinary practices test the first expert module: what has to exist before a model is asked for code, what it may be shown, why a query that runs is not yet an answer, how a gap is reconciled, and how generated tags and markup are checked, tested and released. Answer every question in writing before opening the explanations, then reread the guide behind any miss.
CheckpointExpert levelModule 1: Checking what AI writes for data and tracking4 minUpdated

What this checkpoint covers

Every scenario is set at Pezourd Veterinary Group, an invented group of veterinary practices with online booking and a monthly pet health plan, whose marketing lead, analyst and developer now ask an AI tool for technical work.

Illustrative example — not a real result

Pezourd Veterinary Group: the work on the table

  • 6 practices, each with a page showing address, opening hours and services, and no reviews.
  • The health plan system reports 760 new plans last quarter. The analyst's generated query, which joins plans to pets on the owner's ID, returns 1,140. After her fixes it returns 772, and she proposes excluding the 12 plan IDs the system does not show so the totals match.
  • The tracking plan row for online booking: event appointment_request, parameters practice_id, species and appointment_type, consent category analytics.
  • The generated booking tag sends vet_appointment with pet_name, owner_phone and practice, on pages matching book: the booking confirmation and a blog post on books for new puppy owners.

Task

  • Answer all eight in writing, action and reason, before reading on.
  • Score yourself against the explanations; the right action for the wrong reason scores as a miss.
  • Seven or eight: move on. Fewer: reread the page linked from each miss.

Questions

  1. The marketing lead types "health plan conversion rate by practice last quarter, plus a tag for bookings" into the approved tool. What should exist before either request is sent?
  2. The analyst plans to paste rows of the plan export, with owners' names and phone numbers, into her personal AI account "so it can see the data". What does the model need instead?
  3. Her first query returned a neat table by practice in seconds. The marketing lead wants it in tomorrow's report. Your reply?
  4. Her corrected query sits a little above the plan system's total. What is wrong with her proposal?
  5. Read the generated booking tag against the plan row. What has to change before anything else is tested?
  6. The developer asked the tool for location markup and pasted the result into each practice page by hand, opening hours and a star rating included. What should he have asked for, and what comes out?
  7. The developer tested the booking tag once, on the confirmation page, after accepting the banner. What is missing?
  8. The developer wants to publish from his own workspace this evening, with no description; the analyst has saved her corrected query to her downloads folder. What should happen to each?

Answers explained

  1. The definitions and the plan row. The question needs every term defined, and the tag needs its tracking plan row. The AI-written code review checklist puts both before anything reaches the model, because without them there is nothing to check the output against.
  2. Field names, row meanings and invented rows, in an approved tool. Owners' details add nothing to a query and are Personal Data the task does not need, and a personal account is not an approved tool. The tutorial on minimising data before prompting starts from the task and keeps only the fields it needs.
  3. Running proves the syntax, not the answer. A Language Model writes a likely-looking query from what it was shown, and a join on the owner's ID repeats each plan once for every pet that owner has. The routine for checking AI-written SQL proves it against the definition and an independent total first.
  4. Excluding plan IDs makes the numbers agree without making them right. A gap gets an explanation, or the checks run again. The diagnosis for AI report numbers that do not match gives the same rule.
  5. Names and personal data. vet_appointment, pet_name and practice are not in the plan, and species and appointment_type are missing, so reports would split. owner_phone comes out. The tutorial on proving AI-written tracking code checks names and values before preview: a tag can fire while sending the wrong things.
  6. A mapping from the page template's fields, not finished markup per page, so the markup follows the opening hours when they change. The rating comes out, because the practice pages show no reviews, and structured data describes only what a visitor can see. See the tutorial on checking AI-generated structured data.
  7. The pages that should stay quiet, and the refusal. The pattern also matches the blog post, so the trigger is tested against both lists. Preview runs again with the banner refused: Google's tags adapt to the choice by themselves, and the preview shows whether a consent requirement held the tag back. See the consent mode guide.
  8. Through the container's rules, and saved where others can find it. The workspace description says an AI tool drafted the tag and how it was tested, and someone other than its author reviews and publishes it, as the container governance guide sets out. The query goes into the team's shared library with its definition, checks and the Prompt that produced it.

Where to go next

Missed the third or fourth? Redo the query half of the sewing machine retailer exercise. The advanced AI in marketing level covers re-testing a saved prompt after a model change. The next module turns from code to customers, and its exercise is the coffee machine retailer's chat assistant.

Pages this lesson applies

Terms used on this page

Also related

Related