If you're trying to measure traffic influenced by AI platforms (like ChatGPT or Perplexity), the easiest starting point is to use Referrer Domain in your reports. Look for domains like chat.openai.com, chatgpt.com, or perplexity.ai. These will show up when a user clicks a link from an AI-generated r...

This is a really good use case for combining anomaly detection with IP-based tracking.   If you're already capturing IP addresses in eVar1, one option is to build a freeform table with Application Start as the metric and eVar1 (IP) as the dimension. Then enable Anomaly Detection on that metric, Adob...

Yeah, you're on the right track, this is one of those edge cases where the "Then" logic in sequential segments doesn’t quite line up with the flexibility you want. If the order truly doesn’t matter but all three events need to occur within a tight time window (like 1 minute), then unfortunately Adob...

Agree with @Jennifer_Dungan  Unfortunately, there doesn’t seem to be a reliable way to natively distinguish AI Overview traffic from standard organic in Adobe Analytics right now. These links typically come through with a 'google.com' referrer, and without any unique query parameters or campaign cod...

You can reduce tracking volume by sampling users, but there are trade-offs. We’ve done this before by assigning users a random number on their first visit (stored in localStorage or a cookie) and only firing the Adobe hit if the value matches a condition — say, 1 in 3.Example logic:var flag = localS...

As per my knowledge, there’s no native Adobe Analytics feature for detecting ad blockers. But it is possible to implement a custom detection and pass that info into an eVar or prop. We could use a small inline detection script that tries to load a known “ad-like” file (like ads.js or something with ...

Yes, it is possible to track a user’s journey across two domains in Adobe Analytics — but there are a few critical things that need to be in place for it to work consistently. First, both domains need to be part of the same Experience Cloud Org and use the Experience Cloud ID Service (ECID). If the ...

This happens quite a bit when using both Adobe Analytics and Adobe Campaign. The numbers often don’t match because the two tools track things a little differently. Adobe Campaign counts clicks and opens directly from the email — like when someone opens the email or clicks a link, even if they don’t ...

This is a common challenge when consent is handled at different levels across subdomains or regions. Since the AEP Web SDK sets the kndctr_<ORG_ID>_consent cookie at the root domain (e.g., .xyz.com), that consent value ends up being shared across all subdomains — which can cause issues when each sub...

You can try building a visit-level segment that looks for hits where both "Target Activity > Experience A" and "Activity Impression" happen in the same visit. Instead of just using the Target dimension (which sticks around for 90 days), this method focuses only on visits where the user actually saw ...