Overview

Ad Lightning's propriety and patent-pending tools detect and stop unwanted behaviors and attributes. Ad Lightning uses a combination of real-time & predictive payload analysis, validated malicious signatures and other machine learning techniques to ensure that new threats are detected, reported and blocked. What's included:

100% coverage from redirects & malware
Stop bad ads while preserving monetization
Flexible integration options streamline launch
Protect user experience to increase pageviews & improve customer satisfaction
Eliminate complaints & free-up AdOps teams for revenue-generating activities

How it Works

The ADL Blocking Solution can be deployed on your site in one of 2 ways: (1) as an on-page script (preferred) or (2) as a DFP creative wrapper or template, depending on your version of DFP. The solutions allows ads to flow through the standard RTB delivery process (steps 1-5 below) without any disruption. Before delivery, the ADL Blocking Solution takes the ad markup from the winning creative, checks against our blocklist, and does not render the ad if our checks fail.

Blocklist attributes include:

Malware (infectious code, phishing, exploit kits, bitcoin mining)
Redirects
Suspicious content (recently registered domains, low reputation domains, obfuscated code)
Category blocks
Risky platforms
Client denylists or competitive domains for advertisers or formats that publishers don't want appearing on their site

You can find a more complete list of ADL's Blocking Taxonomy here.

Dynamic Analysis and Proactive Blocking:

As part of our continued commitment to ensuring our clients are receiving the latest in real-time protection from bad ads, we've updated our blocking technology to include improved and enhanced dynamic analysis to detect novel threats in real-time. For more information on Dynamic Analysis and how it works with our already existing detection methods, please read here.

Some solutions block malicious code, does ADL do that?

In some cases, yes, but typically our philosophy is that bad ads should never make it to the page. Just because one script has been removed, other parts of the creative (like the click-through url) can still be problematic which is why we prevent the entire ad and get a new one. Refreshing the DFP/GAM call allows the slot to be monetized.

Implementation

There are two ways to implement our wrapper - using our on page script (OP) or our creative wrapper. OP (preferred) is the best option if you:

Are a publisher or monetization platform
Use GAM, APN, Smart Ad Server or Yahoo (shortly) to manage inventory
Have control over publisher page level integrations

If none of the above fit, then our creative wrapper is the best solution

On page

For clients that choose the on-page integration (which is our preferred solution), the recommended implementation is to place our script in the <head> element. If that is not possible, then our script simply needs to be added after the googletag object is defined, but before any of the ad units get defined/placed onto the googletag command queue.

Here is a sample script:

To implement our on page script via GTM, please read here.

Creative Wrapper

Implementation of the wrapper depends on your version of DFP. Ad Lightning will work with your ops team to determine the best process based on your tech stack.

Please ensure that the ADL wrapper is the outer most wrapper when it's applied (outside of MOAT, IAS etc).

For DFP Small Business, ADL wrappers are implemented by running our proprietary script to wrap individual creatives.

For DFP Premium, users can implement ADL wrappers by using Creative Wrappers (to wrap an entire ad slot) or by using Creative Templates (to narrow the scope of the wrapper to specific creatives)

Please read here for our platform integration guide.

APS Connections Marketplace

Current Ad Lightning publisher partners and new customers alike can take advantage of our partnership with Amazon Publisher Services (APS) Marketplace. The integration not only provides more effective ad quality protection against malware but also offers a turnkey way for shared partners to enable the ADL script across all of their demand. Learn more here.

Blocking Configuration Options

ADL offers unique features for client-specific customization.

Standard Configuration:

With the Standard configuration, our blocking wrapper automatically detects and blocks bad ads from rendering on your site. From there, you can easily add objects that are known to be safe and should be excluded from our blocking wrapper to an Exclusion List.

Selective Configuration:

With the Selective Configuration option, ads will not be protected by default. Instead, you build an Inclusion List by adding DFP objects that are known to be problematic and should be wrapped with our blocking wrapper. If you have a greater percentage of direct traffic on your site, this configuration option may be best for you, as you can opt to have only programmatic objects on your Inclusion List.

GAM Integration:

To programmatically sync orders, line items, and creative IDs to your GAM instance, please read here.

Category Blocking

Brand and Category blocking options available in the UI. Learn more here.

Report an Ad

If you're an on-page script (OPS) client, Report an Ad works in tandem and gives users on your site the option to interact with and give feedback on your ads from your site in real-time. Check it out here for more information and reach out to your Account Manager to get it set up on your account.

Frequently Asked Questions

Q: How much latency is added with your wrapper?

The ADL wrapper adds minimal latency. The average initial payload is about 50ms. A subsequent ad loads take 5-10ms. The script is cached once-per-day so that subsequent loads are typically faster and are based on how long it takes the browser to read it's cache.

Q: What is dynamic analysis?

In addition to looking for known signatures (static denylist analysis), AdL's script now conducts dynamic analysis to identify misbehaving script in the wild to ensure that new threats are detected on the spot. Our proprietary combination of a denylist coupled with in-browser scanning blocks bad ads quickly so that pages remain performant and 3rd party reporting isn't disrupted.

Q: What happens when malicious code is detected?

If the malicious code appears after the initial markup, ADL will prevent the malicious code from executing and the ad will render as expected. Impression trackers will fire and be counted as expected.

If the malware exists within the creative markup, ADL will block the ad from rendering. Our belief is that creatives that contain anything malicious should not be allowed to render, as there are often multiple malicious objects in a creative. Once the ad is blocked, ADL attempts to call the refreshSlot() function. The GPT's refreshSlot mechanism triggers a net-new impression and allows you to monetize a given slot. The ad selected is based on the publishers' adserver configuration. In many cases, because the creative is blocked prior to rendering, impression trackers aren’t fired and the impression is not counted by the DSP, SSP, or adserver. There may one-off instances where a tracker is fired, however, it’s important to remember that block rates are typically less than .5% and these instances do not lead to any material discrepancies.

This feature is enabled by default for our on-page script and publisher creative wrapper clients. If you'd like to disable this feature, please inform your Account Manager.

Q: What reporting can you provide?

Reporting is available in the ADL dashboard. For ads that are blocked we provide complete reporting, which includes:

What ads were blocked and which block type they fall under
How many times the given ads were blocked
Signature that triggered the block
When the signature was last seen and blocked
Relevant DFP Company & Order information
SSP & Network CRID
HTML & Block source
Trend analysis

Q: What are the benefits of the on-page wrapper

Because the on-page solution is NOT applied through DFP, it has a few advantages over the creative wrapper deployments:

Protects and monitors ADX/EBDA inventory
Supports SafeFrames
Less likely to impact rich media or custom units
Less likely to impact viewability

Q: Do I need to also have Site Scanning if I am implementing the Blocking Wrapper?

Site Scanning is a critical component of a successful blocking strategy. By running Site Scans we are able to collect the HTML as well as all the Javascript responses for each ad call. This is the source of the bad ad behavior and in this data is the “signature” for the ad we put on our blocklists. Scanning data also helps us reduce false positives because we have more granular detail on specific IDs to block versus having to block entire domains, which is what happens with many of our competitors.

Q: Why do I frequently see signatures being blocked by the wrapper still appear in my site scans?

The reason is that bad actors are constantly evolving their techniques. New variants will get captured in our site scans first and then we then run our internal process to identify the next signature to add to our blocklist.

Q: Do I need to alert my Demand Partners about this wrapper?

Yes. It's always good to alert your partners of changes that could impact delivery.

Q: What are the limitations of implementing a Creative Wrapper?

ADL will work closely with your team to test our wrapper across your site(s) to ensure there aren't any issues specific to your site or tech configuration. It's important to follow the steps in the Implementation Checklist to ensure a seamless deployment.

For mobile web or apps, creative wrappers are supported for creatives built on the following types: Custom, Image, Native, Third party, User-defined template, or System-defined template. For other creative types, creative wrappers are ignored on mobile, even if they’re assigned to an ad unit.

Limitations of google ad manager creative wrapper implementations are documented here: https://support.google.com/admanager/answer/2797762?hl=en

ADL does not monitor creatives served through unfriendly iframes.

Updates made to the wrapper will affect all associated creatives. This makes updates across all monitored creatives easy if ADL provides updated template code.

It's important to alert ADL to any custom creatives running on the page that impact the page layout including wallpaper ads and sliding billboard units.

Q: Will AdLightning impact my core web vitals?

Using ADL should not cause a significant impact to your core web vitals. Ad tags use document.write() to render the ad. Since our script patches this method during our check of the ad markup, it can appear that AdLightning is using document.write(), however this is not the case as it’s coming from the ad tag itself. Since our script patches/proxies document manipulation methods, it is possible that any ad related script can be attributed to our op.js script (we would be at the top of the call chain). We break-up our script into 3 parts: op.js (main page script to inject blocker and blacklist into ad frames), blocker.js (core blocking logic) and blacklist.js (our denylist).