Before committing campaign budget, the merchant wants proof that every Meta event fires in the right place with the right parameters. In this case, the immediate task is to check Meta pixel events during a test journey. The workflow should produce a tracking diagnosis and a repeatable test plan, listing which checks passed and which failed on the test order.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me check Meta pixel events during a test journey.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the predefined test journey with the Meta event expected at each step, the required parameters including value, currency and content identifiers, the browser and log capture method, the consent state for the run, and the test order identifier]. Run the journey while capturing events from the browser and from the merchant's logs, then check each event on name, firing order, parameter completeness and the identifier matching the test order, marking a check as failed where an event is absent, arrives twice or arrives with a required parameter empty.
Return a tracking diagnosis and a repeatable test plan with captured events verified and failing checks listed for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Define the test journey in advance, writing for each step the Meta event expected, the parameters it must carry such as value, currency and content identifiers, the browser and log capture used to observe it, the consent state the run is made under, and the test order identifier that ties the run together.
Run the journey while capturing events from the browser and from the merchant's logs, then check each event on name, firing order, parameter completeness and the identifier matching the test order, marking a check as failed where an event is absent, arrives twice or arrives with a required parameter empty.
Deliver a tracking diagnosis and a repeatable test plan listing every check with its pass or fail result, the failing parameter or step and the correction to make, then reconcile the captured purchase events with the test order in the merchant's records and repeat the run until the same result appears on consecutive passes.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Writing the steps, the expected event and the required parameters first gives the run something to be judged against. Without it, a pass only shows that something fired; the written plan also makes the test repeatable by another person, and any step without a defined expectation is marked as not checked rather than assumed correct.
A parameter check fails when a required value is absent, empty, or different from the test order, such as a value that does not match the order total. The event may still be counted elsewhere, so the payload is inspected and not only the event name; parameters the merchant has not defined are listed as unspecified.
The pixel is ready when every defined check passes on consecutive runs under the consent state the merchant expects, and the purchase events reconcile with the test order by identifier. Until then the run is repeated and the failing check corrected first, because budget committed on an unverified event buys reporting that cannot be trusted.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.