Not getting Engagement metrics for ORGANIC_TWEET

api

#1

Hey, guys.
I am trying to download the engagement metrics of tweets.

I sent a POST request to download metrics (via async method) :

https://ads-api.twitter.com/1/stats/jobs/accounts/xxxxxx? end_time=2017-04-20T00%3A00%3A00Z&entity=ORGANIC_TWEET&entity_ids=ttttttttttt&granularity=HOUR&metric_groups=ENGAGEMENT&placement=ALL_ON_TWITTER&segmentation_type=GENDER&start_time=2017-04-14T00%3A00%3A00Z

I got a response with the job-id and url. But when gzipped json file gets downloaded, the data contains nothing other than the “id” of the entity.

 {
  "data_type": "stats",
  "time_series_length": 144,
  "data": [
    {
      "id": "xxxxxxxxxxx",
      "id_data": [
        
      ]
    }
  ],
  "request": {
    "params": {
      "start_time": "2017-04-14T00:00:00Z",
      "segmentation_type": "GENDER",
      "entity_ids": [
        xxxxxxxxxxx
      ],
      "end_time": "2017-04-20T00:00:00Z",
      "country": null,
      "placement": "ALL_ON_TWITTER",
      "granularity": "HOUR",
      "entity": "ORGANIC_TWEET",
      "platform": null,
      "metric_groups": [
        "ENGAGEMENT"
      ]
    }
  }
}

What am I missing?

thanks.
-jerry


#2

@JerryAclan: Thanks for the question. Please list the relevant ads entity IDs so that we may further investigate. Also, see our Guidelines for Reporting Issues post.


#3

Thank you Juan for responding so quickly.

The POST request is :

https://ads-api.twitter.com/1/stats/jobs/accounts/48g7op?end_time=2017-04-20T00%3A00%3A00Z&entity=ORGANIC_TWEET&entity_ids=853027657851838465&granularity=HOUR&metric_groups=ENGAGEMENT&placement=ALL_ON_TWITTER&segmentation_type=GENDER&start_time=2017-04-14T00%3A00%3A00Z

The response was:

{
  "request": {
    "params": {
      "job_ids": [
        854784792960937984
      ]
    }
  },
  "data_type": "job",
  "next_cursor": null,
  "data": [
    {
      "start_time": "2017-04-14T00:00:00Z",
      "segmentation_type": "GENDER",
      "url": "https:\/\/ton.twimg.com\/advertiser-api-async-analytics\/vQTzDH8toD1bJCDCDd7yr_DNBQdqnTSHjnM6aSvmuzfHkglwqpCezM68ONFOFdaS4yJCNh4eJ-yAeNCDMWGmN7HENoKq1gBoCUGdQEof30htwpEvJCz6kHosb3mCqi77.json.gz",
      "id_str": "854784792960937984",
      "entity_ids": [
        853027657851838465
      ],
      "end_time": "2017-04-20T00:00:00Z",
      "country": null,
      "placement": "ALL_ON_TWITTER",
      "id": 854784792960937984,
      "expires_at": "2017-04-21T19:52:32Z",
      "account_id": "48g7op",
      "status": "SUCCESS",
      "granularity": "HOUR",
      "entity": "ORGANIC_TWEET",
      "created_at": "2017-04-19T19:52:30Z",
      "platform": null,
      "updated_at": "2017-04-19T19:52:32Z",
      "metric_groups": [
        "ENGAGEMENT"
      ]
    }
  ]
}

But when I downloaded the JSON.gz file, all it contains is :

{
  "data_type": "stats",
  "time_series_length": 144,
  "data": [
    {
      "id": "853027657851838465",
      "id_data": [

      ]
    }
  ],
  "request": {
    "params": {
      "start_time": "2017-04-14T00:00:00Z",
      "segmentation_type": "GENDER",
      "entity_ids": [
        853027657851838465
      ],
      "end_time": "2017-04-20T00:00:00Z",
      "country": null,
      "placement": "ALL_ON_TWITTER",
      "granularity": "HOUR",
      "entity": "ORGANIC_TWEET",
      "platform": null,
      "metric_groups": [
        "ENGAGEMENT"
      ]
    }
  }
}

Thanks.
-jerry


#4

Hi, @juanshishido
were you able to get the chance to take a look at this issue?
thanks.
-jerry


#5

Thanks for following up, @JerryAclan! I will look into this today and get back to you.


#6

@JerryAclan: It looks like id_data is always an empty array when using segmentation_type with entity=ORGANIC_TWEET. We tested this with various Tweets and segmentation types. We’re trying to determine whether this is expected behavior or not. We’ll let you know as soon as we have an update.


#7

@JuanShishido : Good morning, Juan. Any update on this issue ?

Thanks.
-jerry


#8

Hi Juan,

We are also interested in this issue, was there any result from this?

Best Regards,
Evan


#9

@JerryAclan and @Evan20160: Apologies for the delay on this one. It’s likely that segmentation isn’t allowed for ORGANIC_TWEET entities, but we haven’t had a chance to confirm yet.


#10

Hey @Evan20160 @JerryAclan

Just wanted to close the loop on this issue. We’ve confirmed that we current don’t support any segmentation options for entity_type = ORGANIC_TWEET

Thanks!