A complete mock of the s object. Every property you can set in real AppMeasurement
— eVar1 through eVar250, prop1 through prop75, hier, list, events, products, link tracking,
linkTrackVars, clearVars. The simulator decodes whatever you fire,
exactly the way Adobe's collection servers would receive it. Press ⌘↵ or
Ctrl↵ to run.
Three workspaces below: a starter scenario, a blank slate, and a reference card. Pick the one that matches what you want to practice. All three use the same simulator engine — output from any of them mirrors a real AppMeasurement hit.
The starter code below fires four hits: a campaign landing, a product view, an add-to-cart link hit, and a purchase. Verify each parameter on the wire. Then mutate it — add eVars, change the products string, serialize the purchase. The simulator will not bite.
Empty editor. Fire whatever you like.
| Variable | Wire param | Notes |
|---|---|---|
s.pageName | pageName= | Identifies the page in reports |
s.channel | ch= | Site section / hierarchy root |
s.eVar1 – s.eVar250 | v1= – v250= | Conversion variables — persist |
s.prop1 – s.prop75 | c1= – c75= | Traffic variables — hit-only |
s.hier1 – s.hier5 | h1= – h5= | Hierarchy strings |
s.list1 – s.list3 | l1= – l3= | List eVars |
s.events | events= | Comma-delimited; numeric/currency use = |
s.products | products= | Semicolon-delimited fields, comma-delimited products |
s.purchaseID | purchaseID= | Serializes the purchase event |
s.tl(...) | pe=lnk_o / lnk_d / lnk_e | Link tracking type |
linkTrackVars | — | Whitelist for tl() hits |
In the journey scenario, change Hit 4's products to two products with different
prices. Verify the comma-and-semicolon encoding on the wire.
In Hit 2's products string, add an eVar20 binding: ;ASTRO-3000;;;;eVar20=organic-search.
Verify it appears on the wire.
Remove the s.clearVars() from Hit 2. Re-run. Observe eVar15, eVar1, and the
campaign event are still on the second hit. This is the #1 SPA bug from module 07.
Remove the linkTrackVars and linkTrackEvents lines from Hit 3.
Observe that the link hit no longer carries the event or products. This is the #1 link-tracking
bug from module 06.
Add s.hier1 = "Shop|Telescopes|Refractors|Astro-3000" and
s.list1 = "weight:14lb,color:black,brand:meade" to Hit 2. Confirm both
appear with the correct wire prefixes.
In Hit 4, change events to include a numeric event:
"purchase:ORD-44210,event50=12.99". Confirm the encoding.