Additional parameters in ad slots

atf-formatNote

This parameter is predefined. It is used to add some predefined special sizes to the selected ad slot format. Publisher can choose between:

• standard

• special

• native (for Native-Ads)

By default the ‘standard’ parameter is being used. If you would like to use only standard sizes then there is no need to add the parameter to ad slot description.

If you would like to add special sizes you need to add atf-formatNote=''special''.

Example with “standard”:

Example with “special”:

Example with “special” and “native”:

atf-gamnetwork

With this additional parameter we can send an ad-request of an ad-slot to another ad-server. It is used like this: atf-gamnetwork=”123456...”

atf-targeting-entitytype

The Tag-pages are not listed as channels within the contentType, but as articles even if they look like a channel. This can be seen in the following setup:

atf-targeting-entitytype="taxonomy_term/tags = contentType="article"

Open

atf-targeting-entitytype="taxonomy_term/channel" = contentType="channel"

Open

atf-requestType (managed via our SDK)

This parameter is predefined. It needs to be defined here request architecture.  The publisher can select from the following:

• single_request

• multi_request

By default the single request architecture is being used. If you would like to use single request architecture  then there is no need to add the parameter to the ad slot description.

SRA = A request to the Google ad server, which answers for several ad slots

MRA = One request per ad slot, therefore several requests are necessary for all ad slots on the site. See more information in the Google documentation 

In case of using the multi request architecture, you need to add atf-requestType=''multi_request'' .

Example with SRA:

Example with MRA: