Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
============
This archive was generated at the request of the following user:
- @username at the time the archive was generated: BryanStreamR
- Account ID: 1128398077457518594
Each file contains detailed information about that category of data. To see this
information, simply double click on one of the JSON files. Note that some
information, such as the media shared via Direct Messages, is included in a folder
instead of a JSON file. Separately, also note that some files may not contain any
information if your account is not associated with any of the data they cover.
The information contained in this archive reflects the state of the account at the
time when the archive was created.
FILE DESCRIPTIONS
=================
account.js
- phoneNumber: Phone number currently associated with the account if a phone number
has been provided.
- email: Email address currently associated with the account if an email address
has been provided.
- createdVia: Client application used when the account was created. For example:
“web” if the account was created from a browser.
- username: The account’s current @username. Note that the @username may change but
the account ID will remain the same for the lifetime of the account.
- accountId: Unique identifier for the account.
- createdAt: Date and time when the account was created.
- accountDisplayName: The account’s name as displayed on the profile.
----------------------
account-creation-ip.js
- accountId: Unique identifier for the account.
- userCreationIp: IP address at account creation.
----------------------
account-suspension.js
- timeStamp: Date and time of a suspension action.
- action: Action taken regarding account suspension. Accounts are unsuspended by
default. This file will be empty unless the account was suspended at some point.
----------------------
account-timezone.js
- accountId: Unique identifier for the account.
- timeZone: Timezone currently associated with the account.
----------------------
ad-engagements.js
- ad: Promoted Tweets the account has engaged with and any associated metadata.
- deviceInfo: Information about the device where the engagement occurred such as
its ID and operating system.
- displayLocation: Location where the ad was engaged with on Twitter.
- promotedTweetInfo: Information about the associated tweet such as unique
identifier, text, URLs and media when applicable.
- advertiserInfo: Advertiser name and screen name.
- matchedTargetingCriteria: Targeting criteria that were used to run the campaign.
- impressionTime: Date and time when the ad was viewed.
- engagementAttributes: Type of engagement as well as date and time when it
occurred.
----------------------
ad-impressions.js
- ad: Promoted Tweets the account has viewed and any associated metadata.
- deviceInfo: Information about the device where the impression was viewed such as
its ID and operating system.
- displayLocation: Location where the ad was viewed on Twitter.
- promotedTweetInfo: Information about the associated tweet such as unique
identifier, text, URLs and media when applicable.
- advertiserInfo: Advertiser name and screen name.
- matchedTargetingCriteria: Targeting criteria that were used to run the campaign.
- impressionTime: Date and time when the ad was viewed.
----------------------
ad-mobile-conversions-attributed.js
- ad: Mobile application events associated with the account in the last 90 days
which are attributable to a Promoted Tweet engagement on Twitter.
- attributedConversionType: Type of activity specifically associated with the
event.
- mobilePlatform: Platform on which the event happened. For example: iOS or
Android.
- conversionEvent: Information about the event itself such as installing or signing
up.
- applicationName: Name of the application in which the event occurred.
- conversionValue: Value associated with the event.
- conversionTime: Date and time of the event.
- additionalParameters: Other optional parameters associated with the event such as
a currency or product category.
----------------------
ad-mobile-conversions-unattributed.js
- ad: Mobile application events associated with the account in the last 10 days
which may become attributable to a Promoted Tweet engagement on Twitter in the
future.
- mobilePlatform: Platform on which the event happened. For example: iOS or
Android.
- conversionEvent: Information about the event itself such as installing or signing
up.
- applicationName: Name of the application in which the event occurred.
- conversionValue: Value associated with the event.
- conversionTime: Date and time of the event.
- additionalParameters: Other optional parameters associated with the event such as
a currency.
----------------------
ad-online-conversions-attributed.js
- ad: Web events associated with the account in the last 90 days which are
attributable to a Promoted Tweet engagement on Twitter.
- attributedConversionType: Type of activity specifically associated with the
event.
- eventType: Information about the event itself such as viewing a page.
- conversionPlatform: Platform on which the event happened. For example: desktop.
- advertiserInfo: Advertiser name and screen name.
- conversionValue: Value associated with the event.
- conversionTime: Date and time of the event.
- additionalParameters: Other optional parameters associated with the event such as
a currency or product category.
----------------------
ad-online-conversions-unattributed.js
- ad: Web events associated with the account in the last 90 days which may become
attributable to a Promoted Tweet engagement on Twitter in the future.
- eventType: Information about the event itself such as viewing a page.
- conversionPlatform: Platform on which the event happened. For example: desktop.
- conversionUrl: URL of the website on which the event occurred.
- advertiserInfo: Advertiser name and screen name.
- conversionValue: Value associated with the event.
- conversionTime: Date and time of the event.
- additionalParameters: Other optional parameters associated with the event such as
a currency or product category.
----------------------
ageinfo.js
- ageInfo: Date of birth provided to Twitter and corresponding current age.
----------------------
block.js
- accountId: Unique identifiers of accounts currently blocked by the account.
- userLink: Link to information about the blocked users’ profiles if accessible to
the account. For example, this information might not be accessible if blocked
profiles are protected or deactivated.
----------------------
connected-application.js
- name: Name of the application.
- description: Brief description of the application as provided by the
organization.
- approvedAt: Date and time when the account authorized the application.
- permissions: List of permissions granted to the connected application by the
Twitter account. For example: read or write.
- id: Unique identifier for the application.
----------------------
contact.js
- id: Unique identifiers for the contacts imported to the account.
- emails: Emails of the contacts imported to the account.
- phoneNumbers: Phone numbers of the contacts imported to the account.
----------------------
device-token.js
- token: Token associated with a mobile device or web browser that was used to sign
up or log in to this account through twitter.com or one of the other Twitter owned
or operated apps within the last 18 months.
- lastSeenAt: Date and time of most recent use. Please note that there may be
instances where older tokens do show this information.
- clientApplicationId: Unique identifier of the application associated with the
token. Please note that there may be instances where older tokens do not have a
unique identifier associated with them.
- clientApplicationName: Name of the application associated with the token. Please
note that there may be instances where older tokens do not have an application name
associated with them.
- createdAt: Data and time of the creation of the token.
----------------------
direct-message.js
- recipientId: Unique identifier for the account who received the Direct Message.
- text: Text content of the Direct Message.
- mediaUrls: Link included in the Direct Message if applicable.
- senderId: Unique identifier for the account who sent the Direct Message.
- id: Unique identifier for a specific Direct Message within the conversation.
- createdAt: Date and time the Direct Message was sent.
----------------------
direct-message-group.js
- conversationId: Unique identifier for the Direct Message group conversation. Each
conversation has a unique randomly generated conversation ID. Within a
conversation, the Direct Messages are ordered in reverse chronological order,
meaning that the latest Direct Message will be at the top of the list.
- text: Text content of the Direct Message.
- mediaUrls: Link included in the Direct Message if applicable.
- senderId: Unique identifier for the account who sent the Direct Message.
- id: Unique identifier for a specific Direct Message within the conversation.
- createdAt: Day and time of when the Direct Message was sent.
- joinConversation: Metadata about when the account joined the conversation. This
field might not be available due to deletions initiated by the account or other
participants.
- participantsJoin: Metadata about when another participant joined the
conversation. This field might not be available due to deletions initiated by the
account or other participants.
- participantsLeave: Metadata about when another participant left the conversation.
This field might not be available due to deletions initiated by the account or
other participants.
- conversationNameUpdate: Metadata about when a participant changed the name of the
conversation including it name.
----------------------
direct-message-group-headers.js
- conversationId: Unique identifier for the Direct Message group conversation. Each
conversation has a unique randomly generated conversation ID. Within a
conversation, the Direct Messages are ordered in reverse chronological order,
meaning that the latest Direct Message will be at the top of the list.
- id: Unique identifier for a specific Direct Message within the conversation.
- senderId: Unique identifier for the account who sent the Direct Message.
- createdAt: Date and time the Direct Message was sent.
- joinConversation: Metadata about when the account joined the conversation.
- participantsJoin: Metadata about when another participant joined the
conversation. This data is only available if the account was in the conversation
when another participant joined.
- participantsLeave: Metadata about when another participant left the conversation.
This data is only available if the account was in the conversation when another
participant left.
- conversationNameUpdate: Metadata about when a participant changed the name of the
conversation.
----------------------
direct_message_group_media
Folder of images, videos and gifs shared in the account’s Direct Message group
conversations. Note:this folder does not include media hosted on other platforms
but linked on Twitter (for example, YouTube videos).
If Group Direct Messages (Group DMs) have been produced and there is associated
media, you can match the media to the Group DM data file. The filename for each
media file in the direct_message_group_media folder contains a numerical ID that
corresponds to a Group DM in the direct-message-group file. By searching the
direct-message-group file for the numeric portion of the filename of the media, you
can find the corresponding Group DM.
If Direct Messages (DMs) have been produced and there is associated media, you can
match the media to the DM data file. The filename for each media file in the
direct_message_media folder contains a numerical ID that corresponds to a DM in the
direct-message file. By searching the direct-message file for the numeric portion
of the filename of the media, you can find the corresponding DM.
If Tweets have been produced and there is associated media, you can match the media
to the Tweet data file. The filename for each media file in the tweet_media folder
contains a numerical ID that corresponds to a Tweet in the Tweet file. By searching
the Tweet file for the numeric portion of the filename of the media, you can find
the corresponding Tweet.
If your production includes a Tweet file and did not include a tweet_media folder,
this is because there was no media associated with the Tweet file.
----------------------
verified.js
- accountId: Unique identifier for the account.
- verified: Indicates whether the account is verified.
----------------------