Hi Andrew, thanks for raising the issue here! We'll be exploring how
possible this is over the next month or so, but only because you asked
so nicely. Of course, I can't comment on whether or when we'll make this
change yet, but I'll keep my fingers crossed.
Thanks for the comments, Danielle, and for weighing in on the value of
getting reports about bots. We agree that cloud computing is changing
the landscape, making it easier for bots to spoof humans. As a result,
our hope is to partner with companies who specialize in bot
identification. If there are a group of people whose livelihood depends
on identifying clandestine bots, they're more likely to stay on top of
the problem than companies focused on larger or related problems. If you
want to take...
Hi Michael, We're actively investigating bot identification and
filtering, so someone from my team may reach out to you for a deeper
conversation. Our goal is to automatically identify non-human traffic
and filter it out. We'd also like to report on it so you're aware of
what content malicious bots are consuming. Would you prefer that the
data be excluded entirely, or do you want the full reporting abilities
of Analytics to be applied to bot behavior? What kinds of reports would
you want on bots...
Great points, everyone. Thank you for the discussion. While I can guess
at what they are, can you talk about your key use cases and the impact
of not having them solved? For example, would you just use this report
to find products to promote together? And how do you make that decision
without this report?
Well, if fast classifications are the answer, we are already working on
that. It may be a few quarters before it's both complete and rolled out
across the customer base, but it's been designed and work has begun.
However, I am interested in whether a product or list-var container
would be helpful in the segment builder, so if anyone else has comments,
feel free to chime in.
Michael, I'll restate to make sure I understand. (By the way, thanks for
providing the use case!) You're trying to filter out specific products.
For non-list variables, you can use a hit segment for this, but for
lists that doesn't work because there are multiple values in a hit. I'm
not saying we should do this, but for the sake of understanding, if we
implemented a product container in the segment builder, and you filtered
out specific products, would that meet the need? You want the rest of
Excellent recommendations, Michael. How often do you make changes to
processing rules? Perhaps more related to what you wrote, how often do
you view processing rules without making changes, and what are you
trying to find when you view them?
Thanks for submitting this, Lee. We're discussing ways to remove the
prop/eVar mapping requirement, but there are a few technical steps we
need to take to get there. Lightening the implementation effort is the
key driver for those discussions.
Really good point, @AndyW. I'd like to restate this to make sure I
understand it. Do you want to disallow users from sharing workbooks
unless they've got permission to do so? You would have one group of
users who can share, and another group that can't.
Hi Arif, Request #1 is in progress (we're working on adding funnel
visualizations now). If I understand your second request, it's about
clarifying whether Lock Selected Items or Lock Selected Positions is
active. My understanding is that only one can be active at a time, and
it's not very clear which is selected with the current design. Excellent
We've considered this many times, but have found that a full regex
engine could add processing delays. Is it fair to say that the key
points of regex are the following? Match a pattern, including wildcards,
number and alpha-character matchingReplace some portion of the string
with somethingExtract a portion of the stirng for use elsewhere
With the release of "Conditional Actions" you now have the ability to
set many different variables, or take many different actions in a single
processing rule, each with their own condition. This means that the
processing rule becomes a category all its own. If you disagree and
think there is still need for a separate categorization feature, please
Hi Andrew, when repurposing an eVar, Adobe recommends using the reset
function on the Conversion Variables page in the Admin Console (see this
documentation). Given this functionality, do you think the following
steps would work? Create a rule to delete the value of the eVar.Reset
the eVar in the Admin console to prevent any existing values from
persisting.Use context data for the new values you want in the eVar and
create a procesing rule that executes after the rule mentioned in #1