Development Newsletters

Release: 11-02-2015

List of new features and major fixes for this release:

  • Modification of scripts for Facebook
  • gDE API update

Scripts modification for Facebook

Facebook was not accepting two dots next to each other in the identifier in our click tracking scripts. As of this release, to give gDE users a possibility to easily get scripts that will be accepted by Facebook, our scripts are under control and they won’t contain two dots anymore.


gDE API update

In two weeks, with Release: 2015-02-25 we will introduce changes to the gDE API in commands operating on target URLs in campaigns. They will be necessary to define more advanced forms of target URLs. Please perform all necessary modifications to your internal tools to ensure smooth running as far as gDE API operations are concerned.

Please find below the list of changes.

GetPossibleTargetURLElementValuesList operation:
Changes will be made to output parameters:

  • Output
    • Old definition:
      <GetPossibleTargetURLElementValuesList>
        <status>OK</status>
        <valuesNumber>1</valuesNumber> : uint
        <values>
          <value>
            <valueID>34</valueID> : uint
            <name>Campaign name</name> : string(255)
          </value>
        </values>
      </GetPossibleTargetURLElementValuesList>
      
    • New definition:
      <GetPossibleTargetURLElementValuesList>
        <status>OK</status>
        <valuesNumber>1</valuesNumber> : uint
        <values>
          <value>
            <valueID>34</valueID> : uint
            <name>Campaign name</name> : string(255)
            <url_macro>CampaignName</url_macro> : string(255)
            <nameType>system</nameType> : enum('system','user')
          </value>
        </values>
      </GetPossibleTargetURLElementValuesList>
      

SetTargetURLElements operation:
Changes will be made to input parameters:

  • Input field
    • Old definition:
        - sessionID : string(16)
        - campaignID : uint
        - names : string(63) list
        - valueIDs : uint list
      
    • New definition:
        - sessionID : string(16)
        - campaignID : uint
        - values : JSON array of objects with fields 'name' and 'value' (eg. [{"name":"utm_campaign", "value":"[CampaignName]"}, {"name":"utm_source", "value":"[CreativeName]"}] )
      


GetTargetURLElementsList operation:
The following changes will be made to result parameters:

  • Output
    • Old definition:
      <GetTargetURLElementsList>
        <status>OK</status>
        <elementsNumber>1</elementsNumber> : uint
        <elements>
          <element>
            <elementID>3</elementID> : uint
            <name>utm_campaign</name> : string(255)
            <valueID>4</valueID> : uint
            <valueName>Campaign name</valueName> : string(255)
          </element>
        </elements>
      </GetTargetURLElementsList>
      
    • New definition:
      <GetTargetURLElementsList>
        <status>OK</status>
        <elementsNumber>1</elementsNumber> : uint
        <elements>
          <element>
            <elementID>3</elementID> : uint
            <name>utm_campaign</name> : string(255)
            <value>[CampaignName]_xyz</value> : string(255)
          </element>
        </elements>
      </GetTargetURLElementsList>
      


The description of the new API operations will be added to the official API documentation on our website after the release.

Should you have any questions, please contact your Local Technical Support office.

direct effect