Inconsistent results in reach estimate endpoint

k4rliky · 2016-04-18T10:59:45.055Z

Hi guys,

I’m getting inconsistent results when using /1/accounts/:account_id/reach_estimate , this happens using the v1 version of this endpoint.

I’m trying to determine the approximate reach of a particular campaign based on the following query:
$ twurl -H ads-api.twitter.com /1/accounts/18ce53vrk7s/reach_estimate objective=TWEET_ENGAGEMENTS&user_id=233631354&product_type=PROMOTED_TWEETS&currency=GBP&locations=ecdce75d48b13b64&platforms=0%2C1%2C2%2C3%2C4&tailored_audiences=1875d&campaign_daily_budget_amount_local_micro=1000000"

Result:

{ data_type: 'reach_estimate',
  data:
   { impressions: null,
     count: null,
     infinite_bid_count: { min: 1638, max: 2457 },
     engagements: null,
     estimated_daily_spend_local_micro: null },
  request:
   { params:
      { locations: [Object],
        tailored_audiences: [Object],
        product_type: 'PROMOTED_TWEETS',
        platforms: [Object],
        objective: 'TWEET_ENGAGEMENTS',
        account_id: '18ce53vrk7s',
        currency: 'GBP',
        followers_of_users: null,
        campaign_daily_budget_amount_local_micro: 1000000 } } }

As you can see, I get 2457 as the max infinite bid count (maximum number of users I could reach if I won every single bid with the current targeting criteria), however, If I add some tailored audiences that sum a total of 11.94M users, I still get 2457 (the same happens using tailored_audiences_expanded):

$ twurl -H ads-api.twitter.com /1/accounts/18ce53vrk7s/reach_estimate .... tailored_audiences&z1nc,182zy,184do,1875d,188ee,19tsd,19v89,19yx8 ....

Result (2457 again):

{
  "data_type": "reach_estimate",
  "data": {
    "impressions": null,
    "count": null,
    "infinite_bid_count": {
      "min": 1638,
      "max": 2457
    },
    "engagements": null,
    "estimated_daily_spend_local_micro": null
  },
  "request": {
    "params": {
      "locations": [
        "ecdce75d48b13b64"
      ],
      "tailored_audiences": [
        "z1nc",
        "182zy",
        "184do",
        "1875d",
        "188ee",
        "19tsd",
        "19v89",
        "19yx8"
      ],
      "product_type": "PROMOTED_TWEETS",
      "platforms": [
        "iOS",
        "Android",
        "BlackBerry phones and tablets",
        "Mobile web on other devices",
        "Desktop and laptop computers"
      ],
      "objective": "TWEET_ENGAGEMENTS",
      "account_id": "18ce53vrk7s",
      "currency": "GBP",
      "followers_of_users": null,
      "campaign_daily_budget_amount_local_micro": 1000000
    }
  }
}

Using a complex query that add more platforms, devices, and other targeting criteria produces a null result.

{
  "data_type": "reach_estimate",
  "data": {
    "impressions": {
      "min": 0,
      "max": 0
    },
    "count": {
      "min": 0,
      "max": 0
    },
    "infinite_bid_count": null,
    "engagements": {
      "min": 0,
      "max": 0
    },
    "estimated_daily_spend_local_micro": null
  },
  "request": {
    "params": {
      "locations": [
        "ecdce75d48b13b64"
      ],
      "tailored_audiences": [
        "z1nc",
        "182zy",
        "184do",
        "1875d",
        "188ee",
        "19tsd",
        "19v89",
        "19yx8"
      ],
      "product_type": "PROMOTED_TWEETS",
      "platforms": [
        "iOS",
        "Android",
        "BlackBerry phones and tablets",
        "Mobile web on other devices",
        "Desktop and laptop computers"
      ],
      "objective": "TWEET_ENGAGEMENTS",
      "account_id": "18ce53vrk7s",
      "network_operators": [
        "1i",
        "14",
        "2t",
        "1b",
        "2l"
      ],
      "currency": "GBP",
      "followers_of_users": null,
      "platform_versions": [
        "1",
        "2",
        "3",
        "4",
        "5",
        "6",
        "7",
        "8",
        "9",
        "a",
        "j",
        "m",
        "n",
        "o",
        "b",
        "c",
        "d",
        "e",
        "f",
        "g",
        "h",
        "i",
        "k",
        "l",
        "p"
      ],
      "devices": [
        "4n",
        "1l",
        "1k",
        "d",
        "1m",
        "30",
        "2x",
        "1h",
        "2i",
        "11",
        "j",
        "2k",
        "4k",
        "b",
        "2l",
        "41",
        "3g",
        "1c",
        "1a",
        "10",
        "2h",
        "28",
        "1e",
        "2p",
        "1b",
        "4l",
        "a",
        "34",
        "4m",
        "2o",
        "y",
        "1d",
        "c",
        "2q",
        "2m",
        "32",
        "1v",
        "1w",
        "1x",
        "1y",
        "20",
        "48",
        "1z",
        "49",
        "4a",
        "4s",
        "1q",
        "1r",
        "1s",
        "1t",
        "22",
        "21",
        "46",
        "47",
        "4q",
        "4r",
        "1u",
        "3h",
        "4j",
        "p",
        "3l",
        "r",
        "s",
        "3t",
        "1f",
        "2u",
        "1i",
        "4t",
        "4u",
        "4v",
        "4w",
        "4x",
        "50",
        "4y",
        "4z",
        "z",
        "m",
        "3c",
        "33",
        "39",
        "1j",
        "3o",
        "1n",
        "4o",
        "4p",
        "23",
        "4d",
        "4e",
        "7",
        "9",
        "3i",
        "3j",
        "t",
        "2w",
        "3v",
        "i",
        "3q",
        "26",
        "4i",
        "3d",
        "3f",
        "l",
        "x",
        "25",
        "k",
        "4f",
        "4g",
        "2",
        "2g",
        "w",
        "1g",
        "8",
        "15",
        "3",
        "1",
        "18",
        "4",
        "h",
        "3y",
        "40",
        "2r",
        "2n",
        "36",
        "35",
        "4b",
        "4c",
        "4h",
        "v",
        "e",
        "51",
        "38",
        "42",
        "u",
        "3k",
        "6",
        "2z",
        "3s",
        "n",
        "19",
        "o",
        "14",
        "2y",
        "3e",
        "45",
        "13",
        "24",
        "q",
        "2s",
        "16",
        "f",
        "3n",
        "31",
        "g",
        "2t"
      ],
      "campaign_daily_budget_amount_local_micro": 1000000
    }
  }
}

Is this endpoint broken? Am I doing something wrong?

thanks in advance

hwz · 2016-04-23T00:58:18.932Z

Thanks for reporting that. This is certianly very odd behavior. We’ll investigate this internally and get back to you soon.

k4rliky · 2016-04-24T10:26:56.636Z

@hwz thank you!

msbukkuri · 2016-05-08T20:35:43.756Z

@hwz @k4rliky Just wanted to provide you with more details on this issue, it looks like the infinite_bid_count that is returned in the reach estimate is always less than the count (which is the amount of people for the current bid - bid_local_amount_micro.)

Here is the twurl for example:

twurl -H “ads-api.twitter.com” “/1/accounts/4nuic/reach_estimate?product_type=PROMOTED_TWEETS&bid_amount_local_micro=1500000&currency=USD&objective=TWEET_ENGAGEMENTS&campaign_daily_budget_amount_local_micro=600000000&interests=19001”

And here is the response:

"data": {
    "count": {
        "max": 45013,
        "min": 30008
    },
    "engagements": {
        "max": 1286,
        "min": 857
    },
    "estimated_daily_spend_local_micro": {
        "max": 720000000,
        "min": 480000000
    },
    "impressions": {
        "max": 55074,
        "min": 36716
    },
    **"infinite_bid_count": {
        "max": 2076,
        "min": 1384
   }**
},
"data_type": "reach_estimate",
"request": {
    "params": {
        "account_id": "4nuic",
        "bid_amount_local_micro": 1500000,
        "campaign_daily_budget_amount_local_micro": 600000000,
        "currency": "USD",
        "followers_of_users": null,
        "interests": [
            "19001"
        ],
        "objective": "TWEET_ENGAGEMENTS",
        "product_type": "PROMOTED_TWEETS"
    }
}

@hwz Can you please take a look at this issue and advise appropriately?

k4rliky · 2016-06-17T19:45:02.805Z

@hwz Any progress on this task? thanks in advance

JBabichJapan · 2016-06-20T07:44:59.829Z

Hey folks,

Apologies for not alerting back here - we fixed some issues with reach_estimate endpoint and do not expect the buggy behavior to be happening now. To best catch our attention please post a new thread if you continue to see results which you believe are not correct.

Thanks,

John