[AA Community Q&A Coffee Break] 04/05/23, 10am PT: Come ask questions on analytics, best practices, and tips & tricks with Ben Gaines, Director of Product Management for Adobe Analytics

Ooooh, engagement is a HUGE (but fun!) topic. There is not a default metric for engagement, per se, and the definition depends on you! Every company has different engagement goals and views different user actions in their own way when it comes to signaling engagement. At Adobe Summit a couple of weeks ago, one of our "rockstar" presenters shared a great tip on doing engagement scoring using calculated metrics. You can watch that session here: https://business.adobe.com/summit/2023/sessions/2023-adobe-analytics-rockstars-top-tips-and-tricks-s101.html. It might give you some ideas for defining engagement and creating a "metric" for it! 

It has been a looooooong time since I dealt with Internal URL Filters, but if memory serves the "." entry is the default and you will want to make sure to add whatever internal domains you want filtered out. That isn't something I can help you with right here and right now, but you can add those domains yourself using the AA Admin Console. Here is some documentation to help!

https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/internal-url-filter-admin.html?lang=en

It sounds to me like you're having an issue capturing the username (or maybe just a "logged-in user") value on your pages post-login. That could be due to a bunch of things, and would be specific to your own implementation and site/app. I can't go deep into your implementation as part of this Coffee Break, but Adobe Customer Care should be able to help you figure out why the value might be getting set incorrectly. The place to start is to find the eVar (or prop) that is meant to contain these values, and figure out how it is getting set (either in your tag manager, or directly on your site), and then test it to see where the breakdown is occurring in your code/implementation. Sorry—if it had a simple answer, I'd give it you, but this one is going to take some digging. 

Sure thing. The first thing I would check is whether you are using a clickthrough metric imported from Eloqua or the clickthrough metric native to Adobe Analytics. If the former (i.e., from Eloqua) then I don't have a good answer—those should be coming through directly and should line up. That would be an issue to raise with Eloqua specific to this integration. If the latter (i.e., the clickthrough metric in AA), then my first guesses would be (a) that you have a bunch of Eloqua links that are either missing a tracking code, so that AA doesn't attribute those clicks to Eloqua correctly; or (b) that the tracking codes in your Eloqua links aren't being correctly assigned to the eVar/campaign variable in question (meaning that, for example, maybe you have emailID=123456 in your links, but AA hasn't been configured to look for the "emailID" query parameter). That's where I would start on this. Customer Care may be able to help more, and dig into the specifics. 

Great to have you here, Ben. Hope you enjoyed your sugar-free Red Bull break today and please do come back 😉 Appreciate you taking time to join us today 

- Ying and ExL PM team