3 Key Ways to Implement Adobe Analytics for Web Applications: EDDL, Data Attributes & Direct Call Rules

By Vivek Mandal | Adobe Analytics Developer

In the digital world, Adobe Analytics remains a cornerstone of enterprise web tracking. But when it comes to implementing Adobe Analytics, developers and analysts often ask:

“Which method should I use for tracking — EDDL, data attributes, or Direct Call Rules?”

In this post, we’ll explore three major Adobe Analytics implementation methods:

1. Event-Driven Data Layer (EDDL)
2. Non-EDDL (data attributes)
3. Direct Call Rule (DCR)

We’ll cover:

• What each method is
• How it works
• Code examples
• Pros and Cons
• Final thoughts: which one is best for your use case

1. Event-Driven Data Layer (EDDL)

What is EDDL?

An Event-Driven Data Layer (commonly adobeDataLayer or digitalData) is a structured JavaScript object that tracks user events and passes them to Adobe Launch.

It allows for clean separation of data and tracking logic and enables marketers to track events without touching the DOM or relying on developers after setup.

How it Works

Developers push structured data like this:

window.adobeDataLayer.push({
  event: 'productClicked',
  ecommerce: {
    product: {
      id: 'SKU1234',
      name: 'Blue T-Shirt',
      price: 29.99
    }
  }
});

In Adobe Launch:

1. Create a Rule
2. Use Core Extension > Event Type: “Data Layer — Push Event”
3. Set event name = productClicked
4. Use Data Elements to map ecommerce.product.name, ecommerce.product.id, etc.
5. Send beacon using Adobe Analytics > Set Variables > Send Beacon

Pros:

• Clean and scalable
• Easier to debug with Chrome dev tools
• Ideal for SPA & modern apps
• Compatible with Adobe Web SDK (AEP Edge Network)

Cons:

• Needs planning and alignment between dev and analytics teams
• Setup effort can be high initially

2. Non-EDDL (data attributes / data-track)

What is it?

This method leverages HTML data-* attributes added to elements for click tracking. It’s simple and quick—especially when you don’t want to touch JS or add complex logic.

How it Works

Add attributes like this in your HTML:

<button 
  data-track="click" 
  data-category="CTA" 
  data-label="Sign Up">
  Sign Up
</button>

In Adobe Launch:

1. Create Rule > Event: “Click”
2. Condition: element[data-track="click"]
3. Create Data Elements:
   data-category → %this.getAttribute("data-category")%
data-label → data-label
4. Set eVars or props and fire beacon.

Pros:

• Simple and lightweight
• No need for deep JS knowledge
• Great for MVP or temporary campaigns

Cons:

• Not scalable for large web apps
• Easy to break (if HTML changes)
• Hard to manage across teams

3. Direct Call Rules (DCR)

What is it?

Direct Call Rules use a JavaScript call to trigger a rule in Adobe Launch explicitly.

Get Vivek Mandal’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

This is great when:

• You can’t rely on DOM or HTML attributes
• You want tracking tied to complex JS logic or functions
• You work with SPAs or AJAX-based UI changes

How it Works

Your developer calls this in JS:

_satellite.track('videoPlayed');

In Adobe Launch:

1. Create Rule
2. Event Type: Direct Call
3. Rule Identifier: videoPlayed
4. Set variables & fire beacon

Pros:

• Gives full control to developers
• Works well in dynamic environments (e.g. Vue, React, Angular)
• Ideal for SPAs or web apps with AJAX-heavy navigation

Cons:

• Requires dev involvement
• Not friendly for marketers
• Overuse may cause maintenance issues

Comparison Table

Comparison Table

Final Thoughts: Which One Should You Choose?

Situation & Recommended Method
✅ Need structured and scalable tagging >>>> EDDL
✅ Simple CTA or link tracking >>>> Non-EDDL (data attributes)
✅ Complex or JS-based user flows >>>>. Direct Call Rule

Pro Tip: Most modern implementations are hybrid — using EDDL for core tracking, data attributes for quick tasks, and DCR for advanced triggers.

Bonus Tips for Professionals

• Maintain a Solution Design Reference (SDR) for your tracking plan.
• Use Adobe Experience Platform Debugger for testing rules and beacon hits.
• Follow consistent naming for Data Elements and Rule Names.
• Adopt Adobe Web SDK with EDDL if you’re planning for future-proof analytics architecture.

👨‍💻 About the Author

Vivek Mandal is an Adobe Analytics Specialist with over 14 years in digital data solutions. He works on enterprise-grade implementations using Adobe Launch, Web SDK, and Target. He’s also a trainer, helping teams and developers master Adobe Analytics across organizations.

Stay Connected

If you found this useful, follow me on Medium, LinkedIn, or leave a comment below. Let’s build better data together!