Event library

​

Overview

The Event Library is like a recipe book for your tracking. Instead of creating the same tracking events over and over, you can save them as templates and reuse them across all your websites and projects.

​

Why use an event library?

​

The problem it solves

Without a library:

• Each team tracks differently
• Same events have different names
• Data doesn’t match across sites
• Updates are time-consuming
• Quality varies widely

With a library:

• Everyone uses the same templates
• Consistent naming everywhere
• Data matches perfectly
• Update once, apply everywhere
• Proven quality standards

​

How the library works

​

Two levels of libraries

​

Creating library templates

​

What’s in a template?

Each event template includes:

1. Basic information
   • Event name (like “product_viewed”)
   • Friendly name (like “Product Page View”)
   • Description of when it fires
   • Category (E-commerce, User, Content, etc.)
2. Required data
   • What information must be collected
   • Rules for each piece of data
   • Examples of correct values
3. Documentation
   • When to use this event
   • Implementation notes
   • Sample data
   • Common mistakes to avoid

​

Building your first template

​

Common library templates

​

E-commerce templates

​

Content templates

​

User templates

​

Using library templates

​

In your tracking plan

​

Benefits of using templates

Saves time

• No need to reinvent the wheel
• Proven templates ready to use
• Faster implementation

Improves quality

• Best practices built in
• Common errors avoided
• Consistent data structure

Easier maintenance

• Update template once
• Changes apply everywhere
• Version tracking included

​

Managing your library

​

Organization tips

Group by purpose

• E-commerce events together
• User events together
• Marketing events together
• Technical events together

Name clearly

• Use descriptive names
• Follow naming conventions
• Include version numbers
• Add helpful prefixes

Document everything

• Why this event exists
• When to use it
• What data it needs
• Example implementations

​

Template lifecycle

​

Best practices

​

Do’s

✅ Start simple

• Begin with core events
• Add complexity gradually
• Test thoroughly
• Get feedback

✅ Be consistent

• Use standard naming
• Follow the same structure
• Apply uniformly
• Document clearly

✅ Think ahead

• Plan for growth
• Consider variations
• Allow flexibility
• Version properly

​

Don’ts

❌ Avoid these mistakes

• Creating too many templates
• Making them too complex
• Skipping documentation
• Not getting buy-in
• Ignoring feedback

​

Working with your team

​

Marketing’s role

• Define business needs
• Review template names
• Approve event purposes
• Ensure completeness

​

Developer’s role

• Implement templates correctly
• Suggest technical improvements
• Report implementation issues
• Maintain consistency

​

Analytics team’s role

• Create initial templates
• Update based on needs
• Monitor usage
• Train others

​

Industry templates

​

Available starting points

Tag Insight provides pre-built templates for:

​

Customizing templates

Start with industry templates, then:

1. Review what’s included
2. Remove what you don’t need
3. Add your specific events
4. Adjust naming to match your style
5. Test with real scenarios

​

Common questions

​

Getting started checklist

Before building your library:

• List your most important events
• Review current tracking
• Identify common patterns
• Get team alignment
• Plan governance process
• Start with 5-10 templates
• Test thoroughly
• Document everything

​

Next steps