Invocation and delivery

Delivery settings

This setting deals with all options which
are related to the invocation and delivery engine. All of these settings are
stored inside the configuration file, so if you want to change these settings
the configuration file needs to be unlocked.

Delivery cache
type

To help speed up the delivery Openads uses
a cache which includes all the information needed to deliver the banner to the
visitor of your websites. The delivery cache is stored by default in the
database, but to increase the speed even more it is also possible to store the
cache inside a file or inside shared memory.

If you want to store the cache inside a
file you will need to make the cache directory inside the Openads directory
writeable. If this isn't the case this option will not be listed in the drop
down menu.

If you want to use shared memory to store
the cache you will need the sysvshm or the shmop extension for PHP. In some
cases you will need to manually configure additional settings in the delivery
cache plug in, which is stored in the libraries/deliverycache
directory.

Delivery limitations help you deliver the
banners more targeted to your visitors. If you are not using delivery
limitations you can disable the evaluations of the limitation altogether with
this setting. Disabling the delivery limitations will reduce the load Openads
is generating a bit. If you have disabled delivery limitations with this
parameter you can't modify any existing limitations from the admin
interface.

If you are using direct selection to
retrieve banners from the inventory you can use logical operators to create a
more complex query. If this option is disabled the load Openads is generating
will be reduced a little, but you will also loose the ability to create complex
and powerful queries. For more information, please read the User guide. This is
turned on by default.

For each banner, you can specify one or
more keywords. This option is needed if you want to specify more than one
keyword. This is turned on by default.

If you want to prevent publishers from
using particular invocation types, you can disable any of the available types
here. Even if certain types of invocation are disabled, exiting bannercodes of
that type will still continue to function. Only generation of new bannercodes
of that type is not allowed. If you disable interstitials or Popups, this will
also disable the corresponding zone types.

Use P3P
Policies

Internet Explorer 6 is the first browser to
implement the w3c P3P standard. The P3P standard is created to protect the
privacy of your users. By default Internet Explorer will reject third party
cookies, unless a valid privacy policy header is also sent, together with the
cookies. These setting will allow you send these privacy policies headers
together with the cookies which are being sent by Openads. If you want to
enable phpAdsNew' P3P Privacy Policies you must turn this option on.

The compact policy which is sent together
with cookies. The default setting is: 'cur adm our nor sta nid', which will
allow Internet Explorer 6 to accept the cookies used by Openads. If you want
you can alter these settings to match your own privacy statement.

If you want to use a full privacy policy,
you can specify the location of the policy.

Pack cookies to avoid cookie
overpopulations

Openads uses cookies to store informations
on the visitor browser for later retrieval. This is needed to have some
features like plain remote invocation and banner delivery capping. However
there is a limit of 20 cookies per domain defined by the RFC 2965 that some
browser enforce. This could cause some cookies to be deleted and prevent
Openads and other applications from working correctly. Since release 2.0.6 of
phpAdsNew, Openads has a way to get around this cookie limit, which basically
works by packing the informations in a smaller number of cookies.