The use of blocking lists and such will become more and more of an issue
as privacy controls get baked into browsers natively. We could get to
the point where the browser pops up a message saying "this URL is
tracking these items about you"
Actually this a partially correct answer, the launch hosting is solid,
but the beacon itself is also getting blocked, smetrics.*/ss/b* is on
public blocking lists, it also appears that some of the strings in the
URL are also getting picked up by some lists.
So we use first-party cookies, but even though the beacon call is with
our local domain, the IP it resolves to is still an Adobe one. My guess
is that it's the IP that's in a deny-list vs the the subdomain we're
using. Ideally what we'd be able to do is proxy, but I'm not sure what
all is involved with that and the issues we may have.
We're seeing some of our users blocking our beacon at the network level.
I'm guessing they're seeing the IP for our beacon on some sort of deny
list since that IP is the same as Adobe. Anyone have a good way around
It's getting annoying having the debugger "reset" every time I go back
to it.... My workflow will sometimes just be looking at a single page,
but other times I'll be looking at a page, checking the variables, going
to Confluence or Jira to verify requirements, then I come back to the
debugger and it's all collapsed and set to the first column again, so I
fix it, put it where I want it, go back to confluence or jira and then
have to come back and reset things. The other issue with this is that
But the next page load never happens, many of our customers come in from
twitter and then close the browser. We're catching that "close" and
submitting a beacon call as it's closed. Our bounce rates are normally
in the 80's because people are reading and then leaving (also mostly on
mobile). It would be good if we could flag a call as a non-interaction
Our bounce rate just got much lower, which we know isn't due to our
brilliant content. Seems that we're firing a direct call rule when the
user leaves a page (this gives us the scroll depth, time on page, etc...
for the user, which is then used to determine the quality of the story
in question). Anyway, I'm pretty sure this is what's causing the issue
because I can see an uptick in this type of content around the same
time. Is there anyway to tell Adobe that this is a "non-interaction"