ILLUSTRATIVE WORKED WALKTHROUGH These steps explain a complete approach. They are not a claim that this live provider/account test was performed for you. Use your own project and record your actual observations. 1. Define an action that the system can actually observe. The reference practice feature opens a local explanation and emits one fixed explanation_open event only after that explanation becomes visible, not simply when a button is pressed. 2. Before opt-in, perform the task and confirm it works without loading Google's script. After opt-in in a fresh tab, inspect page_view and the action's payload/count in Network and your own DebugView. Click twice and verify the documented once-per-tab rule. 3. Keep free text, email, query/hash and identifying path content out of events. A local queued command is not remote ingestion; a blocker or wrong stream can leave reports empty even when the page works. Remove debug mode and implement a suitable persistent consent/withdrawal flow before public use.