back to list

Desktop Dynamic Sidekick

Media delivery format

HTML5, JavaScript-Redirect


All URL-based components of an advertising medium (e.g. redirect, pixel tracker) must contain the IAB macro gdpr_consent=${GDPR_CONSENT_XXX} to process the TC string, where XXX is the numerical vendor ID according to the global vendor list of the IAB.

Pixeltracker without IAB macro of a vendor with ID 123:
This Pixeltracker incl. IAB macro:${GDPR_CONSENT_123}

More Information: here

Media delivery


Sebastian Krone
Tel.: +49 40 2866 864319


This ad format supports HTML5. HTML5 can be used to create interactive ad formats or complex animations.

  • A complete HTML file must be delivered. Tracking pixels and click commands must be integrated into the HTML code upon delivery if required.
  • The landing page must always open in a new window, e.g. via a "target=_blank" tag or a JavaScript function that opens the destination URL in a new window.
  • All JavaScript-based special ad formats must have a no-script area that ensures a graphic fall-back ad will be displayed.
  • When using global JavaScript variables, these should have their own namespace or else be clearly designated, e.g. "gujemsAdtext" instead of just "text". This clear designation requirement also applies when assigning HTML IDs (e.g. "gujEmsExpandableWrapper" instead of just "wrapper" for <div> containers) and ID, class and type selectors in CSS (e.g. .gujEmsClickAreas instead of just .clicks). Otherwise, site-specific variables/designators/CSS styles may negatively impact on the display and function of the ad and vice versa.
  • When using jQuery, the ad must check for any framework already loaded by the site (and in case of doubt, should use this framework). Your own framework can only be used if the site does not use jQuery.
  • document.write may not be used in the mobile context, since the ads are mostly loaded and executed in asynchronous environments. Alternatively, DOM operations like appendChild() should be used via a document.onload type handler.
  • The ad must independently identify the orientation of the device and, if required, independently adjust its visuals and functions to any shift between portrait and landscape.
  • Unless otherwise agreed, all media/script/style files for the ad must be hosted externally.
  • Unless otherwise agreed, the ad’s creator shall track all interactions.
  • In order for ads to be displayed in apps with the G+J SDK, these ads must be MRAID-compliant. MRAIDis a worldwide standard for displaying rich media in apps.
  • In such cases, G+J e|MS requires separate ad versions for mobile Web and for apps (MRAID-compliant) or a version with an integrated Web-app push/launch function.

For special ad formats that have been produced externally and delivered to us and any ad formats via redirect, G+J e|MS tracks the ad impressions (AI) generated by the ad server. G+J e|MS also offers the option of using tracking pixels and/or click commands in order to measure specified events/interactions in an ad. This tracking may incur special technical costs.

HTML5 Guidelines
HTML5 Guidelines
Tracking Guidelines
Tracking Guidelines
Most recent amendment