Track custom events with Claude or your AI agent

Implement one website event in this project using its existing Crisper installation.

1. Inspect before editing
Find the requested action's handler, existing tracking and product/order data. Reuse a compatible helper and check whether this action is already tracked. Keep the change scoped to this event.

Ask only for missing answers:
- What action should count, and where does it happen?
- What name should appear, and in which ad/analytics platform?
- Which available customer or commerce fields are permitted to share?

Resolve ambiguity about the success condition or required data before implementing. Prefer generate_lead for a lead and the matching commerce action below. Keep an explicitly requested custom name after checking its platform mapping.

2. Emit this contract
Use the existing dataLayer and clear event-specific values before each push:

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ user_data: null, ecommerce: null, properties: null });
window.dataLayer.push({
  event: "gtm_custom_event",
  datalayer_event_name: "<confirmed_event_name>",
  user_data: {},
  properties: {}
});

Replace the placeholder and empty objects with available, permitted values. Flat user_data keys are email, phone, first_name, last_name, street, city, region, zip, country and customer_id. Omit unknown fields; keep free-text form answers and sensitive labels out of event data. Preserve consent behavior. A form identifier can use properties.form.id.

Fire a lead only after accepted submission, capturing values before the form resets. For other actions, use the actual action/success signal. Prevent repeated handlers, renders, retries or page reloads from recounting the same completed action.

3. Add ecommerce only when relevant
Attach ecommerce beside user_data, not inside properties. Read actual product/cart/order values from the project:
- view_item: viewed product.
- add_to_cart: successfully added items and quantities, not the whole cart.
- begin_checkout: cart entering checkout.
- add_shipping_info / add_payment_info: completed checkout step.
- purchase: confirmed successful order and its final items.
A relevant custom commerce event can use this object too. Add only the requested action.

Purchase example with synthetic values; replace every value in the implementation:

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ user_data: null, ecommerce: null, properties: null });
window.dataLayer.push({
  event: "gtm_custom_event",
  datalayer_event_name: "purchase",
  user_data: {},
  ecommerce: {
    transaction_id: "EXAMPLE_ORDER_1001",
    currency: "USD",
    value: 49.98,
    tax: 3.50,
    shipping: 5.00,
    items: [
      {
        item_id: "EXAMPLE_SKU_1",
        item_name: "Example product",
        price: 24.99,
        quantity: 2
      }
    ]
  },
  properties: {}
});

For commerce, send items with a stable item_id and/or permitted item_name, numeric discounted unit price and quantity. Include the actual three-letter currency whenever sending value. Value is the sum of price times quantity, excluding tax and shipping; send known tax/shipping separately. Convert minor-unit amounts correctly and avoid subtracting a discount twice. Include known, permitted brand/category/variant/coupon/discount fields only when supported. Omit ecommerce for a non-commerce action.

Purchase transaction_id must be the real, stable order ID. Preserve existing event-ID/deduplication behavior: a repeated order must not fire again, while a new order must still count. Report missing required data instead of inventing values.

4. Verify and report
Use local fixtures or test-mode checkout, with no real enquiry or charge. Test success, failure, repeated success/reload, a genuinely new action, and a commerce-to-lead transition with no stale fields. Check payload types, item quantities, currency and value arithmetic; run relevant project checks.

Verify the outgoing request and platform receipt when access permits, including user_data and ecommerce.items forwarding. If they cannot be verified, name the remaining check. Keep GTM containers, integrations, campaigns and payment settings unchanged; report a missing installation or forwarding configuration to the site owner/Crisper support instead of adding another sender.

Finish with the files changed, actual trigger and event names, a synthetic example payload, test results, and any unresolved setup step. Separate website implementation, platform delivery and ad attribution in your report.