...
AdEngine implementation in WordPress should be done directly in page codes for the best effectiveness. In the header
and body
, plugins are allowed; however, please notice the possible issues listed below.
This integration guide applies if all ads are delivered by Snigel on a site with a simple page layout.
...
If there are specific pages where only a subset of the ads are shown, it is important to declare the ad tags used on the current page. If ad tags are not correctly declared, ad units will be auctioned, even if not used. This will lead to false ad impressions, negatively affecting page performance and user experience.
You can declare ad units using the snigelPubConf element.
Please remember:
ad-unit-name:
topleaderboard
div-name:
adngin-topleaderboard-0
...
Replace **site.domain** with the actual site domain
Place the script at the very top of the header to ensure the best possible performance
If Google Analytics is used, place the AdEngine tag after the Google Analytics tag
Keep the correct order of the tags: first configuration and then loading of AdEngine
...
Minify plugins do a search on the page for all the content, then join all files - JS and CSS - without order or dependencies, and mix before displaying it on the page. After that, they inject all the code and then compress the page. It impacts how several elements of the page work, especially the ad stack loader.
Cache plugins - are caching old versions of scripts. When there is a fix or an update, a new version doesn't load, and fixes don't work.
The typical issues:
Ads stop appearing,
CMP starts being called multiple times,
Scripts stop working completely,
Impact on A/B test run with different partners,
Use of
data-cfasync="true"
to minify scripts by Cloudflare RocketLoaderChanges don't show due to old versions of the scripts being cached.
Some of the typical plugins causing these sorts of issues: