Video metrics for a campaign without videos

[c_chauve]

Hello,

For this campaign: a5h5r.

We’re getting video conversions:

  "data_type": "stats",
  "time_series_length": 1,
  "data": [
    {
      "id": "a5h5r",
      "id_data": [
        {
          "segment": null,
          "metrics": {
            "video_views_50": [
              272
            ],
            "video_views_75": [
              254
            ],
            "video_3s100pct_views": [
              153
            ],
            "video_cta_clicks": null,
            "video_content_starts": [
              301
            ],
            "video_views_25": [
              288
            ],
            "video_views_100": [
              270
            ],
            "video_mrc_views": [
              205
            ],
            "video_total_views": [
              205
            ]
          }
        }
      ]
    }
  ],
  "request": {
    "params": {
      "start_time": "2018-01-01T23:00:00Z",
      "segmentation_type": null,
      "entity_ids": [
        "a5h5r"
      ],
      "end_time": "2018-01-08T23:00:00Z",
      "country": null,
      "placement": "ALL_ON_TWITTER",
      "granularity": "TOTAL",
      "entity": "CAMPAIGN",
      "platform": null,
      "metric_groups": [
        "VIDEO"
      ]
    }
  }
}

Problem is that the campaign doesn’t contain any Tweets with video (only two Tweets with photos). Could you check why this is happening?

Thank you,

Chris

[c_chauve]

Hello,

Any feedback?

Thanks,

Chris

[juanshishido]

Thanks for the follow up, @c_chauve. We’ll take a look.

[c_chauve]

Hello @juanshishido,

Any news

Thanks,

Chris

[juanshishido]

Thanks for the follow up, @c_chauve. We’ve identified the issue. However, we don’t have a timeline for when this may be addressed. For now, the guidance is to not retrieve video metrics for Tweets without videos.

[c_chauve]

Hello @juanshishido,

Problem is that in terms of dev, it doesn’t make sense for us to check each campaign’s tweets to know what to ask when getting the account/stats values.

Usually, the guidance would be to ask for everything and then to display what we have, that’s why we currently have this issue in our UI when clients are checking their campaigns’ stats.

I mean, it’s a bit strange to add this kind of “if” in our code just to build a workaround to an issue you identified, especially because it will require time (coding, testing…).

Thanks anyway for this acknowledgement! Please let me know if you manage to get any ETA at some point so we’ll be able to communicate about this to let our clients know that the resolution of this issue is on going.

Best,

Chris

[juanshishido]

Makes sense, @c_chauve. Some partners use the objective to determine what metrics to request. The idea is to reduce the cost of the query. However, it depends on what your users expect. If it’s more important for the data to match what’s on ads.twitter.com, then I understand your approach. This is a discrepancy on our end. Will update this thread as I get more information. Thanks!

[Manuel_Roy]

Hello @juanshishido

Do you have any update to share with us ?

Thanks

[juanshishido]

@Manuel_Roy: I don’t believe we will address this in the near term.