A great advantage of Ambassify's API-share* feature is that you can seamlessly connect your social network accounts to your Ambassify account. This lets you directly share or interact with campaigns without leaving our interface.
*for more information about sharing content via Ambassify, please read this article
In this article, we'll look closer at the data permissions that X requires when you want to connect your X account to share content via Ambassify (or any other third-party application). You will see this message:
These are the default permissions that X requires. This does not mean that Ambassify uses these permissions exactly as they are described, nor do we influence how X formulates its permissions. Because these permissions might feel intrusive to users, we will explain how Ambassify uses your X account.
Creating Posts
At its core, Ambassify needs access to your account to post posts on your behalf. You remain the owner of your account at all times, and only you can decide when a post should be created. The main difference is that instead of you creating a post on X, you use Ambassify as a third-party tool to create the post for you. This happens when you share a piece of content on X via a Social Share campaign, image share campaign or video share campaign.
When you select X as a channel and click the Share now button (or you use the scheduling tool), Ambassify converts this action by creating and posting it in a post. This happens seamlessly via the API connection, so you don't have to leave the Ambassify interface.
Reporting
To measure the impact of the posts created via Ambassify, we track their potential reach and the number of clicks. Reach is calculated based on the number of accounts that follow your X account. The higher this number, the higher your potential reach. Ambassify only tracks the number of accounts; we do not see who these accounts are. In other words, this is anonymized. The same goes for the clicks that your posts receive. Ambassify measures the number of clicks but doesn't collect any data about the X accounts that are responsible for those clicks.
Permissions that are not applicable
Most permissions listed in the X pop-up are not applicable (N/A). These are standard permissions formulated by X but not used by Ambassify. In order to get permission to post, the other permissions need to be accepted as well. To find out more about these permissions, we refer to X's developer platform where this is described as well.
Permission | Comment |
See posts from your timeline (including protected posts) as well as your Lists and collections. | N/A |
See your X profile and account settings. | Ambassify can see your profile and account settings and only reads out the number of followers you have to provide the above-mentioned reporting metrics. |
See accounts you follow, mute and block. | N/A |
Follow and unfollow accounts for you. | N/A |
Update your profile and account settings. | N/A |
Post and delete posts for you, and engage with posts posted by others (like, unlike, reply to a post, repost, etc.) for you. | Ambassify only posts posts for you, as explained above. This only happens at the user's (i.e., X account owner's) command. We do not delete posts. |
Create, manage, and delete Lists and collections for you. | N/A |
Mute, block, and report accounts for you. | N/A |