Help Center
Imagine you're shopping online and click the "Add to Cart" button. For the website, this is just an ordinary click behavior. But what if we could know:
This additional information is Event Properties - they transform a simple "click" into a "user intent signal" rich with business insights.
Ptengine can already capture users' basic behaviors (clicks, browsing, dwell time, etc.), but to truly understand users, we need to combine business scenarios to capture and define more user behaviors, and understand the business meaning behind these behaviors.
If you were the user, you'd want the website to:
Event properties are the foundational data for achieving these experiences. Only by truly understanding user intent can we confirm whether user needs are being met and how to provide more thoughtful service.
The value of event properties is mainly reflected in two directions: Deep User Analysis and Precise User Engagement.
By tagging users' specific behaviors with event properties, we can identify behavioral differences among users with different intents, thereby optimizing experiences to better meet their needs.
Background: A fashion e-commerce site found low conversion rates and wanted to understand browsing habit differences among different user groups.
Implementation Plan:
add_to_cart
product_category
Insights Discovered:
Optimization Strategy:
Implementation Results:
Background: An online health consultation platform found inconsistent user satisfaction after consultations and wanted to improve service quality.
consultation_request
symptom_category
urgency_level
Based on event properties, we can push truly valuable information to users at the right time through the right channels.
Background: A mother & baby e-commerce platform wanted to reduce user information interference and improve push content relevance.
product_view
baby_age_range
product_type
Engagement Strategy:
Background: A fitness APP found high user churn rates and wanted to improve user exercise persistence and platform stickiness through precise intervention.
workout_completed
exercise_type
duration
workout_time
Want to achieve similar results on your website? Try starting with these simple event properties:
Remember, the core of event properties isn't collecting more data, but better understanding and serving your users 🎯
Before deploying any code, think: What user behavioral intents do you most want to understand?
price_range
user_type
article_type
read_completion
reading_time
service_type
user_source
⚠️ The following content requires technical personnel assistance for implementation If you're not technical, you can forward this section to your development team
⚠️ The following content requires technical personnel assistance for implementation
If you're not technical, you can forward this section to your development team
ptengine.track('event_name', { property_name1: 'property_value1', property_name2: 'property_value2' });
Method 1: Button Click Events (Simplest)
<!-- Add directly to button --> <button onclick="ptengine.track('product_add_cart', { category: 'skincare', price_range: '100-500' })">Add to Cart</button>
Method 2: Form Submit Events (Most Practical)
// Automatically record when user submits form document.getElementById('contact-form').addEventListener('submit', function() { ptengine.track('form_submit', { form_type: 'inquiry_form', user_source: 'homepage' }); });
After deployment, you'll be able to see in Ptengine:
After deploying event properties, you can conduct refined user behavior comparison analysis in Ptengine's heatmaps:
Dimension (Event Name) refers to a specific dimension of a specified event. Dimension refers to a specific dimension not limited to any event.
Taking Dimension (Event Name) as an example, The dimension name is before the parentheses, and the event name is inside the parentheses.
🔍 User Group Behavior Comparison
For example: Comparative analysis of - "Users who added high-priced products to cart" vs "Users who only browsed low-priced products" - Behavioral differences on product detail pages (which areas they click, how long they stay)
Practical Application Results:
Based on event properties, you can create more precise user operation strategies:
🎯 Precise Push Examples
Q: I don't understand technology, can I deploy this myself? A: It's recommended to get technical assistance. If your website uses CMS systems like WordPress, there are plugins that can simplify the deployment process.
Q: Do I need to track many event properties? A: It's recommended to start with 3-5 core ones and gradually improve. Tracking too many can actually scatter attention.
Q: How long before I see results? A: Usually after 1 week of deployment, you can accumulate enough data for preliminary analysis.
Q: Will it affect website loading speed? A: Ptengine's event tracking uses asynchronous loading, with minimal impact on website performance.
🎉 Ready to get started?
Remember, event properties aren't about collecting more data, but about better understanding and serving your users. Start with a simple event and gradually build up your user insight system, so every user can have a better experience on your website!
Was this article helpful?
Thanks for your feedback.
Sorry about that. Do you mind sharing how we can improve?
Write your feedback here...
We have received your feedback and will make sure to improve this article. We will get in touch with you once we do.