Goal REST API bug fix.
Goal REST API bug fix
There was an issue with creating goals (POST) through the Goal API, where you could pass in a start date and time in the past. This caused delivery issues as it made it seem like the goal was lagging behind and under-delivering so Pulse would significantly accelerate the delivery to catch up, which led to uneven or over-delivery. From 17 July 2019, with the issue fixed, if you pass in the
startparameter in the past, it gets set to the date and time of goal creation. This is also consistent with the Pulse UI. Things to keep in mind:
- Passing in a start date and time in the past is only allowed if the end date
and time is also in the past, as this means that the goal is not active and
delivery is not affected. In this case, the
startparameter does not get set to the date and time of goal creation.
- Ad start date and time cannot be before goal start date and time. If you
want the ad to inherit the goal's start date and time, do not pass in the
startparameter when creating an ad through the Ad API.
This release includes the following documentation updates: