Complete Guide to Ptengine Event Properties: Making Data Truly Serve User Experience

1️⃣ What Are Event Properties? #

Simply Put: Adding "Tags" to User Behaviors

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:

  • 🛍️ What product did you add to cart?
  • 📱 Which page did you add it from?
  • ⏰ How long did you browse before deciding to add it?
  • 💰 What's the price range of the product?

This additional information is Event Properties - they transform a simple "click" into a "user intent signal" rich with business insights.

Why Do We Need Event Properties?

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.

Industry Scenario Basic Behavior Record + Event Properties Record Insight Value Enhancement
E-commerce Platform User clicked a button Added ¥299 sneakers to cart after browsing reviews for 3 minutes Understand price sensitivity and decision factors
Financial Services User viewed a page Inquired about medium-risk, 1-year financial products Match user risk preference and needs
Job Platform User searched content Product manager positions in Beijing, 3-5 years experience required Precisely recommend suitable positions

💡 Think From Another Perspective

If you were the user, you'd want the website to:

  • Understand what you really want, not blindly recommend
  • Provide help at the right moment, not repeatedly disturb
  • Show information you care about, not one-size-fits-all content

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.


2️⃣ What's the Value of Event Properties? #

The value of event properties is mainly reflected in two directions: Deep User Analysis and Precise User Engagement.

🔍 Analytical Value: Insights into Real User Needs

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.

📱 Fashion E-commerce Case: Optimizing Page Layout Based on Purchase Intent

Background:
A fashion e-commerce site found low conversion rates and wanted to understand browsing habit differences among different user groups.

Implementation Plan:

  1. Track add-to-cart behavior through event add_to_cart with property product_category
  2. Compare page behaviors of "users who added dresses to cart" vs "browse-only users"
  3. Adjust page layout based on behavioral difference data

Insights Discovered:

User Group Focus Area Behavioral Characteristics
Users with Add-to-Cart History 👗 45% higher attention to product review section Trust real feedback from other buyers more
🔗 30% higher click rate on related recommendations Willing to explore more styling options
Browse-Only Users 📝 60% longer dwell time on product details Need more product information to make decisions
💰 Repeatedly check price information More price-sensitive, need promotional incentives

Optimization Strategy:

  • For users with purchase experience: Highlight user reviews on first screen, add "buyer photos" display
  • For new users: Strengthen product selling points introduction, add "new customer exclusive price" labels

Implementation Results:

Metric Improvement Specific Data
Overall Conversion Rate ⬆️ 45% New user conversion rate improved from 1.1% to 1.6%
User Engagement ⬆️ 40% Review section click rate increased, average dwell time increased by 1.2 minutes
Purchase Decision Time ⬇️ 15% New users' time from browsing to order shortened by average 8 minutes

🏥 Online Health Service Case: Optimizing Service Process Based on Consultation Intent

Background:
An online health consultation platform found inconsistent user satisfaction after consultations and wanted to improve service quality.

Implementation Plan:

  1. Record consultation details through event consultation_request with properties symptom_category, urgency_level
  2. Analyze service path differences for users with different symptom types and urgency levels
  3. Optimize consultation allocation and response mechanisms accordingly

Insights Discovered:

Consultation Type User Expectations Current Issues
Chronic Disease Consultation Users 🔍 Want detailed understanding of causes and long-term management plans Doctor responses too simple, lack systematic guidance
Acute Symptom Users ⚡ Need quick emergency treatment advice Wait time too long, anxiety escalates

Optimization Strategy:

  • Chronic Disease Consultations: Match specialized doctors, provide 15-minute in-depth consultations
  • Acute Symptoms: Open fast track, respond within 5 minutes, provide emergency advice first

Implementation Results:

Metric Improvement Specific Data
User Satisfaction ⬆️ 22% Chronic disease consultation satisfaction improved from 72% to 88%
Response Efficiency ⬆️ 60% Acute symptom average response time shortened from 15 to 6 minutes
Repeat Purchase Rate ⬆️ 28% User second consultation rate significantly improved

🎯 Engagement Value: Precisely Push Content Users Really Need

Based on event properties, we can push truly valuable information to users at the right time through the right channels.

🛒 Mother & Baby Products Case: Smart Recommendations Based on Browsing Preferences

Background:
A mother & baby e-commerce platform wanted to reduce user information interference and improve push content relevance.

Implementation Plan:

  1. Record browsing preferences through event product_view with properties baby_age_range, product_type
  2. Provide precise content push based on baby age groups and focus categories
  3. Send personalized recommendations during user active hours

Engagement Strategy:

User Profile Push Content Engagement Timing
0-6 month baby mothers, focus on formula 📱 "Newborn Formula Feeding Guide" + brand formula discounts 8-10 PM (after bedtime routine)
6-12 month baby mothers, focus on baby food 🥄 "6-month Baby Food Preparation Videos" + baby food tool recommendations 2-4 PM (nap time)
1-3 year baby mothers, focus on toys 🧸 "Educational Toy List for Toddlers" + early education toy discounts Weekend mornings (parent-child time)

Implementation Results:

Metric Improvement Specific Data
Push Open Rate ⬆️ 45% Personalized push open rate improved from 12% to 17.4%
Conversion Rate ⬆️ 53% Post-push purchase conversion rate improved from 3.2% to 4.9%
User Feedback ⬆️ 38% "Useful" ratings for push content improved from 68% to 94%

💪 Fitness Industry Case: Personalized Fitness Guidance Based on Exercise Habits

Background:
A fitness APP found high user churn rates and wanted to improve user exercise persistence and platform stickiness through precise intervention.

Implementation Plan:

  1. Record exercise habits through event workout_completed with properties exercise_type, duration, workout_time
  2. Identify different user types' exercise preferences and times when they're likely to quit
  3. Push personalized motivational content before and after users' habitual workout times

Engagement Strategy:

User Profile Engagement Content Engagement Timing
Morning exercisers, prefer cardio 🌅 "Great weather today, perfect for morning run!" + outdoor route recommendations Daily 7:00 AM (30 minutes before workout)
Evening exercisers, like strength training 🏋️ "Time to release work stress!" + 15-minute efficient training plan Daily 6:30 PM (after work)
Weekend exercisers, flexible workout times 🎯 "Haven't exercised this week? 2 hours this weekend to get back on track" + fun exercise challenges Saturday 10:00 AM
3 consecutive days without exercise 💚 "Don't let your body forget the joy of exercise" + 5-minute simple stretching video User's previous active hours

Implementation Results:

Metric Improvement Specific Data
User Retention Rate ⬆️ 38% 30-day retention rate improved from 42% to 58%
Exercise Frequency ⬆️ 43% Average weekly exercise sessions improved from 2.1 to 3.0
Content Interaction Rate ⬆️ 52% Push content click rate improved from 8% to 12.2%

💡 Pro Tip

Want to achieve similar results on your website? Try starting with these simple event properties:

  • E-commerce sites: Record product price range, category, source page
  • Content sites: Record article type, reading completion rate, sharing behavior
  • Service sites: Record consultation type, user source, focus areas

Remember, the core of event properties isn't collecting more data, but better understanding and serving your users 🎯


3️⃣ How to Start Using Event Properties? #

📋 Step One: Clarify What You Want to Understand

Before deploying any code, think: What user behavioral intents do you most want to understand?

💡 Common Business Scenarios and Corresponding Property Design

Industry Type User Behaviors of Interest Event Properties to Set Questions They Can Answer
E-commerce Sites Users adding products to cart product_category, price_range, user_type What are the differences between content needs of interested users vs new users?
Content Sites Users reading articles article_type, read_completion, reading_time What type of content are users most interested in? What's the completion rate?
Service Sites Users submitting inquiries service_type, urgency_level, user_source What are the demand differences between users from different channels?

🔧 Step Two: Technical Implementation

⚠️ The following content requires technical personnel assistance for implementation

If you're not technical, you can forward this section to your development team

Basic Call Format

ptengine.track('event_name', {
  property_name1: 'property_value1',
  property_name2: 'property_value2'
});

🌟 Recommended Simple Deployment Methods

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:

  • Which price range products are most popular?
  • What colors and sizes do users prefer?
  • What's the conversion rate for add-to-cart from product detail pages?

📊 Step Three: View and Apply Data in Ptengine

1. Deep User Behavior Analysis

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:

  • 📈 Discovered high-value users pay more attention to "product reviews" section (45% higher click rate)
  • 🎯 Targeted optimization: Highlight user review content for these users
  • 💰 Result: High-value users' repeat purchase rate increased by 28%

2. Smart User Engagement

Based on event properties, you can create more precise user operation strategies:

🎯 Precise Push Examples

User Behavior Trigger Automatic Push Content Expected Effect
Browsed "sensitive skin skincare" but didn't add to cart Push after 7 days: "Sensitive Skin Care Guide" + related product discounts Improve conversion rate
Added "baby products" category items to cart Push: "New Mom Essential List" + maternity section link Increase average order value
Selected high-end price range in "price filter" Push brand stories, craftsmanship introductions, and other premium content Strengthen brand awareness

💭 Frequently Asked Questions

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?

  • Yes, great!
  • Not really

Thanks for your feedback.

  Sorry about that. Do you mind sharing how we can improve?

    Write your feedback here...