#1

Is there a limit on a number of ad accounts, a handle can access?
Also, what are the limits on the maximum number of entity ids for the various entities ACCOUNT, FUNDING_INSTRUMENT, CAMPAIGN, LINE_ITEM, PROMOTED_TWEET, MEDIA_CREATIVE, ORGANIC_TWEET
Also, I tried to fetch Line_Item entity with the AGE segmentation type. In the response, I am getting a list with multiple segment_type and segment_value parameters. Ex. segment_name => 30-39, segment_value = 11 and in the same list, segment_name => 20-49, segment_value => z
What does this mean, and why the segment_value is number and character both?
Is there a way to find out all the possible segment_value data types, or documentation for the same?
Can someone please respond to the queries?
Thanks

#2

Can someone please respond

#3

I haven’t encountered any limits but strongly recommend reviewing the documentation on obtaining access to an ads account and getting an advertiser’s OAuth token to make requests against their account.

Also, what are the limits on the maximum number of entity ids for the various entities ACCOUNT, FUNDING_INSTRUMENT, CAMPAIGN, LINE_ITEM, PROMOTED_TWEET, MEDIA_CREATIVE, ORGANIC_TWEET

The main limits for entities are discussed in the POST line items endpoint that states: “There is a limit of 100 line items per campaign and 8,000 active line items across all campaigns.”

Also, I tried to fetch Line_Item entity with the AGE segmentation type. In the response, I am getting a list with multiple segment_type and segment_value parameters. Ex. segment_name => 30-39, segment_value = 11 and in the same list, segment_name => 20-49, segment_value => z

Many fields used by the Ads API are Base36 alpha-numeric strings. Let us know if you have any additional questions.

#4

Thanks for the reply!!!
So, segment_value 11 and z both are base 36 encoded?
Is there a way to find out, which segment/metrics/attributes are returned in ads api as base-36 encoded and which are not?

#5

@talha_iiita Generally, values returned via the Ads API will be in the base-36 format, except for Tweet IDs and job IDs retrieved via the async stats endpoints.

#6

Thanks a lot!!
1 more question
In the documentation, it’s written
“Spend metrics are generally final within 3 days of the event. However, processing billing data takes up to 14 days from the date of the event (for spam filtering, for example).”
What are the spend metrics and billing metrics? I can see billing metric groups but which metric group does spend metrics belong to?

#7

I’d recommend using the “Help?” button at the top of ads.twitter.com for those types of questions.