Expand my Community achievements bar.

SOLVED

IAB Bot Filtering Include Paid Services

Avatar

Level 1

1. I am wondering if the IAB bot rules enabled within Adobe Analytics already include known paid monitoring services like Gomez or Catchpoint? I know you have to pay to see this list, but generally is it all bots/services or just the malicious ones?

2. The "Bots" report - Does this show a combination of bots that I have identified and blocked AND they are on the IAB's list?

For example, we use Gomez and are not currently blocking their IP addresses. I do not see "Gomez" listed in my Bots report. Can I assume that it's not included on the IAB list?

 

Thanks!

Cristine

1 Accepted Solution

Avatar

Correct answer by
Employee

1.The IAB list intends to include all advertising related spiders, bots, OR site-traffic associated with robotic activity.

2.The Bots report should show any bots that are filtered out via the auto-IAB list or if you also have done manual additions via the admin bot rules. If you feel the IAB list is not capturing a known bot you can enhance through you own custom additions.

Important to note any party can recommend new IAB bot inclusions via http://www.iab.net/2216776.

Best,

Brian
 

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

1.The IAB list intends to include all advertising related spiders, bots, OR site-traffic associated with robotic activity.

2.The Bots report should show any bots that are filtered out via the auto-IAB list or if you also have done manual additions via the admin bot rules. If you feel the IAB list is not capturing a known bot you can enhance through you own custom additions.

Important to note any party can recommend new IAB bot inclusions via http://www.iab.net/2216776.

Best,

Brian
 

The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----