After you created your card, you must add it to a Tweet in order to use it in a campaign. They are not complete ad units on their own.
What should I set for my primary app store territory?
This is the primary territory in which your app is available. We use this information to verify your App ID.
If you're not sure what the primary territory for your app is, try selecting the United States.
If you're outside of the US, set your territory to wherever your app was first available in. This will not limit where you can target your ad. App IDs can be the same for multiple countries as long as that version of your app is available in that country.
What is a deep link?
A deep link scheme is analogous to a domain for a website, except it allows users to launch an app and serves as the base scheme for full deep links (see below). For example, try typing twitter:// in your mobile web browser and hitting “Go.” If you have the Twitter app installed, it will open the app on your phone.
In the context of an App Card on iOS, adding deep link schemes to your card configuration allows Twitter to recognize if an app is installed and enable users to directly open the app from Twitter. Of course, if the app is not installed, the App Card will send the user to the App Store, where they can proceed to download the app.
A deep link scheme is also required to enable "Install Notifications" on iOS. Install notifications are prompts that occur on Twitter once an app is fully downloaded and are designed to drive activation of your app.
To get your app's deep link scheme:
In order for your app to respond to open URL requests correctly, you’ll need to add a URL scheme into your app’s.plist file. Common patterns for naming this scheme include reverse-DNS, or simply myappname://.
Look for the URL types section in your app’s .plist file. If it doesn’t exist, you can add it yourself. If you haven’t already edited URL types, it should be an array with a single item, a dictionary with the key “URL Identifier”. Click the + button associated with the dictionary to add a “URL Schemes” section, which is another array, and add your scheme to this array. You can add as many custom schemes as you like. More information can be found here.
In your app delegate, you can add logic to the application:openURL:sourceApplication:annotation:method to take in the incoming URL (the one you specified in the card) and parse it within your app.
Deep-link information is passed to your app as part of the intent data. You can add an intent filter to the relevant receiving activities in your app. The intent filter might look something like this:
<action android:name=”android.intent.action.VIEW” />
<category android:name=”android.intent.category.DEFAULT” />
<category android:name=”android.intent.category.BROWSABLE” />
<!— Accepts URIs that begin with “example://action” —>
A more complete explanation can be found in Google’s developer docs.
What are the specs for App Cards?
We offer 4 types of App Cards:
- 1:1 Image App Card
- 1.91:1 Image App Card
- 16:9 Video App Card
- 1:1 Video App Card
To see specific specs for each, read our specifications page.
What are the creative best practices for App Cards?
Image App Card
- Use vibrant colors to make the image stand out
- Don't cram too much into a small space
- Include a preview of what someone can expect in your app
- Don't use overly branded imagery with just company logos
- Include an app store and play store logo if space permits
Video App Card
- Include visual cues and don't rely on audio
- Include a card in the beginning and end of the video that shows the app or play store logos and a visual CTA to download your app
- Make it clear that the video revolves around an app
- Don't re-purpose branded video, make sure it's app-focused
- Show the interface/usability/what someone what to expect within the app
- Keep the video between 6-15 seconds
For more optimization tips and creative suggestions, check out our app installs or app re-engagements optimization page.