MetaTag Releases / Change Log

If you are part of the Ströer Organisation you can join our Release Channel in Microsoft Teams with our Team Code: g7orpko

Legend:

Log Entries

Meaning

Log Entries

Meaning

Added

A new feature or functionality was added. We provide a short description of the feature, explaining the use case and what you can do with this.

Changed

A functionality was changed internally, this might be a changed feature or a bugfix. This change does not need any action on publishers website. We provide a short description what was changed and why

Action

Something was changed, that requires an action on publishers websites. This will be used very rarely, our declared goal is that after you integrated the tagManager once, you dont have to change it.

issue

During our development cycle we became aware of an issue, but could not fix it right away and released anyway. This will often be something very small, for example: some rare use case within a new feature that nevertheless might be usefull to fix in the future.

Removed

Deprecated functionality that is not in use anymore

 

Each feature will be documented by a "pull request" in our collaboration software (GitHub). A release will also be documented by a "pull request".
For read access to our GitHub, please send us a ticket "Fragen zur Vertaggung" with your GitHub Username via our "Publisher Support Center" (login required).

Release 20.10.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/835
Status: Live

Entry

Description

Entry

Description

Changed

Metatag: fixed bugs when rendering a native backfill and a blocker campaign gets deliverd

Changed

MetaTag: Internal api changes in our testing framework

Release 11.10.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/828
Status: Live

Entry

Description

Entry

Description

Changed

Metatag: fixed the visibility logic from our adhesionUnit. Now if the adhesionunit-node is not in the visible area, the height of the adhesion unit gets set to 0.

Changed

Metatag: fix SDG.Publisher.getIABVendorConsent() returns value for legitimate interest instead of consent

Added

Metatag: allow publishers to pass us a native backfill, which we will directly then render if the slot does not receive an advert from the ad server

Added

Net ID: added another event for netId tracking when the user status gets checked

Release 23.09.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/821
Status: Live

Entry

Description

Entry

Description

Changed

Info-Tool: fixed Encoding issue where special characters are not displayed correctly

Added

Net ID: added Tracking Events for layer shown and user status checked

Changed

Net ID: changed read endpoint

Added

Net ID: added new status PERMISSION_NOT_FOUND

Changed

MetaTag: added accept header when sending a cors call

Changed

Meetrics: refactored Meetrics code and added extensive documentation. Changes are eyed torwards porting this module into typescript in the future. Process flow should be more apparent and transparent, making debugging easier.

Release 01.09.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/811
Status: Live

Entry

Description

Entry

Description

Changed

Keywords: meta keywords are collected when the publisher sets a zone. This should cover most cases, where the tags of the website will be present. ContentElementLoaded event as former trigger did not work too well.

Changed

Net ID: relocated re-show time and script version for netId layer to Config, so we can quickly change the value per website.

Changed

Store ID: fixed issue within Id Store where multiple identical id's could occur in our queue in certain circumstances

Added

Net ID: added another Event to fire when user is unknown to netId

Release 25.08.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/804
Status: Live

Entry

Description

Entry

Description

Changed

Integrated events into netId module, to react to specific states (netId consent successfull, failed, rejected, etc.). This can be used either for tracking purposes (how many users consented to usage of netId) or for reacting to state transitions through the website / publisher.

Changed

Editing the local or session storage will now always wait for consent for IAB TCF purpose 1, before saving any data on the user device. This was already implemented by most modules, but some edge cases could bypass those checks. To counter this, all calls to Web "Storage API" will now force a check for the consent state.

Changed

Refactored the StorageId Module to benefit from the upper two changes and to simplify the code

Release 11.08.2021 - ​https://github.com/mbrtargeting/stroeerMetaTag-development/pull/793

Entry

Description

Entry

Description

Added

add new event in Targetings for delaying scripts until the first auction from yieldlove is complete

Added

add new storeId interface to centralize storage of ids for persistent id vendors

Added

add new netId module

Release 27.07.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/789

Entry

Description

Entry

Description

CHANGED

fixed race condition error when delaying gpt script until full consent is available might lead to the script never being loaded bugfix/loadGptScriptAfterConsent #782

Changed

release new Info-Tool v2 with new CMP-Testtool prepare for info-tool v2 release [METATAG-76] #785

Changed

metakeys are collected earlier in the page load process. The event beforeLoadAll was too late for the headerbidder (and therefor stroeer.Core) to receive the meta keyValues bugfix/TICKET-24338/MetaKeyValue Fix #787

Release 07.07.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/778

Entry

Description

Entry

Description

Action

We will change our release process in the coming 2-3 weeks. In the future we will announce a release 24 hours in advance, and provide a testable preview version of the changes. If you, as a Publisher, are interested in utilizing this preview, please create a new test site in your staging or development environments. We propose a permanent and reuseable test site, since our releases will happen on a regular basis.
We will provide a preview URL to your websites metaTag.min.js file, which in turn can be integrated in your newly created test site.

If your are interested, please let us know via our “Publisher Support Center

CHANGED

removed useHull switch, hull feature is now always used refactor/unifyHullFeature #774

Changed

Publisher.getConfig().getFilteredKeyValues() will now also include keywords and return those as an additional keyValue dimension bugfix / getFilteredKeyValues will include keywords #775

Changed

fixed race condition error when delaying the header bidder until full consent is available might lead to the script never being loaded bugfix/loadYieldloveScriptAfterConsent #780

Added

new interface for changing the adhesionUnit on the fly. Will help mitigating problems where websites are heavily changed and the tagManager needs to keep pace. (adhesion units are elements from the website, scrolling along with the user, like sticky navigations, potentially colliding with ads) METATAG-46/add new interface for adhesionUnit change #776

Release 15.06.2021 -https://github.com/mbrtargeting/stroeerMetaTag-development/pull/773

Entry

Description

Entry

Description

CHANGED

ad slot is now again able to control, if a sticky ad will use or ignore the adhesion unit height. (Adhesion units are sticky elements from a website, for example a sticky navigation) #770

Changed

refactored checkOS() method under utility.js to return a type-safe object in all cases #771

Changed

removed unused function in info-Tool.js; refactored message for Report Error Panel to fit with the new data structure of infotool 2.0 #772

HotFix Release 10.06.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/769

Entry

Description

Entry

Description

CHANGED

Fix for adhesion unit update (adhesion units are “sticky” elements from a website, like a “sticky navigation)

We tried to conserve resources when updating the adhesion unit, doing an update only every 250 milliseconds. However on some websites this was not enough to position ads correctly. We now update on every scroll and after 250ms (since some websites will remove sticky navigations after the user stopped scrolling for a while).
This will fix positioning errors for some websites.

Release 10.06.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/765

Entry

Description

Entry

Description

CHANGED

Positioning of adx billboards reworked, to be compatible with "StrictSticky" (ads are sticky inside their slot containers, when slots reserve more space than the creative actually needs). StictAdSlots are only activated on a website, with approval from the Publisher.
Billboards will no longer use a positioning via fixed values for CSS properties "top" and "left", instead display:flex is used. #764

Changed

Reworked "adhesionUnit" interfaces and connected scripts. AdhesionUnits are now managed more centralized, and therefor don't require performance hungry computations in different parts of the tag manager any more. #763

Changed

Slots will now be "width" stabilized by setting a min-width, instead of using a "hard" width limit. This will fix some problems with the "Billboard" format, since its positioning on a website is largely dependent on the relation of width between the content and ad slot.

Changed

changes to stabilized slot height will now be animated, this allows users to better comprehend why and how the website is changing, #755

Added

Viewport breakpoints for blocking formats #762

Information 04.06.2021

Entry

Description

Entry

Description

CHANGED

After 1 and 1/2 months of testing and optimising, we will release our new “HTML Element structure” (outlined in this post: https://stroeerdigitalgroup.atlassian.net/wiki/spaces/SDGPUBLIC/pages/1205339000/MetaTag%2BReleases%2BChange%2BLog#Release-21.04.2021 ) to all websites.
Most websites already have the new structure activated, we now will finish the process by rolling out to all remaining sites.
The change will happen on Wednesday, June 9th at around 9:00 (AM).

For Publishers there is no action required to receive the changes.
Should you experience any problems (ads wrongly positioned or layout degradation) please let us know via our “Publisher Support Center”.

Release 02.06.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/761

Entry

Description

Entry

Description

CHANGED

new viewport buckets have been added to MetaTag #757

Changed

bugfix for AudienceProject Legitimate interest domain call #759

Changed

internal Testsites cleaned up #758

Release 26.05.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/756

Entry

Description

Entry

Description

Added

support for IAB initial/subLoad API integrated see: https://github.com/Unitadtechnologystandards/Initial-Sub-Load/blob/master/library.md

Changed

optimize scroll position calculation: when calculating the scroll position of the current document, we check more thoroughly if the tag is actually present. Thanks Holidaycheck!

Changed

internal refactoring: clarified variable names and types inside the methods for building modules and targetings.

Release 20.05.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/749

Entry

Description

Entry

Description

Changed

refactor/optimize module consent: targetings and modules now use a simplified logic to decide if they have consent from the user or not. Vendors can be configured to be based on either consent (will only load when user consents) or legitimateInterest (vendor will load as long as user does not refuse)

Changed

sticky flexible adhesion unit: sticky ads for CLS-Feature now can dynamically change top position, if page has dynamically height of adHesionUnit (for example flexible sticky-header)

Information 18.05.2021 - Changes to HeaderBidding key value “hb_pb”

Entry

Description

Entry

Description

Action

Our HeaderBidding solution “Yieldlove” will gradually change a long standing “key value” in the coming weeks.

The key value “hb_pb” will be removed and all functionality involving this key will pass to the key “yieldlove_hb_pb” (contains ecpm price information about the current best bid for a given adslot).
Please check if you use any of those keys in your reporting and analytics tools (like “Google Analytics”) and prepare those for switching to “yieldlove_hb_pb”.

If you haven’t use either of those keys in any report tools, you will not need to act.

 

Release 06.05.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/744

Entry

Description

Entry

Description

Changed

refactor adserver module:

  • prepared AdServer modules for streamlining event handling in the future

  • Google Publisher Iframe will now be searched by the AdSlot, as this entity was also saved there.

  • new method on the AdSlot for setting the frame window, will be used for transmitting postMessage events in the future

Changed

introduce layout option allowEmptySlotCollapse

  • introduced an option to local.json -> layout -> allowEmptySlotCollapse to control if an adslot should always collapse when empty (even if cls is caused)

  • edited reportDefaultDelivery to make possible for ad format template to tell the tagManager that a slot will be empty but to keep the slot open (be that the slot is stabilzed or not). Our template engine will use this for formats that block multiple adslots but use the space of those slots to fill it with parts of the format. (see "DirectionAd")

  • all AdServer modules will now use the reportDefaultDelivery method when encountering an empty slot, so they cant bypass the new logic

Release 28.04.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/740

Entry

Description

Entry

Description

Changed

MetaTag: mbr data will now be passed as simple array, not as nested array. This has no impact how the AdServer actually handled the keyvalues, but was a potential error for any script that might expect another result when iterating over the keyvalue store

Changed

MetaTag: fix for detecting the height of a Sidebar also the “jumping” of the skyslot when stickyStop is active.

Release 22.04.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/736

Entry

Description

Entry

Description

Changed

MetaTag: when an AdSlots location are newly calculated, we also evaluate the visibility markers anew. This will help in mitigating problems where the AdSlots position changes but the StrictSlot and LazyLoad are not reacting to the change

Changed

MetaTag: adSlots will now only be stabilized and evaluated if not blocked in config or are used for the correct device type

Release 21.04.2021

Entry

Description

Entry

Description

Added

We will gradually release an update on all websites in the coming 3-4 weeks:


Added more HTML Elements inside the AdSlot, to allow for better customisation of ad positioning and Google’s Core Web Vitals, without impacting pre-existing CSS styles on your websites.

The new elements are named “div#sdgSlotHull-[name of adSlot]” and “div#sdgAdServerAnchor-[name of adSlot]” and are nested under the HTML Element, to which you registered an AdSlot.
To see this change in action, on a test page, please see: http://s3.eu-central-1.amazonaws.com/stroeer-metatag-development-eu/bjoern/spa/spa.html
Use a developer tool/browser of your choice, to inspect the new elements inside the DOM.

 

If you like to test this change on your website, you can use the developer console of your browser to set

1 localStorage.sdgHullDemo = "1"

Please note: This update will only introduce the two new “DIV” elements on your site and will NOT activate any mechanic to reduce “Layout Shifts” in itself.

The gradual release process means that we will test a website, before making the change and afterwards activate the new feature for all visitors on your site.
Should you experience any problems or regressions inside your layout, please contact us via the Publisher Support Center (separate account required for login).

 

Release 15.04.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/729

Entry

Description

Entry

Description

Changed

MetaTag: Fix of position for starting stickyStop

Changed

MetaTag: Refactor LazyLoad:

  • removed separate "lazyLoadQueue", which informed the PlacementController, which slots should be measured and loaded if some visibility metric is met

  • AdSlots will now self regulate their lazyLoad logic. AdSlot are now aware where they are located relative to the viewport, in turn allowing its rendering process to start as soon as the slot enters / comes near the viewport. This should help greatly in the future, if new changes and features are introduced to lazyLoading and fixes some issues in non-scrollable “foto / click shows”

  • some minor changes to googleDfp.js and googleQueueDfp.js to optimize the code

  • InViewport Events will now trigger slightly before the AdSlot is actually visible. This should help mitigating problems where user is faster scrolling than JavaScript has time to react.

Release 07.04.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/727

Entry

Description

Entry

Description

Changed

MetaTag: fixed adLabels for IE11, which can not process multiple classList attributes

Changed

MetaTag: "fluid" size now possible in publisher created adSlots, changed SRA Testsite to consider modularSlots and the new fluid size

Changed

MetaTag: delay transitionAd setup until another slot is configured to simplify publisher setup

Release 31.03.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/724

Entry

Description

Entry

Description

Changed

Meetrics: names for device types changed from "mobile" to "MEW" and from "desktop" to "Desktop"

Changed

MetaTag CLS: slots can now be made exempt from using StrictSticky, LoadingAnimations and stabilized width

Changed

MetaTag CLS: stabilizing slots works a bit better when the website does not set any width or height preferences for slots

Changed

MetaTag Teamcity: fixed an issue where our build process does not build newly created files

Changed

MetaTag: re-implemented interface method getContainerId in our placements.js

Release 23.03.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/706

Entry

Description

Entry

Description

Added

MetaTag: introduced dialect settings to better differentiate between javascript version used on files inside the project

Added

MetaTag: introduced a new HTMLElement inside the AdSlot Container named "hull". The hull will be responsible to define the adslot with dimensions (width & height) and to facilitate the correct positioning of the adSlot without interfering with the AdSlot Container. Since the Container is often under full control of the publisher, we should leave the Container alone as much as possible and concentrate any css and layout changes to the new "hull"

Added

MetaTag: new switch in "layout" to de/activate the use of "hull". The Placement getHull() interface can be used no matter how this switch is configured. See jsDoc for details

Added

MetaTag CLS: Loading animations (called load spinner or loading spinner) are configured inside the "layout" config. Can be de/activated and user can choose between "circle", "bounce" and "wave"

Added

CMP Test Tool: checking of vendors with names, not only id's. Amount of founden and not founded consents and legitimate interests of SDG-vendors: https://docs.google.com/spreadsheets/d/1r_CJJMLCGZR2dcH0sBxVl3SzlPcRPtVBYJA0KpuMY-g/edit#gid=106593060

Changed

MetaTag: simplified the configuration of css rules inside of metaTag. Now all rules can be sorted under the "build"->"css" property as the user sees fit. The build process for releasing the final metaTag.min.js will parse the property and condense all CSS rules into just one value under "common" -> "css". This should vastly enhance the readability of all CSS rules and also detach the bulky code from the websiteConfigs local "common" property

Changed

MetaTag: restructured the Placement Module and tried to abstract multiple subclasses, for easier management of AdSlot specific logic, like AdLabels, AdServerContainer and LoadSpinner

Release 09.03.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/698

Entry

Description

Entry

Description

Added

New targeting pixel from "Deutsche Post AG" prepared for network-wide release (not activated yet)

Added

New feature in ConsentManagement testsuite. When opening the tool you can click “Test Vendors”, to run a test which vendors are configured in your CMP and how they are integrated. We will compare your configured vendors against the “Ströer Vendor Allowed List”, and report back all missing vendors. The “Ströer Vendor Allowed List” contains all vendors necessary for optimal monetization of your website.

Changed

fixed multiple issues in Info-tool

  • info tool file and css will now only load once, and not multiply times when reopening the info-Tool

  • fixed error counter when closing and reopening the tool

  • fixed logMessages in LogPanel being not translated properly, when loading the info-tool on slower devices

  • fixed new log messages not being added to the logPanel, now all new messages will be inserted on run time (you dont have to reopen the tool anymore, to get all logMessages)

Removed

removed modules "Coralogix" (performance tracking) and "Cookielayer" (predecessor to current CMPs). Both modules are no longer needed and are moved from productive code base to archive. No action required from Publishers.

Release 03.03.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/693

Entry

Description

Entry

Description

Added

MetaTag: added two new methods to parse the current keyValues and filter any unwanted keyvalues on Placement and Publisher level. This is used by Stroeer.Core to filter at least some of the many (and often unnecessary for Core) keys used in our ad network.

Added

MetaTag: Direct Rendering now available for Meetrics.

Changed

CMP: removed unused "SDG_CMP_PRIVACY_MANAGER_AVAILABLE" event for now.

Release 25.02.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/691

Entry

Description

Entry

Description

Changed

Meetrics: visibility measurement is now detached from the Placement "GlobalAddons" feature, since it was necessary to delay and call the measurement in different scenarios, without impacting the execution of addons.

Measurement will now delay if an advertisement "template" is used, until the template is actually ready to display an ad

Changed

MetaTag: removed now depricated Flash code, changed datatype for browser version.

Changed

MetaTag: Iframes created by metaTag will now use a css width & height definition to better facilitate size responsive ads

Changed

MetaTag: fix for uploadYLScripts task



Release 09.02.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/677

Entry

Description

Entry

Description

Changed

Info-Tool: Settings panel is now "Options" panel. Flex styles added, CMP-Test button removed from support to options.

Changed

MetaTag: Module Cleanup

Changed

MetaTag: Fix for Automatic reload when slot is not in a visible area.

Added

TransisitonAds: new check, to deliver this format only on Mobile if the Publisher calls it on Desktop

Added

Ströer Labs: new test segment added "mbrsegtest"



Release 04.02.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/670

Entry

Description

Entry

Description

Changed

Fixed minor issues on consent testpages

Added

Feature to delay all script calls from Metatag until consent has been set by user

Release 02.02.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/668

Entry

Description

Entry

Description

Changed

Decision of NPA (non-personalized ads) mode or LimitedAds mode based on IAB TCF Consent now will be done by Google itself, not the tagManager. In the past we overwrote the decision of Google, resulting in unclear targetings and traffic reports.
Only should the publisher signal us that non-personalized ads are to be used (no matter how the user consents), we will force the NPA mode.

Changed

If tagManager has the info that a CMP is used, which does not support IAB TCF, we will not write the __tcfapi to the website anymore. In the past this could cause problems when Google checks for the __tcf API but never receives valid TCF Consent

Changed

New keyvalue "cs" reporting a simplified consent status to the adserver (to measure how much consented traffic we likely can server with personalized ads). This KeyValue is reportable.

Changed

KeyValue "lta" reporting a simple status to the adserver if "LimitedAds" are likely to be used. This keyvalue however is only a approximation, the decision if LimitedAd are used is done by Google and will not be 100% coinciding with the "lta" key. This keyValue is reportable.

Release 27.01.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/653

Entry

Description

Entry

Description

Added

MetaTag: Automatic Mapping of the blockedPositions within the Formats under the key af

Changed

Sourcepoint: fixed an issue regarding un-allowed symbols within the URL

Changed

Audience Project: fixed Issue regarding the AP Launcher

Release 19.01.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/646

Entry

Description

Entry

Description

Changed

Audience Project: Script changes from Audience Project

Added

MetaTag: CMP Test Tool Documentation/Commenting

Release 13.01.2021 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/643

Entry

Description

Entry

Description

Changed

MetaTag: fixed confusing statements in CMP test tool, now it will let you know if a vendor has legitimit Interest

Added

MetaTag: added animations for resizing Strict Ad Slots (CLS)

Added

MetaTag: Info-Tool now identifies campaigns from stroeer core and logs the relevant Info from the bidder

Release 10.12.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/636

Entry

Description

Entry

Description

Changed

MetaTag: Reworked our Info-Tool styles. Fixes for IE11

Added

MetaTag: added Strict Ad Slots (CLS)

Added

MetaTag: added TransitionAds

Release 26.11.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/630

Entry

Description

Entry

Description

Changed

MetaTag: Fixed a bug in our CMP Check for websites where MetaTag is not implemented.

Changed

MetaTag: Reworked our Info-Tool styles.

Added

MetaTag: CMP Test Button added to our Support Panel

Release 18.11.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/627

Entry

Description

Entry

Description

Changed

MetaTag: CMP-Test for internal use and publisher updated. New features added, bugs fixed.

Changed

MetaTag: fixed a bug when handeling consent information in our AudiencePixel Module

Changed

CMP: fix for checking of Google vendor consent for non eu lands

Release 05.11.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/615

Entry

Description

Entry

Description

Added

MetaTag: New Logs from Google Advertising Products Vendor to Info-tool

Changed

MetaTag: CMP Test Tool for Publishers

Changed

MetaTag: Placement Module cleanup

Release 29.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/612

Entry

Description

Entry

Description

Changed

CMP: When using SDG.Publisher.getIABVendorConsent(), to determine if a tech vendor should be loaded, vendors requiring consent of the user will now only be allowed if the vendor has complete consent of the user. Legitimate interest will no longer suffice and vendors only operating under legitimate interest will be blocked.

Changed

CMP: tcfapi will now correctly been set even in cross domain iframes

Changed

MetaTag: eventQueue for an AdSlot will be reset when the adslot is loaded anew. Will stop triggering multiple stickies and measurements on reloaded slots

Changed

MetaTag: removed sessionStorage of consent data, since this performance focused feature did not provide much better performance but introduced problems concerning the validity of the consent data (cached consent not in sync with current consent)

Release 28.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/607

Entry

Description

Entry

Description

Changed

MetaTag: fixed localAddons to fire properly. This fixes problems with adSlots not being set "sticky" (=will scroll along with the user) and visibility measurements.

Release 27.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/604

Entry

Description

Entry

Description

Changed

MetaTag: Added new Function in Placements to check if metaTagSlotDone and metaTagSlotRendered have been fired on a placement. If so we execute the global Addons

Changed

MetaTag: Fix for a rare case where Slots get stuck in the loadqueue if slots gets registerd and unregisterd before the slot finishes an auction.

Changed

CMP: inserted communication bridge for using __tcfapi() even when CMP is located in another secured iframe. This will help when website use "non-friendly" iframes, blocking us from gathering the user consent directly.

Changed

Audience Project: Changed Object.entries into a IE11 friendly method

Release 21.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/599

Entry

Description

Entry

Description

Changed

MetaTag: optimised Browser data. Data will be saved only once for all event setups.

Changed

CMP: removed redundant SP config variable and fixed loadScript call.

Added

MetaTag: Save the view states and min max state from the info-tool.

Added

CMP: added CMP Check Script

Release 14.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/595

Entry

Description

Entry

Description

Changed

Yieldlove auction was not properly delayed until the tcString is available, but instead the auction could start at any time. Correct behaviour should be that auction is delayed until the CMP can safely give a tcString (after the user has given consent)

Changed

Removed check for valid consent if we retrieve consent data from the sessionStorage. While great in theory, most CMPs will answer early calls to __tcfapi() with tcData that only allows legitimeInterest. This data than gets compared to the full consent data of the last page impression. Since this will very likly differ (full consent IS NOT legitime Interest only) the full consent was deleted and LI consent saved, until the CMP reports "tcloaded" or "useractioncomplete" (at which point full consent was saved again to cache).

Changed

Reorganized saving of CustomVendorConsents, so custom vendors are fully saved and available when TagManager reports FULL_CONSENT_AVAILABLE

Release 07.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/589

Entry

Description

Entry

Description

Changed

Fix for Custom Consent API. Custom Consent from API will only be set if CMP is from Sourcepoint.

Action

If a Publisher is listening for our Event: metaTagSystemSpVendorConsent , this is now depricated. Please use: metaTagSystemCmpConsentAvailable from now on.

Added

new method to get current Adunit from placement.

Release 05.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/584

Entry

Description

Entry

Description

Added

New Logic for Custom Vendors. Now we save the CMP response Object for Custom Vendors.

Changed

Infotool Style Fixes

Release 01.10.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/581

Entry

Description

Entry

Description

Changed

pixels will now wait correctly until the point the user has actually consented (if the pixel is configured to wait for user consent)

Changed

simplified pixel configuration by assuming the most used defaults, only if a pixel does not use these defaults, a corresponding entry for the given setting has to be placed inside the config.

Changed

modules requiring consent will now load only after users actually have decided. Before modules might have loaded if vendors have based some of their script functionality on "legitimate interest". However this was often abused or not handled correctly, so cookies and trackings were wrongly loaded.

Changed

optimized Sourcepoint CMP integration. If the website is using our Sourcepoint CMP through TagManager, calls and APIs should now be a bit more efficient and the CMP should load faster.

Removed

Functionality to support TCF 1.0 is deleted from the TagManager. TCF1 is no longer in active production and the corresponding IAB standard is deprecated

Removed

NuggAd Module removed was replaced with AudienceProject

Release 29.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/578

Entry

Description

Entry

Description

Changed

Default console.logs for CORS requests replaced to infotool

Changed

Old events deleted, Trigger function optimized by switch statement, generateLocalPlacementParameters function optimized

Added

fix for cases, when container is null

Added

added gdpr macros for simple targeting pixels, so we can pass consent data to small img and script pixel

Release 25.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/575

Entry

Description

Entry

Description

Changed

cache check for gdprApplies for certain Modules fixed

Release 23.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/570

Entry

Description

Entry

Description

Changed

Cmp test script, version 1.9: vendors list for nonIAB websites

Changed

added check of gdprApplies of ConsentCache for true

Added

Information about active modules and its configurations now available in info-tool and info-tool console

Release 17.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/569

Entry

Description

Entry

Description

Changed

Serving "Personalized" or "NonPersonalized" ads will now be decided by checking the consent state of IAB TCF2.0 Vendor "Google Advertising Products" (ID 755).

If there is a Consent Manager on the website, that does not support IAB TCF2.0, we will deliver nonPersonalized ads when website uses our interface "SDG.Publisher.setAdServerConsent(false)

Release 15.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/565

Entry

Description

Entry

Description

Changed

fixed a problem with websites using a non IAB TCF2.0 consent manager, but all services (ex: header bidder) expecting and waiting for TCF2.0 consent data


Release 10.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/563

Entry

Description

Entry

Description

Changed

MetaTag/CMP: added display call for AdServer in a certain Site Constellation (SRA + Container available Delayed.)

Release 10.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/561

Entry

Description

Entry

Description

Changed

CMP: Adcall to adserver will trigger once consent information is available

Changed

DMP: Request now contains gdpr Macros

Added

MetaTag: introduced new ways to handle an adslot, so Yieldlove Wrapper can directly render a creative after the adSlot auction is finished

Added

MetaTag: new key value for criticle inventory

Sub-Release 09.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/560

Entry

Description

Entry

Description

Changed

Smaller improvements to new Audience Project pixel to increase user match rates

Release 08.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/555

Entry

Description

Entry

Description

Added

MetaTag: Audience Project now added to MetaTag to replace Nuggad

Changed

MetaTag: fixed error message when using XHR calling meetrics visibility forecast

Release 01.09.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/550

Entry

Description

Entry

Description

Changed

CMP: consent data is cached if the user changes her consent, even if it just was set

Changed

CMP: reworked and streamlined CMP events for easier use by the publisher. Events will now signal when a cmp ui is shown, when its closed and when the full tcf consent is available. metaTag documentation already reflects those changes

Release 19.08.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/543

Entry

Description

Entry

Description

Added

MetaTag: Pre-loading script function now added to System

Added

MetaTag: CMP for VAST Calls integrated

Added

MetaTag: Added new Testing Scriplet for CMP

Changed

MetaTag Code-Cleanup: removed 'use-strict' from Code

Changed

MetaTag: Sticky Performance Optimization

Release 10.08.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/539

Entry

Description

Entry

Description

Changed

MetaTag: Internal fix on how to load Scripts, if not defined differently we will default to async

Changed

MetaTag: New Media Format Video

Changed

MetaTag: Sticky Stop Fixes

Release 03.08.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/535

Entry

Description

Entry

Description

Changed

CMP/Yieldlove: headerbidder can now be delayed until cached consent is available. This should be much faster than the usual call to the __tcfapi.

However this in turn will mean that on users first impression on a website will most likely delay the auction and ad delivery process at least until we have some indication

how the user will respond.

Release 27.07.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/533

Entry

Description

Entry

Description

Added

MetaTag: introducing new options to reduce layout shifts, see https://stroeerdigitalgroup.atlassian.net/wiki/x/cQH9a for in-depth details.

Added

MetaTag: added option to have "rigid" adSlots, making it impossible for the adSlot to trigger a resize or reflow of the web page

Added

MetaTag: added option to center smaller ads in larger width adSlot containers (for example 150x250 add in 300x250 adSlot)

Added

MetaTag: added option to sticky smaller ads in larger height adSlot containers (for example 300x250 in 300x600 adSlot)

Added

MetaTag: added new test site to measure layout shifts and subsequent improvements

Changed

MetaTag: rewritten formatController and FormatMaster classes. Formats will not be initiated and assigned to adSlots much sooner, so we can work with formats and their potential sizes before the adslot actually is rendered to the website

Release 15.07.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/527

Entry

Description

Entry

Description

Added

ADP: AudienceDiscoverPixel Module now integrated

Changed

MetaTag: removed depricated modules

Changed

MetaTag: House Cleaning, cleaned up Testsites and log Messages

Changed

Coralogix: turned off logging of Placements and Modules loadtimes to Coralogix

Changed

MetaTag: blockedFormats now works pro Slot

Release 09.07.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/521

Entry

Description

Entry

Description

Added

CMP: Reorganized consent events into 3 distinct states

Changed

CMP: rewritten google consent statements to open the possibility to change the consent decision later on (for example, first load without consent, smart reload with consent)

Changed

CMP: fixed bug in consent cache behaviour

Changed

CMP: targetings and modules use new consent events to determine when to load

Changed

CMP: removed old targetings function "collectPageImpression", no longer needed.

issue

After deployment the TagManager was unavailable for around 60 minutes, without any advertisments showing on all websites. The issue was related to a so called "race condition", where a needed resource was not available in time and services broke down.
The error started to impact websites at around 11:00am on the 9th of July.
Websites functioned normally, but advertisments where not showing and no requests to the Adserver were sent or processed. This resulted in a loss of all ad reporting data for the duration of the error.
The error was found and a fix publicated at 11:17.

Content Delivery Network was updated shortly after and all stored, faulty versions of the TagManager were removed by 11:46.
Full service was restored by 11:47


Release 06.07.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/520

Entry

Description

Entry

Description

Changed

Coralogix: added switch to turn on/off certain logging options

Changed

Coralogix: added a/b Switch optimisation for Kibana

Release 02.07.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/518

Entry

Description

Entry

Description

Changed

Ströer SSP: Fixed race condition when previewing Slots

Release 23.06.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/512

Entry

Description

Entry

Description

Changed

CMP: added new config entry in "userconsent" to be able to switch seamlessly between tcf1.0 and tcf2.0 via URL parameter, instead of changes in tagManager config

Changed

MetaTag: fixed cache-control header when uploading to aws origin server. Cache-controll header will now be correctly handled by Akamai CDN, when fetching files from AWS origin.

Changed

MetaTag: fixed A bug where our Adlabel Node is disconnected from DOM.

Release 16.06.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/506

Entry

Description

Entry

Description

Changed

Yieldlove: fix for A/B Testing

Changed

DMP: changed context categories

Changed

SSP: Previews are now renderd only in givin Adslot

Release 11.06.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/500

Entry

Description

Entry

Description

Added

CMP: first iteration of a very simple state management, used to coordinate events and event triggers.

Added

PREBID: Automatic upload from YLScript to our CDN's

Added

PREBID: YLScript can now be loaded from Stroeer CDN's (cdn.stroeerdigitalgroup.de or cdn.interactivemedia.net).

Changed

CMP: Fixed Debug Log in Sourcepoint Module

Changed

CMP: Targeting pixels will now check if a given event concerning their load pattern has already passed. If the event has passed the pixel will fire at once, if the event was not triggered yet, queue the pixel until event execution. Will fix some errors of pixels using the consentManager, when the user makes their consent choices not "at once".

Changed

SDG: Minifier Optimization



Release 04.06.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/494

Entry

Description

Entry

Description

Added

Build Process: new config entry in local.json and global.json for building a website

Changed

Build Process: globalAdTag files will only be build when website requests it

Added

TCF1: Cache is now checked if consent has been changed since last set

Changed

TCF: added different config keys for consent controller URLs to make it easier to switch from one framework to another

issue

TCF: If a website actively switches from TCF1 to TCF2 within the same browser session the vendor Object is not filled properly. This is a very seldom case and the issue resolves itself when the browser is restarted


Release 02.06.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/491

Entry

Description

Entry

Description

Changed

optimized log messages and removed javascript variables in messages. Are now replaced by console.log placeholders, which will be correctly parsed and replaced when translating messasges

Changed

optimized minifier process


HotFix Release 28.05.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/489

Entry

Description

Entry

Description

Changed

readded option send "withCredentials" when using XmlHttpRequests, after Ströer DMP suffered massive cookie sync problems.

Release 26.05.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/483

Entry

Description

Entry

Description

Changed

fixed unnecessary error message when registering a local adslot.

Added

added new Logging System into MetaTag. Log messages will now be saved in separate file and loaded asynchronously if the user opens the info tool. This will help in bringing down the file size of metaTag

issue

The new Logging system Temporarily can threw an Error when calling the Info-Tool. This should be fixed as soon as the our cache gets flushed from our systems. 

Release 20.05.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/482

Entry

Description

Entry

Description

Changed

fixed error in consentManager IAB TCF1.0, stopping the consent Manager in some cases

Release 13.05.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/477

Entry

Description

Entry

Description

Added

TagMananger now supports IAB TCF 2.0 Consent Management. See https://iabeurope.eu/tcf-2-0/ for extensive information on the Consent Framework

Changed

keyValue for Yieldlove HeaderBidder, to measure revenue impact of performance boosts during website load process (mts = 1 for metaTagSpeed = active)

Release 06.05.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/476

Entry

Description

Entry

Description

Changed

minor fixes in sourcepoint.js

Changed

fixed DFP Consent value when an external CMP is used

Release 29.04.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/471

Entry

Description

Entry

Description

Changed

fixed bug in infotool where registred slots are shown twice

Changed

reverted -use-strict in Core due to Issues in IE

Release 23.04.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/466

Entry

Description

Entry

Description

Changed

CDN Switch optimization, small internal changes

Changed

Updated Grunt packages

Changed

small fixes within MetaTag (code cleanup)

Changed

Info-Tool Touch fix for Mobile


Release 16.04.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/459

Entry

Description

Entry

Description

Added

StickyStop feature. User can now stop sticky object anywhere in the middle of the page.


Release 07.04.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/457

Entry

Description

Entry

Description

Changed

fixed A bug in our newConfig so the GenericTargetings will fire again


Release 01.04.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/452

Entry

Description

Entry

Description

Changed

Complete internal rework of MetaTag on how our Config Files are managed and built.

Changed

Testing within Core now possible through 1 Project.

Changed

new Build File which runs for all projects and repositories concerning MetaTag.

Release 26.03.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/450

Entry

Description

Entry

Description

Added

We now have the ability for an A/B Test loading yieldlove from our CDN or Yieldlove's CDN

Added

introduced new keyValue data from the DMP (IAB Taxonomy based context information)

Release 24.03.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/449

Entry

Description

Entry

Description

Changed

The Copy-button Position from our Info Tool was out of the visible area on some mobile page(s)

Changed

improved yieldlove measurement to distinguish more clearly between "time to load website", "time to load yieldlove script" and "time to auction end"

Changed

made format feature "connectedTo" more resilient to errors. If the parent Format is not active or can not be identified, deactivated the new format.

Release 16.03.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/443

Entry

Description

Entry

Description

Added

New functionality introduced to Formats, where one formats "availableOn" value can be based on another format. This should solve the usecase when deploying new formats, that are derivatives from another ("StickyBillboard" is related to normal "Billboard" format and should deliver on the same slots).

Added

The Auction Logs from Yieldlove are now implemented.

Changed

Info-tool: position of copy-button fixed. 

Release 10.03.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/441

Entry

Description

Entry

Description

Changed

Fixed caching of consent data in CMP module and cleaned up the code.

Changed

Sticky function - fix for responsive pages. Now sticky objects follows the reference objects regardless of changes of dimensions and position of the reference.

Changed

Removed format templates, which will be now loaded only, when the format is actually needed on the website.

Release 02.03.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/437

Entry

Description

Entry

Description

Added

Added Preview for SSP.

Changed

fix for sourcepoint.js, was checking the wrong value to make a decision about serving the consent manager or not.

Release 24.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/431

Entry

Description

Entry

Description

Added

MetaTag is now able to read Consent from __cmp() when an external CMP is used.

Changed

re-activated PI Logging and code cleanup for Coralogix.

Release 18.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/427

Entry

Description

Entry

Description

Added

new functionality to lazyLoad Slots due to the visibility Percentage from the Slot itself

Release 17.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/427

Entry

Description

Entry

Description

Added

new functionality to block a format only on one specific slot, while all other slots remain unaffected

Changed

Neustar (Procter&Gamble) can now use GDPR signals more in line with the IAB TCF framework

Changed

queueController will not queue adslots for loading, if they are already loading.

Release 14.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/423

Entry

Description

Entry

Description

Added

New loadQueue "Controller" and "GoogleDFP" updated. LoadQueues are now aware of each other, which enables us to control the Google AdManager more granually when defining a "page impressions". 

A "page impression" is responsible for determine which creatives are already shown, and which creatives might still be show. Especially in situation where adslots are loaded at a later point in time (or reloaded after some time) we will now have more information to deliver the right creative or block unneeded creatives.

Release 10.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/421

Entry

Description

Entry

Description

Added

new interface on Slot level to mark any DOMNode. When the slot is reloaded or deleted all DOMNodes added via the Slot will be iterated upon and any content in those Nodes are deleted. The nodes itself will be kept. This will help our ad developers to let our more complex formats be deleted and removed completely from the website, if they are no longer needed.

Changed

Added small fixes for our SDG CookieLayer (IE 11: height fix for when body is not completely loaded, All Browsers: safety checks so counting is not double, script will only be delivered if user has not seen the layer)



issue Due to a JS Error in a specific Site Configuration Setup we rolled the release 04.02.2020 back to release 28.01.2020 until this is fixed

Release 04.02.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/417

Entry

Description

Entry

Description

Added

Yieldlove Auction Time to our Performance Logs in Coralogix

Added

new interface on Slot level to mark any DOMNode. When the slot is reloaded or deleted all DOMNodes added via the Slot will be iterated upon and any content in those Nodes are deleted. The nodes itself will be kept. This will help our ad developers to let our more complex formats be deleted and removed completely from the website, if they are no longer needed.

Changed

Added small fixes for our SDG CookieLayer (IE 11: height fix for when body is not completely loaded, All Browsers: safety checks so counting is not double, script will only be delivered if user has not seen the layer)

Release 28.01.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/410

Entry

Description

Entry

Description

Changed

Fix for our Info-Tool on Mobile. Counter is now working properly on IOS.

Changed

Cookie Layer Fix for IE 11. In certain conditions on IE 11 an error was thrown and the layer could not be played. This is now fixed

Changed

Hover Style now fixed for cookie layer.

Release 21.01.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/404

Entry

Description

Entry

Description

Changed

Streamlined build process of metaTag, some steps are no longer needed and have been removed from the process (mostly compressing files, will now be done automatically by CDN)

Added

Introducing a new (internal) way to load AdSlots and to group those Slots together.

Grouping AdSlots is important for the AdServer to control which adSlots should deliver the same campaigns, or which AdSlots might have delivered a campaign that blocks another campaign from delivering (brand exclusivity, 100% share of voice campigns, etc)

Grouping of adslots is now more consistently solved in MetaTag. We just dont derive the possible intent of the website, but use further "clues" to cluster AdSlots together (time between registerSlot(), time to auction slots, adSlot features like LazyLoading, etc).

Publishers dont have to change anything, the new feature will work automatically.
For now we will roll out this new feature on very few sites to evaluate the impact. Only after further thorough testing we will apply the feature to more sites.

For the time, until all websites have been activated for feature, we will deliver around 2-3kb minified, redundant code, to have the possibility to switch to the new solution on the fly. As soon as the feature is activated over the whole network (probably mid to end-february) we will remove the redundant code.



Release 20.01.2020 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/403

Entry

Description

Entry

Description

Changed

restructered a few log messages during the adslot loading process, this should help find important messages faster

Changed

fixed a bug with some charsets (ex: charset="iso-8859-1") on websites causing german "umlaute" in our InfoTool/CookieInfo Layer to not be rendered properly

Changed

CookieInfo Layer can now be loaded from different Ströer CDN's. Some sites use one of our older CDNs, which in turn can cause trouble for IE11. IE11 has a stricter cross-origin ruleset, especially when scripts from different domains A and B are used on site domain C.

Changed

fixed a bug in the deployment process of the CookieInfo Layer, so the current version is always rolled out and not an older one.

Added

new Event for indicating that an AdSlot is about to reload. This Event will be triggered before the AdSlot call process starts and can be used to do any task that my be required before the AdSlot can safely reload (ex: removing HTMLElements, etc)

Release 14.01.2020- https://github.com/mbrtargeting/stroeerMetaTag-development/pull/396

Entry

Description

Entry

Description

Changed

  • setZone() Bug. Now when a Zone gets changed to a new Zone without loading a new PI and a refresh Slots is performed, the proper Zone will be requested

  • Our Headerbidder is now able be blocked on Certain Browsers for specific websites

Release 19.12.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/390

Entry

Description

Entry

Description

Changed

  • Meetrics ADAM bridge function (collect viewability keyvalues before ad call) will now use event based triggers instead of extensive call stacks

  • Rollout of ADAM Bridge functionality to all websites (tries to forecast visibility rates based on historic data). If Meetrics collects and store keyvalues (historic data), we will get a accurate forecast for the ad call, Otherwise we assume that the ad call is being able to reach all viewability thresholds, and parse this info to the adserver. We can use this to only deliver visibility-based campaigns to a page, which is likely to actually reach the threshold asked by the advertiser.

  • Added proper Publisher Interface to check for IAB consent (for more information please see: German MetaTag Documentation#getCustomVendorConsentSDG.Publisher.getCustomVendorConsent(vendor)

  • Fixed a log error within sourcepoint

  • Fixed gesture control for our Info-Tool

Release 16.12.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/387

Entry

Description

Entry

Description

Changed

  • Fixed bug when meta keywords tag was present, but without content.

  • VAST adtags will now include the website url up to 250 letters.

Release 10.12.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/381

Entry

Description

Entry

Description

Changed

  • Optimized Styles in our Cookie Layer for IE11 and Edge

  • Added new functionality to personalize text size/ button text size on Mobile

  • Added support for 3rd Party Systems through the Object: SDG_CookieLayer_Styles

  • removed redundent Yieldlove Event for Slot reloading

  • new keyvalue for PPA to report on which impressions is a reloaded impression

Added

  • Trafiller script is now live in our Core and will be activated on the sites:

giga.de, desired.de, kino.de and familie.de

Release 04.12.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/375

Entry

Description

Entry

Description

Changed

  • Fixed Styles on our Cookie Layer

  • Added funcitonality to personalize: buttonColor, buttonBorder, buttonRadius, fontSize, buttonFontSize, linkText, linkURL, layerFontFamily

  • Script Now testable through Demo Parameter which loads file from a non-cached folder for testing

Release 29.11.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/370

Entry

Description

Entry

Description

Changed

Update for "cookie consent" layer with new functionality and css styles.

Added

Meetrics solution "ADAM Bridge" implemented with more possible keyValues. This solution will enable the adserver to collect chance based information on how likly some viewability thresholds will be reached before the adserver actually receives the call. This will help to deliver viewability based campaigns only to impressions that have a valid chance to actually serve the impression successfully without wasting inventory.

Changed

When delivering ads, MetaTag will now parse most ads and validate at least minimal HTML specifications (like a <html> and <body> tag) and if missing, add them. This should help in avoiding erroneous displayed ads.

https://stroeerdigitalgroup.atlassian.net/browse/TICKET-15960

Release 26.11.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/368

Entry

Description

Entry

Description

Changed

changed parameter in setPersonlizedAds for GoogleDFP now uses correct types in function argument

Added

Google Cookie Layer Module 



Release 14.11.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/363

Entry

Description

Entry

Description

Changed

Our Into-Tool (https://stroeerdigitalgroup.atlassian.net/wiki/x/x2LNAQ) will now load most of its JavaScript payload only when the Info-Tool is started by the site user, reducing the initial file weight of the metatag.min.js

Changed

The Info-Tool can now be started on mobile websites by placing 3 fingers on the screen and holding them there for 3 seconds. Documentation for the Info-Tool will be changed the coming days.

Changed

A site user can now place a support ticket directly from the Info-Tool by selecting the new "Support" tab in the tool. An account for our Publisher-Support Center will be required. Please contact your Ströer representative if you do not own an account.

Changed

Error in Slot API .removeTargeting when using method chaining has been fixed



Release 30.10.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/360

Entry

Description

Entry

Description

Changed

Cleaned up redundant Code from our MBR Module

Changed

Fixed a bug within our Positioning from ADEX Billboards

Changed

Renamed our out-of-page slot to out_of_page as our Meetrics Identifier

Changed

Format sizes are now able to be counted up per toggle within its first size in tag.

Release 24.10.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/355

Entry

Description

Entry

Description

Changed

NetID: HotFix in Domain Protocoll for NetID Test.

Release 22.10.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/349

Entry

Description

Entry

Description

Changed

Nuggad: Removed Obsolete code/logic for handling OMS Websites with Nuggad

Changed

NetID: Incase the MBR User ID or the Yieldlove Auction ID is not available a default Value of 0 will be sent.

Release 17.10.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/349

Entry

Description

Entry

Description

Added

Pubstack Pixel: This will allow us to generate better reports for our Header bidder

Added

NetID Pixel: Test for 1 week. Details are available here: NetID-Test

Changed

Backwards compatibility fix:OMS video tags will be able to get Nuggad segment information and pass it on to the video ad server.
This is necessary, otherwise the old video tags might not work anymore when the old "oms.nuggad.net" pixel is deactivated

Changed

In case of a canceled measurement the output will now be changed from error to debug. It was falsely marked as an Error.

Release 30.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/336

Entry

Description

Entry

Description

Changed

Formats can now be configured if they should count their dfpSizes up for each format occurrence, if the format is present multiple times on the same page

Changed

The Flex Ad Formats from the "IAB New Ad Portfolio" will now use only one Google Ad AdManager Size. Beforehand each format used a "base" size and an "occurence size", depending on how many possible adslots could display the FlexAd (ex base: 10x30, 10x32 for second occurence on the same page). This was intended for easier campaign booking, but never paid off and wasn't used. Each format will now only retain its base size.

Changed

backgroundColor of Ad Formats (for example "Wallpapers") will now be deleted, if an adslot is going to be reset (be it because of an reload, or because the slot will be deleted)



Release 26.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/333

Entry

Description

Entry

Description

Added

(For this to have any effect, your website will need to be part of our CMP network and the Ströer CMP needs to be activated on your site.)
New interface for ConsentManagementPlattform (CMP) for "Data Supplier/Vendors", which are not part of the IAB Consent Framework (https://iabeurope.eu/transparency-consent-framework/).

In most cases these will be vendors directly employed by websites, without any ties to the IAB.

If you are a website and use such data vendors, you will be able to have us insert your vendors into our consent plattform. At this point we will be able to gather consent data for your vendors, as well as the standard IAB approved vendors. Please contact your Ströer representative if you like to add your vendors to our CMP.

Further new methods in our "Publisher" interface will allow you to query our CMP and read the gathered consent for your vendors.

However we will not interact with your vendors directly!

Should a user deny consent for your vendors, it will be your task to either block your vendors or signal the vendor that the user revoked consent.

All IAB approved vendors will still be handled (activated/deactivated) by us, based on the consent of the user.
For further information please read our documentation and code examples.
https://stroeerdigitalgroup.atlassian.net/wiki/x/qQcTAw#GermanMetaTagDocumentation-ConsentManagmentPlatform(CMP)

Changed

Removed modules "BugSnag", "PraeludiumConverter", RecommendationAds" and "Remintrex"
All modules were not used for a long time. In order to reduce unneeded code, we are sunsetting these modules.
This should get us back under 60kb transfered size for metaTag.min.js

Changed

Removed synchronous tag logic in module "GoogleDFP". Since Google no longer support synchronous tags, this is unneeded code

Changed

Removed all mentions and methods for the above modules in our test and development process, moved the code to "archive" sub directory

Changed

GPT.js will now be loaded from another domain, since Google is consolidating their different delivery server under one roof.

Changed

"Modular AdSlots" will now recover better from misconfiguration during their setup. Especially the adserver sizes are repeatably a source for problems. We will now try to convert the publisher input into the correct format but still signal the user that there is an error.
https://stroeerdigitalgroup.atlassian.net/browse/TICKET-15278
https://stroeerdigitalgroup.atlassian.net/browse/TICKET-15285
https://stroeerdigitalgroup.atlassian.net/browse/TICKET-15277

Changed

Made the type documentation for modular slots much more clearer

Release 25.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/327

Entry

Description

Entry

Description

Changed

calling Slot.removeTargeting method now will delete the targeting key on the tagManager as well as on the "Google Publisher Tag" AdSlot. Formerly only the tagManager removed the key, but later calls from "GPT" still contained the removed key.

Changed

added error events to "Yieldlove" module and "InfoTool". This will help to recover from otherwise fatal HeaderBidder errors and hopefully provide more insights into the possible error source

Changed

optimized "DeutschePostCookie" module, will now load after the website is completey finished

Changed

reactivated "Neustar", a targeting pixel from Protcer&Gamble. Edited the pixel according to Neustar documentation to respect GDPR

Changed

"GoogleDfp" Module will filter duplicated "sizes", which are used to indicate which format should the adserver deliver. During a transition period, it might occur that our "formatController" as well as the "slot" config will have the same sizes configured. While a duplicate size should have no effect on Google AdManager, we are better safe than sorry.

Changed

Deactivated module "Praeludium Converter" on the whole network. This module did provide some very, very old methods to interact with our former TagManager "Praeludium". Since "Praeludium" was not in active circulation for 2 years, we will remove the module completely soon, and started by deactivating it.

Release 11.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/325

Entry

Description

Entry

Description

Changed

Bugfixes in video modul after yesterdays release:

  • Zones with less than 3 characters are now supported

  • Format names are correctly translated depending on the publisher input and config. Some sites use other names for the video formats, and therefor the tagManager should honor those names correctly. Thanks for the info @Stefan Steurenthaler !

Release 10.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/323

Entry

Description

Entry

Description

Changed

Cleaned up "Video" module. Methods have clearer names and use our coding standards

Changed

Video module can now handle new formats, which might be added dynamicall by Ströer or the publisher. Before the system was locked into only 5 formats.
https://stroeerdigitalgroup.atlassian.net/browse/TICKET-14463

Changed

MutationObserver will now be able to report multiple new DOMNode on the website, in one event cycle. Before only one DomNode per event cycle was reported.
This is used to identify new DOMNodes, which are dynamically added to the site. If the TagManager detects a DOMNode which is associated with an AdSlot (for example by registering an adslot onto it), the TagManager will start and insert the process for delivering ads to this Node.
https://stroeerdigitalgroup.atlassian.net/browse/TICKETEXT-896

Added

New API for Publishers: SDG.Publisher.generateVastUrls(). This works exactly like "getVastAdDataObject", its just named more clearer. "getVastAdDataObject" will still work for the foreseeable future (2+ years), but we will remove all mentions of this method in our documentation and replace it with "generateVastUrls"

Added

Over the next 2 weeks we will added multiple new "adserver sizes" to our adslots. These will allow us to report revenue more detailed, down to the delivered "Format" in relation to an "AdSlot". Furthermore detailed targetings will be available for booking campaigns.



Release 03.09.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/318

Entry

Description

Entry

Description

Changed

ADX Billboards will no longer use a zIndex of 10, this should help in avoiding collisions between layering navigations and the Billboard.

Added

A new CookieSync feature was added to the Core of MetaTag, and set to inactive. This feature will allow selected partners to sync their cookie / user data to other systems in the future. Those other systems will be able to better decide, if they want to buy an impression generated by that user.
The feature is currently not syncing any cookies, but instead sits idle and awaits final activation until all relevant steps are taken (GDPR cleared, websites informed, etc).



Release 13.08.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/314

Entry

Description

Entry

Description

Changed

mobile adslots will now work with lazyLoad options, relates to https://stroeerdigitalgroup.atlassian.net/browse/TICKET-14043

Changed

lazyLoad Slot will now wait until it is actually in view, when the slot is also auctioned of via headerbidder, instead of just loading straight away as soon as the auction finishes



Release 12.08.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/310

Entry

Description

Entry

Description

Changed

"Placement" module: streamlined and removed excessive calls to discover the "PublisherConfig" module, this should skimp a few milliseconds off the module initialization

Changed

"AdTemplates" module: removed method to build flash banner. R.I.P. Flash (saves a few KB)

Changed

"ConsentManager" module: Sourcepoint will now use a new config parameter "messageDomain" to determine which domain will handle connection to sourcepoint server

Changed

"ConsentManager" module: new message library for CMP tool. Includes some smaller bugfix and changes from "Sourcepoint".

Changed

"Formats" module: Formats now use a default template, if no other setting is used in the config (saves a few lines in config)



Release 30.07.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/306

Entry

Description

Entry

Description

Changed

added fix for IE11 where in some cases the window.console object was not loaded properly and the logger would cause a fatal exception

Changed

added additional keyvalue "as" containing the slotname of the adslot. Since this keyValue will be used as customDimension in DFP, we can not send the name of very publisher defined adslot. therefor making a new keyvalue necessary

Changed

fixed detection of Edge browser in "Info Tool"



Release 22.07.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/303/

Entry

Description

Entry

Description

Changed

Fixed error with GPT command queue, which in rare cases would result in commands beeing send to a shallow array copy of the command queue, instead to the real command queue.

Added

New function to load external templates for formats on runtime. This will replace our static template library (prepacked with all metaTag version) in a bid to decrease javascript payload.Templates will be loaded only when the format is actually delivered to the website. This might delay the creative shown for a few milliseconds. We will test this in the next few weeks before fully commiting to load all templates from an external resource.



Release 01.07.2019  - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/299

Entry

Description

Entry

Description

Changed

removed an unnecessary calculation when to actually draw a background color. This calculation was used in case multiple formats with a background color wanted to share the same impression. However no products actually ever used this feature, therefor we removed it.

Changed

fixed error in resetting the background color back to the original value used by the website

Changed

added additional type checks suggested by meetrics to cancel an error message on microsoft edge browser

Release 11.06.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/294

Entry

Description

Entry

Description

Changed

fixed return value of getSlotForEvent in case of native dfp slots

Added

Code for our Meetrics Test concerning Visibility Data to be sent per KV now live. XHR Request gets sent to Meetrics



Release 04.06.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/292

Entry

Description

Entry

Description

Changed

Google provides 2 new events (slotRequested, slotResponseReceived) in their "Google Publisher Tags". MetaTag utilizes these events to trigger its already known events "SlotCalling" and "SlotResponded" more accurately

Changed

Fixed mix up of "Subzones" in connection with mobile "PostFix" attributes. Mobile Placements often use a "Postfix" to identify the slot more clearly in the adserver (for example: _b1 or _b2). These Postfixs were not correctly appended to the AdUnit Name when the Publisher also used the "SubZone" attribute for defining their own, locally used adslots.



Appendum: issue
During Deployment an error emerged on the latest Chrome versions (Chrome 70-74) in around 20-40% of all Chrome impressions.

The error did go live at around 16:05 on June, 4th 2019, and was detected at 16:15.
A hotfix was deployed at 16:30. Around 17:00 all websites have received the hotfix and operations were back to normal.

Cause of the problem was a "race condition" between two inter-dependent scripts:
If "script A" was NOT loaded before "script B", the error occured.

The error showed only in specific conditions and was therefor not catched in our testing phase of the deployment.
We changed the testing procedure and will now test inter-dependency more rigorously.

Release 28.05.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/287

Entry

Description

Entry

Description

Changed

Deleted some unused code in Meetrics module

Changed

Meetrics module will now log which information is sent to Meetrics for debugging

Changed

TimeTracker Module added to Yieldlove and Meetrics

Changed

Typos fixed in Yieldlove and Meetrics module



Release 08.05.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/283

Entry

Description

Entry

Description

Added

Tool for logging performance of metaTag scripts (load and execute time), will only be activated on selected sites

Changed

AdPage collection tool reworked and fixed names of some internal methods (no real impact on the collection of AdPages itself)

Release 29.04.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/279

Entry

Description

Entry

Description

Changed

fixed Placement.removeSizes() not working sometimes, depending on when the publisher called the Method



Release 17.04.2019 -  https://github.com/mbrtargeting/stroeerMetaTag-development/pull/275

Entry

Description

Entry

Description

Changed

When setting formats and AdSlots sticky, the adslot can now beconfigured to ignore the a possible sticky navigation of the website. In case the navigation of the site does not cover the whole viewport, but only the width of the content, ads around the content should not change their position to accomodate the navigation.

Changed

Fixed all remaining instances of "advertisment" and renamed it to "advertisements"



Release 15.04.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/275

Entry

Description

Entry

Description

Changed

An adslot can now be configured to decide, if the sticky navigation of a website should be used when determining the position (top, left) of a sticky advertisement.
This will be usefull when the sticky navigation is the same width as the content of the site, but some adslots are positioned left and right of the content and will never "touch" the navigation.

Changed

major typo fixed. The english word "advertisement" is NOT spelled "advertisment"



Release 27.03.2019 - https://github.com/mbrtargeting/stroeerMetaTag-development/pull/267

Entry

Description

Entry

Description

Added

Added a new keyValue, when the viewport is smaller than 450 pixels AND the user agent is detected to be problematic with the rich-media formats from the vendor "InSkin".
This will help to block "InSkin" formats in browsers and devices not capable to display them correctly (for example: webview apps)