Overview
Requirements are the foundation of your tracking documentation. Each requirement represents a specific tracking behavior on your website, such as a purchase event, a page view, or a form submission. Think of a requirement as a single, testable unit of tracking that your team needs to validate.
Each requirement can contain several types of detail. Variables define the data layer values you expect to see. Data objects describe the full data structures that should be present. Tracking pixels list the marketing tags that should fire. Scenarios lay out the exact test steps for QA. You can also attach scripts and related links for additional context.
When you build a QA plan, it pulls from your requirements automatically. The more thorough your requirements, the more useful your QA plans become.
Creating a Requirement
Navigate to Blueprint from the main menu and select your property. Click Requirements to view the requirement list for that property. Click Add to create a new requirement.
Enter a title that clearly identifies the tracking event, such as "Purchase Event" or "Newsletter Signup." Add a description that explains what this requirement covers and any important context a tester or analyst should know. Click Save to create the requirement.
After saving, the requirement detail view opens. From here you can add variables, tracking pixels, data objects, scenarios, scripts, and links using the tabs along the top.
Adding Variables
Open the requirement and go to the Variables tab. Click Add to attach a variable. Select a variable from the library, then configure the expected values that a tester should look for when validating this requirement.
The Additional Testing Notes field lets you provide extra context that the tester needs. For example, you might note that a variable should only populate after the user completes checkout, or that the value format changes between mobile and desktop. These notes appear highlighted in red within QA plans and test case views, making them hard to miss.
Each variable you add here becomes a testable line item in any QA plan that includes this requirement. Be specific about expected values so testers know exactly what to look for.
Adding Tracking Pixels
Go to the Tracking Pixels tab. Click Add to attach a tracking pixel. Select the pixel type (such as Google Analytics, Meta, or TikTok) and configure the expected parameters for that pixel.
The Testing Notes field works the same way as it does for variables. Use it to tell testers about timing considerations, expected parameter values, or conditions under which the pixel should or should not fire. These notes also appear in red in QA plans.
Tracking pixels in your requirements give testers a clear checklist of marketing tags to validate. Each pixel becomes a pass/fail item during QA rounds.
Adding Data Objects
Go to the Data Objects tab. Here you define the expected data structures for this requirement. For example, you might document the exact format of a dataLayer push that should fire on a purchase event, including all expected keys and sample values.
Data objects give your QA team a reference for what the raw data should look like. During testing, they can compare the actual data layer output against the documented structure to confirm everything matches.
Keep data objects up to date as your tracking implementation evolves. Outdated structures lead to false failures in QA plans.
Adding Scenarios
Go to the Scenarios tab. Click Add to create a new test scenario. Each scenario defines the exact steps a tester follows to validate this requirement. Enter a title, description, and the ordered steps.
You can add tags to categorize the scenario and include Additional Testing Notes for anything that is not obvious from the steps alone. Scenarios tell your QA team exactly how to trigger and observe the tracking behavior described by this requirement.
For detailed guidance on building effective scenarios, see the Test Scenarios guide.
Using Templates
If you have standard tracking patterns that apply across multiple properties or pages, requirement templates save you from recreating the same setup each time. Click Apply Template from the requirement list to populate a new requirement with a predefined set of variables and tracking pixels.
Templates are especially useful for common events like page views or e-commerce transactions where the expected variables and pixels are consistent. After applying a template, you can customize the requirement further to match your specific implementation.
Use descriptive titles so anyone on your team can identify the requirement at a glance. Stick to one requirement per tracking event to keep things organized. Testing Notes on variables and scenarios appear in red in QA plans, so use them to highlight anything critical that a tester must not overlook.
Troubleshooting
Requirement not showing in QA plan
When creating a QA plan, you select which requirements to include. If a requirement is missing, go back to the plan setup and verify that it was checked. Also confirm the requirement belongs to the correct property.
Variables not appearing
Variables must exist in the variable library before you can attach them to a requirement. If you do not see a variable when clicking Add, check the library to confirm it has been created for your property.
Template not applying
Templates are scoped to platform types. If a template does not appear in the list, make sure it matches the platform type configured for your property. Check the template settings to confirm compatibility.