A small event specification that connects an important action to a business question.
Begin with a question
Ask something you can act on: do visitors who complete our product quiz go on to buy the recommended product? Map the journey into a few events, such as quiz_started, quiz_completed and recommendation_viewed. Record purchases through the conversion interface.
For every event, write down its exact trigger, owner and useful properties. A completed quiz should fire when a result is successfully saved, rather than on every click of the final button.
Send an event from your application
After initializing the Adverfly JavaScript package, send a descriptive event name and the properties needed for your analysis. These are illustrative names; adapt them to your product and keep them consistent.
import { track } from "@adverfly/pixel";
track("quiz_completed", {
quiz_id: "find-your-scent",
result_id: "evening",
question_count: 5,
});Validate before using the result
Complete the action once and inspect the event. Then repeat navigation, refresh and error paths to check that the same action does not accidentally fire twice. Do not assume that sending an event twice will be deduplicated.
Group results by the properties you actually need. Compare equivalent periods and customer groups, and treat observed differences as a hypothesis: completing a quiz may indicate existing purchase intent rather than cause a purchase.
Your next steps
Use this checklist as you work through the guide.