#1

Hello,

We automate campaign performance reporting and we are looking to add the 2 below metrics to the report which we pull. We are unsure of how to do this - would someone please be able to help us?

  1. ‘Website conversion by tag’ - When this is selected in the UI during export, a custom field is contained within the export its self. But how do we select or pull this from the API?
  2. DMA name/code (Designated Market Area) - Is this possible to pull from the API? If so, how?

Many thanks,

Cameron.

#2
  1. Tag-segmented stats are not available through the Ads API.
  2. To segment by DMA, use the CITIES segmentation type with our asynchronous analytics endpoint. (FYI, we are planning to update the name to METROS.)
1 Like
#3

Thanks for your response, Juan.

Could you please confirm for us; The metric downloaded from the UI that has a custom name applied in the export (Essence | Metro | Twitter | PEVR - Custom events), is not available on the Ads API?

We thought we might have been able to download the field ‘conversion_custom’ with a segmentation applied of ‘conversion_tags’. Is this not correct?

Many thanks,

Cameron.

#4

I don’t have familiarity with the UI export. Through the Ads API, we don’t have a segmentation type related to tags.

#5

Hey Juan,

FYI - We went ahead and tried to pull the field ‘conversion_custom’ with a segmentation applied of ‘conversion_tags’ from the API and it has worked.

image
image1150×884 86.8 KB

Cam.

#6

Thanks so much for continuing to look into this, @BorrettCameron. I didn’t realize that option existed in the Ads API, but I looked through source and confirmed. It looks like the enum value is: CONVERSION_TAGS. Thanks again!

#7

No problem.

Just touching back on DMA - Is there the equivalent of ‘dma name’ and ‘dma code’ for the twitter API?

You mentioned ‘cities’, but i know that other platforms will have both ‘city’ and ‘metro_id’?

Look forward to hearing from you,

Cam.

#8

Hey @juanshishido,

Just following up on this for DMA.

Thanks.

#9

Thanks for following up.

Are you looking for information on the location IDs? For example, for cities I can make the following request where the ID for Los Angeles the city is 3b77caf94bfc81fe.

$ twurl -H ads-api.twitter.com "/5/targeting_criteria/locations?location_type=CITIES&q=los angeles" | jq
{
  "data": [
    {
      "name": "Los Angeles, LOS ANGELES, CA, USA",
      "country_code": "US",
      "location_type": "CITIES",
      "targeting_value": "3b77caf94bfc81fe",
      "targeting_type": "LOCATION"
    },
    ...
  ],
  "request": {
    "params": {
      "location_type": "CITIES",
      "q": "los angeles"
    }
  },
  "next_cursor": null
}

I can do the same for metros. Notice that the ID, in this case, is e4315a8602024dcb.

$ twurl -H ads-api.twitter.com "/5/targeting_criteria/locations?location_type=METROS&q=los angeles"
{
  "data": [
    {
      "name": "LOS ANGELES",
      "country_code": "US",
      "location_type": "METROS",
      "targeting_value": "e4315a8602024dcb",
      "targeting_type": "LOCATION"
    },
    ...
  ],
  "request": {
    "params": {
      "location_type": "METROS",
      "q": "los angeles"
    }
  },
  "next_cursor": null
}

Please let us know if that’s what you’re looking for.

Thanks!