The original question was posted by a product manager. We are using the regular (non-batch) campaign update endpoint… documentation here ~ https://dev.twitter.com/ads/reference/put/accounts/%3Aaccount_id/campaigns/%3Acampaign_id
We saw this problem all day yesterday, starting at around 8AM Pacific Time. The last time someone intermittently tried to enable campaigns before this morning was at 5:30PM PT yesterday.
We then saw the same problem today for around half the work day (9AM PT - 1:30pm). I would say there’s about a 70% success rate based on the behavior I personally saw. I wasn’t attempting to hit the endpoint when the campaign manager’s contacted us about an inability to set the campaigns live at all, which was earlier today.
There is nothing unusual about the type of requests we’re making to the V1 ADS API campaign PUT endpoint. Here is sample data. Basically… we send up all the fields with the current value, and are toggling the “paused” field to mark the campaign ACTIVE.
{"account_id": "<account_id>",
"campaign_id": "<the campaign id>",
"name": "<the campaign name>",
"start_time": "2016-05-16T04:00:00Z",
"end_time": "2016-08-01T03:59:00Z",
"standard_delivery": true,
"paused": false,
"total_budget_amount_local_micro": 10000000000,
"daily_budget_amount_local_micro": 77000000,
"frequency_cap": 5,
"duration_in_days": 30}
If you’d like the accountId, campaignName, campaignId, etc… please contact me directly via Elyssa Toda, and I can send you the client info via email. Thanks for your help!
