Props Practice Test 2026 | Exam Prep

In the context of Adobe Analytics, what is the primary distinction between a "Prop" (e.g., `prop1`) and an "eVar" (e.g., `eVar1`) when tracking user behavior?

probes the fundamental difference in data capture and attribution models between Props and eVars. Option B correctly identifies that Props are often used for sequential data where the order matters (e.g., page views in a journey), and their value is reset based on the hit. eVars, on the other hand, are designed for persistent attributes that persist across hits and are crucial for attribution modeling, where their value is allocated to subsequent marketing activities. Option A is incorrect because eVars are the primary mechanism for user identification (though not exclusively) and Props can be event-based. Option C is incorrect; both have limitations on string length, and eVars have a finite number of values in their allocation, but the core distinction isn't about storage capacity in this way. Option D is incorrect as both require configuration, and neither is automatically populated in a general sense for tracking user behavior. Question: A marketing team wants to track which specific product detail pages users visit *before* making a purchase. They are considering using a Prop for `prop1` to capture the product ID from each product detail page. What is the key limitation of this approach if they want to attribute the purchase to the *last* product detail page viewed?

tests the practical application and limitations of Props in attribution scenarios. Option C correctly identifies that without specific processing rules (like "sticky" or "sequential" for Props, though less common for direct attribution compared to eVars), the value of `prop1` on the purchase confirmation page would likely reflect the *current* hit's context, not necessarily the preceding product detail page. This makes direct attribution difficult. Option A is partially true but doesn't fully explain the attribution problem; Props *can* capture sequential views, but their value is hit-based. Option B is incorrect because the value on the purchase confirmation page is unlikely to be the *last* product detail page's `prop1` value without specific configuration. Option D is fundamentally wrong; Props do not have built-in attribution models in the same way eVars do. Question: When analyzing campaign performance, a common practice is to use eVars for campaign names and Props for specific campaign parameters (e.g., ad group ID, creative ID). If a user clicks on an ad with parameters `campaign=SummerSale` and `adgroup=BeachAds`, and then navigates through several pages before converting, what is the most effective way to ensure the conversion is attributed to the `SummerSale` campaign and the `BeachAds` ad group?