Can no longer re-associate promoted tweets

api

#1

Hello,

As one cannot pause/un-pause individual promoted tweets (only line-items have this ability), we would typically make a DELETE request to accounts/:account_id/promoted_tweets/:id to “pause” our promoted tweet, and then make a subsequent POST request to accounts/:account_id/promoted_tweets to un-pause/re-enable the tweet.

This worked well, but now this method does not seem to work. We receive the following back:

POST (ENABLE) TWEET RESULT: [{:line_item_id=>"841e1", :display_properties=>[], :id=>"17yyik", :paused=>false, :created_at=>"2017-03-15T14:28:27Z", :updated_at=>"2017-03-16T16:40:09Z", :approval_status=>"ACCEPTED", :tweet_id=>"842019662158278657", :deleted=>true}]

When we check in ads manager, we still see the promoted tweet at ‘paused’. Note the deleted parameter in the response…this may indicate the source of the issue, but this field cannot be altered.

Any recommendation as to how we can use our existing methodology to simulate the pausing/un-pausing of promoted tweets, as we see it in the Twitter Ads UI?

Thanks,

Colin McDonald, Ampifii


REPLY


Can’t seem to give this as a reply below…so will post here and hopefully you can see it:

turning off:
DELETE TO /1/accounts/18ce541dt2m/promoted_tweets/17yyjm
DELETE (DISABLED) TWEET RESULT: {:line_item_id=>“841e1”, :display_properties=>[], :id=>“17yyjm”, :paused=>false, :created_at=>“2017-03-15T14:29:11Z”, :updated_at=>“2017-03-17T18:13:08Z”, :approval_status=>“ACCEPTED”, :tweet_id=>“842019845805871104”, :deleted=>true}

turning on:
POST DATA: {:line_item_id=>“841e1”, :tweet_ids=>“842019845805871104”}
POST (ENABLE) TWEET RESULT: [{:line_item_id=>“841e1”, :display_properties=>[], :id=>“17yyjm”, :paused=>false, :created_at=>“2017-03-15T14:29:11Z”, :updated_at=>“2017-03-17T18:13:35Z”, :approval_status=>“ACCEPTED”, :tweet_id=>“842019845805871104”, :deleted=>false}]

^^ looks fixed!


#2

Hey @ampifii

That’s an interesting situation. It would be helpful to have some additional information here:

  • The Ads account_id
  • The API calls (or sequence) of calls that you make to achieve this functionality. It would be helpful to have both, the request and response bodies.

Thanks!


#3

Additionally, a quick update. We’ve identified this as a bug on our end and we’re currently working through a fix. The additional information (mentioned on the previous comment) would be great so we can ensure things work as expected once a fix is in place.

Thanks!


#4

turning off:
DELETE TO /1/accounts/18ce541dt2m/promoted_tweets/17yyjm
DELETE (DISABLED) TWEET RESULT: {:line_item_id=>“841e1”, :display_properties=>[], :id=>“17yyjm”, :paused=>false, :created_at=>“2017-03-15T14:29:11Z”, :updated_at=>“2017-03-17T18:13:08Z”, :approval_status=>“ACCEPTED”, :tweet_id=>“842019845805871104”, :deleted=>true}

turning on:
POST DATA: {:line_item_id=>“841e1”, :tweet_ids=>“842019845805871104”}
POST (ENABLE) TWEET RESULT: [{:line_item_id=>“841e1”, :display_properties=>[], :id=>“17yyjm”, :paused=>false, :created_at=>“2017-03-15T14:29:11Z”, :updated_at=>“2017-03-17T18:13:35Z”, :approval_status=>“ACCEPTED”, :tweet_id=>“842019845805871104”, :deleted=>false}]


#5

Thanks, @ampifii.