From 3d7d043ce32a0ed1b3d8a8b78bc4ce01319ebffb Mon Sep 17 00:00:00 2001
From: Rodrigo Tallar <89488066+rtallarr@users.noreply.github.com>
Date: Mon, 31 Mar 2025 01:30:20 -0300
Subject: [PATCH] fix custom event example

---
 custom-events.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/custom-events.mdx b/custom-events.mdx
index cdb287f..5888512 100644
--- a/custom-events.mdx
+++ b/custom-events.mdx
@@ -61,11 +61,13 @@ Lit.event("click-on-buy");
 Sometimes just an `event name` isn't enough. If you want to add more control to your data, you can use the `metadata` field. Like this:
 
 ```javascript 
-Lit.event("click-on-buy", metadata: {
+Lit.event("click-on-buy", {
+  metadata: {
     "product_id": "1",
     "customer_id": "customer_id_1",
     "price": 1999.99,
     "product_name": "Design Chair with a cute cat!"
+  }
 });
 ```
 
@@ -92,4 +94,4 @@ Analyze all yours `custom events` on the cloud dashboard.
 
 - Understand how users interact with your custom events by creating `Custom Funnels`. 
 - Analyze where your users come from and trigger an event with the `User Flow`.
-- Interact with events metadata with our `Events Metadata Analyzer`.
\ No newline at end of file
+- Interact with events metadata with our `Events Metadata Analyzer`.