Versions Compared

Version Old Version 19 New Version Current
Changes made by

Former user

Nicole Jünger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents

Supported AdServers

Google Ad Manager only 

...

Please use the field: ADvendio_KeyValues__c on those objects. It is named the same on all objects and gets transferred to the ad server. Also, note that these key values are not getting transported into the campaign item key-value fields and therefore are not shown on the pdf documents. Instead, they are transmitted directly to the ad server.

Syntax before version 2.112

Info

If you manually edit make sure that

  1. Only the Adserver's API names are allowed, do not use display names.

  2. Use spaces only before or after a connective (and, or). If a value contains spaces, you have to use quotation marks.

  3. If you have a key-value string in more than one object (AdSpec, Placement, and AdType) the resulting string will be concatenated with an AND. 

  4. No new values will be created. If a value does not exist, it will be ignored.

  5. Make sure that you combine expressions with the same key and operator into on line: (location=de,at,ch,fr,nl) instead of (location=de OR location=at OR ...)

We highly recommend that if you are using version 2.112 to automate these values by adding the 3.5.5.3 KeyValue Generator to generate key-values for AdType and AdSpec.

Manual Syntax Examples:

  • gender!=male

  • age=18,19,20,21 and gender=male

  • age!=0 or (gender=female and (cat=sport OR cat2="value with spaces") and location=de,at,ch,fr,nl)

Syntax Changes with version 2.112

Version 

2.112 and up

Supported Adservers

Google Ad Manager, Xandr, Freewheel

...

This results in the following changes to the feature:

1.) Keys & Values will be saved in a JSON string

Instead of the old format (e.g. Key = Value) The key values will now be entered in the form of a JSON string into the field:

{"KeyValue":{"type":"List","logic":"||","valL":[{"type":"List","logic":"&&","valL":[{"type":"List","logic":"==","valL":[{"type":"Id","valS":"a09A0000010it2KIAQ"},{"type":"List","logic":"||","valL":[{"type":"Id","valS":"a09A0000010it3yIAA"},{"type":"Id","valS":"a09A0000010it4KIAQ"},{"type":"Id","valS":"a09A0000010it4MIAQ"}]}]}]}]}}

As this refers to IDs instead of names, the system makes it easier to handle keys and values with special characters in their names.

To create these strings, please use the 3.5.5.3 KeyValue Generator on Ad Spec and Ad Type. Before doing this, you might need to enhance your page layouts, with the new buttons included in ADvendio.

2.) The Key-Value String Generator will only support the new format

The existing Key-Value String generator, which was used to generate a Key-Value string for the old format, will now only support the new format. 

Info

3.) Placement-level Key-Value targeting is not supported anymore

Before 2.112, it was also possible to define a fixed Key-Value string for Placements. For the new format, it will only be possible to do this for Ad Specs and Ad Types.

Migration steps for existing customers

Existing predefined Key Values for Google Ad Manager will continue to work for now, but to switch to the new system, you will have to do the following steps:

...

Note

We do not recommend to use the two different formats of Keys and Values in combination, as there might be unexpected results.

Additional Note - Key-Value connecting logic for Xandr

When using the fixed Key Values for Xandr, it's possible to create a targeting set, which can not be edited in the console UI of Xandr. This will be displayed as follows:

...