{
 "schema": "aiblocks-page/1",
 "id": "meta-event-matching-evidence-reviewer",
 "type": "skill",
 "name": "Meta event matching evidence reviewer",
 "summary": "Check how well your Meta events match real customers. Get a per-event review of missing fields, hashing and duplicates, with fixes in order.",
 "headline": "Meta event matching evidence reviewer",
 "subhead": "Give it your Events Manager match scores and a redacted list of the customer fields each event sends. It reviews Purchase and other events one by one. You get missing fields, hashing mistakes, duplicate-event findings and a ranked fix list.",
 "job": {
  "id": "check-ads",
  "name": "Check ads before they go live"
 },
 "level": "intermediate",
 "thinking": "medium",
 "tested": true,
 "updated": "2026-10-28",
 "first_published": "2026-10-25",
 "inputs": [
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  }
 ],
 "outputs": [
  {
   "type": "audit_report",
   "required": true,
   "label": "Audit report",
   "what": "findings with evidence, severity, missing inputs and next actions"
  }
 ],
 "you_give": [
  "The events you want to review, such as Purchase, Lead, Add to cart and Initiate checkout",
  "The match quality score Events Manager shows for each event, with its date range",
  "A redacted list of the customer fields each event sends, from the browser and from the server (for example \"email yes, phone no\")",
  "How you send events, such as the pixel only, your store's built-in connection, a partner tool or custom code",
  "What you know about duplicate events, such as whether browser and server send the same event ID (optional)"
 ],
 "you_get": [
  "A review of each event with its supplied score and which customer fields are sent, not sent or unknown",
  "Hashing mistakes, listing fields that should be hashed and are not, and the other way round",
  "Where each missing field could come from, and how big the job is in plain words",
  "Duplicate-event findings, based on only the evidence you gave",
  "Fixes in order, each with an owner, and a plan for what to check again in Events Manager"
 ],
 "use_when": [
  "Events Manager shows a low or middling match quality score for your Purchase event.",
  "You added a server connection (the Conversions API) and want to know if it is set up right.",
  "Meta Ads Manager shows more sales than your store does, or fewer, and you suspect double counting.",
  "A developer or agency says tracking is fine and you want a second check."
 ],
 "skip_when": [
  "You haven't chosen how to send server events yet: use the Meta server tracking checker.",
  "You want the whole account reviewed, not only tracking: use the Meta Ads 30-check account auditor.",
  "Your site has only the pixel and no server events. This review has little to check, so set up server events first.",
  "You want a forecast of how much money better matching would earn. This skill does not give one, because the score alone cannot show it."
 ],
 "output_sample": {
  "input": [
   "The match quality score Events Manager shows for each event, with dates",
   "A redacted list of customer fields each event sends, browser and server",
   "How you send events and whether browser and server share an event ID"
  ],
  "prerequisites": [
   "A Meta pixel, and ideally server events, already sending data",
   "Access to Events Manager, to read the scores"
  ],
  "output": [
   {
    "name": "Per-event review",
    "contains": "Each event with its supplied score, fields sent and not sent, hashing issues and priority."
   },
   {
    "name": "Hashing issues",
    "contains": "Fields sent in the wrong form, with the correct form for each."
   },
   {
    "name": "Missing fields",
    "contains": "Each missing field with where the data would come from, the likely cause and the size of the fix."
   },
   {
    "name": "Deduplication findings",
    "contains": "Whether browser and server events share a name and an ID, using only the evidence you gave."
   },
   {
    "name": "Fixes in order",
    "contains": "What to add or change first, the events it helps and who should do it."
   },
   {
    "name": "Check plan",
    "contains": "What to read in Events Manager after new data comes in, and the earlier value to compare with."
   }
  ]
 },
 "output_shape": "SETUP  events <list> | sent by <pixel, server or both> | score dates <from to>\nPER-EVENT REVIEW\n<event> | supplied score <n or MISSING> + rating label | sent <fields> | not sent <fields> | hashing issues <list> | duplicates <evidence> | priority <n>\nHASHING ISSUES  <field> | <what is wrong> | <correct form>\nMISSING FIELDS  <field> | would come from <source> | likely cause <x> | effort <small, medium, large>\nDEDUPLICATION  <event> | event name match <yes, no or unknown> | event ID match <yes, no or unknown> | counts given <x>\nFIXES IN ORDER  <fix> | events affected <list> | source <x> | owner <name or MISSING>\nCHECK PLAN  after new data, read <event> score again and compare with <date and value>\nMISSING AND NOT RUN  <list>",
 "how_to_use": [
  "Open the skill in Claude, ChatGPT or Gemini. If you have not added it, copy it and paste it into a new chat.",
  "In Events Manager, open your pixel or dataset and write down the match quality score for each event you want reviewed. Add the date range you looked at.",
  "Write a list of what each event sends. Use \"yes\" or \"no\" for each field, and never paste real customer emails, phone numbers or names.",
  "Tell the AI how events are sent and whether browser and server events share an event ID.",
  "Read the hashing issues first, because they are the quickest wins. Check Meta's current documentation before you change any field.",
  "After you fix something, wait for new data, then read the same score again and compare it with your first note."
 ],
 "checks": [],
 "next": [],
 "source": null,
 "credits": [],
 "files": [
  "references/emq-parameter-checklist.md",
  "references/emq-prompt-pack.md",
  "references/emq-sample-output.md",
  "references/emq-when-to-use.md"
 ],
 "links": {
  "page": "https://useaiblocks.com/skills/meta-event-matching-evidence-reviewer",
  "markdown": "https://useaiblocks.com/skills/meta-event-matching-evidence-reviewer.md",
  "json": "https://useaiblocks.com/skills/meta-event-matching-evidence-reviewer.json",
  "instructions": "https://useaiblocks.com/skills/meta-event-matching-evidence-reviewer/SKILL.md",
  "download": "https://useaiblocks.com/skills/meta-event-matching-evidence-reviewer.zip",
  "api_item": "https://useaiblocks.com/api/v1/items/meta-event-matching-evidence-reviewer",
  "api_document": "https://useaiblocks.com/api/v1/documents/skill/meta-event-matching-evidence-reviewer",
  "mcp": "https://useaiblocks.com/mcp"
 }
}
