...
Version | Type | Components | Description | ADvendio Ticket No. | Wiki |
|---|---|---|---|---|---|
2.131.3 | Changes & Optimizations | AdServer Gateway / Freewheel | We had issues, where our matching by account name was not working properly for our Freewheel integration. This means, if you were using an advertiser from ADvendio for the first time to push to Freewheel, which was already existing in Freewheel, the processes resulted in an error. You needed to manually match the IDs in ADvendio in order to make this work. Now this matching is working automatically again, without the user having to do something. See this page, if you want to know more about the matching of accounts between ADvendio and integrated systems. | AD-6150 | |
2.131.3 | Changes & Optimizations | AdServer Gateway | We fixed a bug, where all Connection IDs were imported with the active checkbox set to true. This could cause problems if you are using the 'filter by active records' setting to manually configure which targeting criteria (like audiences or keys and values) will be visible to your users in ADvendio. | AD-6193 | x |
2.131.3 | Changes & Optimizations | Publisher Payout | Fixed issue where Publisher Payout Collection process encountered a CPU limit where a single Invoice Item had thousands of Delivery Data Records. | AD-6195 |
...
To install ADvendio please use
Installation link 2.131.4 for your production environment (org) or
Installation link 2.131.4 to update your sandbox.
Version | Type | Components | Description | ADvendio Ticket No. | Wiki |
|---|---|---|---|---|---|
2.131.4 | Changes & Optimizations | AdServer Gateway, Targeting Sets | We encountered a problem with our flexible targeting preconfiguration via targeting sets. While it is possible that you can assign flexible targeting sets to accounts, ad specs or ad types and when you create a new campaign item, all criteria of these sets is shown in the media configuration to be edited. A problem in our Gateway caused the default targeting from the targeting template, to be always send to the external system. For Example, you defined that Geo Targeting for Germany for your products. You are now planning a Campaign Item from that setting. The new Campaign Item will have the targeting Germany selected, but you can remove it, in order to target a specific number of regions in Germany. The bug caused that still only Germany was sent to the AdServer. This is now fixed. | AD-6201 | x |