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)

Facebook deferred deeplink

Facebook deferred deeplink is not available for Facebook iOS 14 campaigns. For iOS 14 campaigns, please see this page.

  1. Make sure you've already added Facebook Protocol in the App setting.

  2. Go to CONFIGURE -> Apps tab and select your app.

  3. Click + New Callback.

  4. Create BOTH Facebook Install and Facebook Deferred Deeplink callbacks from templates.


  5. Enter facebook_app_id for your app, and hit SAVE CALLBACK for both Facebook Install and Facebook Deferred Deeplink callbacks.


  6. After you create a campaign in Tenjin, you will automatically see deeplink. undefined

  7. 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. As in the below example, it would say "iOS-US-male-Wordsearch @hB1zqEeYDeKgDPF6qvkq7O". You can name a Facebook campaign as you want.


  8. 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 ad under the same ad set.


  9. To redirect users to a specific place in your app, you can append any parameter and value to the deeplink generated in step 6 above.

Original Facebook deferred deeplink:


Facebook deferred deeplink with a custom parameter/key:


Once your users install the app from your campaign, Tenjin will pass the entire deeplink url with the custom parameter to the Tenjin SDK. The customized deeplink data can be fetched directly from the Tenjin SDK to handle any types of redirects within your app, by following these instructions (iOS, Android, and Unity)


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.

You would need to implement the logic to handle the redirect by following these instructions (iOS, Android, and Unity)

Also, Here's an example on how you can test if this is working properly before deploying your app in production.

results matching ""

    No results matching ""