Deeplinks are helpful for passing the context of the download to your mobile application.
When marketing your app, there is always context around that marketing. For example, if you show a download button on your blog, the blog gives context to get the user to install your app. Let's say that you built an e-commerce app that sells shoes. If there is a specific shoe that you're writing about in your blog, if the user clicks and downloads the app, ideally you show them the shoe they clicked on after the download. (Read here)
Make sure you already added Facebook Protocol in the App setting.
Go to Apps tab and select your app.
Click "+ NEW CALLBACK".
Create BOTH Facebook Install and Facebook Deferred Deeplink callback from templates.
facebook_app_idfor your app, and hit "SAVE CALLBACK" for both Facebook Install and Facebook Deferred Deeplink callbacks.
After you create a campaign in Tenjin, you will automatically see a deeplink.
Go to your Facebook Ad account and create your ad set in Facebook's dashboard. Name the ad set with the same name as the Tenjin campaign name. Per the below it would say "iOS-US-male-Wordsearch @hB1zqEeYDeKgDPF6qvkq7O". You can name Facebook campaign name as you want.
Create an Ad for the Facebook ad set you created and in the "Deep Link" field insert the Tenjin generated DeepLink you generated in step 6. You can use the same Deep Link url for each ads under the same ad set.
For non-Facebook campaigns, you can take the tracking URL generated and add a
deeplink_url parameter and value to the end of the tracking URL. On install, the Tenjin SDK will be able to pull this context directly from Tenjin's servers.
Let's say that your Tenjin generated tracking link for your campaign looks like this:
To pass deeplink context and information to your app's install you can add a value to the
deeplink_url parameter so it looks like this:
The Tenjin SDK will pass the
myschema://shoe1 information to your app so you can handle the user on the app in a specific way. In this case you might redirect them to the content with
shoe1 in the app.
Also, Here's an example on how you can test if this is working properly before deploying your app in production.