The 429 "Too Many Requests" error usually means your org is hitting Adobe's API rate limits and it might not just be from your script alone. Even if your script is only making calls every few seconds, it’s worth checking: If any retry logic or hidden loops are unintentionally sending more requests ...

You're right, _satellite.track() is just used to manually trigger a rule by name. It doesn’t care whether the rule sends data via AppMeasurement or the Web SDK. So if you're already using_satellite.track("video_25"), and that rule fires a Beacon with AppMeasurement, you just need to update the actio...

From what I understand, it’s partially tied to Chrome’s User-Agent Reduction initiative, which has been phasing out granular device details over time. That seems to impact what Adobe can pick up, especially for Android users coming through Chrome.   One thing worth checking is whether Client Hints a...

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 ...