← Academy·New at Trackingplan

Intermediate3:46

Validate events and create custom metrics with the Trackingplan agent

Ask the Trackingplan agent to edit an event spec, create an event, or create, star and delete a custom metric. Nothing is saved until you approve.

Ask the Trackingplan agent to rename a destination, create an event with its spec, make a property required, and create, star or delete a custom metric. Nothing is saved until you approve the card.

In the video, on a demo workspace, the agent creates the purchase_test event with four properties (an enum, a required ID, an optional number and a GUID regex), makes value required, and creates a custom metric for the orders paid with PayPal.

More in Threads and in the release notes: edit an event spec from the chat, create and delete events from the chat and create and delete custom metrics from the chat.

Transcript

Validating the spec of every event and creating custom metrics takes a lot of clicks. With the agent, it takes one sentence. I'll show you how to do both using the Trackingplan chat. When you have many destinations, it's hard to tell which one is which. You can give each one an alias in Settings and Members, but you can also do it straight from the chat. To do that, we open a new thread and ask it to rename the GA4 destination with this ID to "GA4 Demo Account". Before making any change, the agent always asks for confirmation. Here, we say yes. Once the change is done, the destination now shows up as GA4 Demo Account, with just one event. We can also create events and edit their specs. For example, let's create a purchase event in this destination with several properties. We ask it to create an event called purchase_test, with a payment_method property of type enum (credit card, PayPal), a required transaction_id, an optional numeric value, and a userID in GUID format. You can also add descriptions and notes to the event. Here, we ask it to add the #ecommerce label. As before, it asks us to confirm the change. We say yes. Once it's done, we can see we now have two events. The second one has its four properties defined: payment_method is an enum with the values we specified, and userID is a regex that validates the GUID format. We can also edit or delete a property. In this case, we'll edit the value property of the event and make it required instead of optional. We accept the change. And we can see that value is now required for the purchase_test event. You can also create custom metrics. Just ask for it. Let's create a custom metric that counts the purchase_test orders paid with PayPal, and mark it as a favorite. It asks us to validate the rules for the custom metric. We say yes. We also want to mark it as a favorite. Here's the result. The metric is starred, and we can see its definition: it takes every purchase_test event where the payment method is PayPal. You can also ask it to delete specific events or custom metrics. For example, we can ask it to delete "PayPal transactions". It will ask us to confirm. And we can see the metric has been deleted. That's all. I hope this short video helps you get more out of Trackingplan, especially when working with event specs. Bye!

Next in New at Trackingplan

Watch it all →

Trackingplan

See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.