Ecommerce Wire Field Coverage

Targeted SDK calls that exercise specific wire fields the regular store flow doesn't cover. Fire each scenario, then query web_events_raw to verify the field landed on the wire. Each click generates a unique order_id with prefix COV-<sessionId>-<n> so you can isolate test events in BigQuery.

Session prefix:

1. Payment type pt

Fire addPaymentInfo() with explicit payment_type values. Wire field expected: pt. Each click sends a different value to verify pass-through.

2. Shipping tier sht

Fire addShippingInfo() with explicit shipping_tier values. Wire field expected: sht.

3. Promotion location_id locid

Fire viewPromotion() and selectPromotion() with location_id, creative_name, creative_slot. Wire field expected: locid (alongside crnm, crsl).

4. Multi-level categories cat1 cat2 cat3 cat4 cat5

Fire viewItem() with all five category levels populated (LL format and GA4 format).

5. Order & item affiliation aff iaff

Fire purchase() with order-level affiliation and per-item item_affiliation. Wire fields expected: aff on the order, iaff on each item.

6. Tax exempt txex

Fire purchase() with tax_exempt: true. Wire field expected: txex: true.

7. Person object on high-value events person → id event

Fire purchase() with a full person object (email, name, phone, address, customer_id, B2B company). The SDK should emit a separate id event before the purchase. The epu event itself should NOT carry person data.

8. Everything at once combo

Single purchase with every gap field populated: pt (via separate addPaymentInfo), sht (via separate addShippingInfo), aff, iaff, cat1cat5, txex, full person. Use this as a single-shot verification.