In the most recent releases of JFBConnect, we've updated how the {SCOpenGraph ..} tag works so that you can add completely custom data, like Applink data. We haven't tested Applinks directly, but the intent is to allow us to move in that direction when/if we decide to implement it.
If your app is already Applink ready, and all you need is to add the tags to your page, there's a few quick things you could test. The main idea of applink data is shown below (I'm sure you're aware of it, but posting it for reference:
developers.facebook.com/docs/applinks/add-to-content
The tags for each page look like:
<meta property="al:ios:url" content="example://applinks" />
<meta property="al:ios:app_store_id" content="12345" />
<meta property="al:ios:app_name" content="Example App" />
<meta property="og:title" content="example page title" />
<meta property="og:type" content="website" />To add those to each page of your site, you could use the following syntax (updating for your site, of course):
{SCOpengraph al:ios:url=example://applinks}
{SCOpengraph al:ios:app_store_id=12345}
{SCOpengraph al:ios:app_name=Example App}The title and type should automatically be set by JFBConnect. In addition to the above, you *should* be able to set the above tags using the default setting in the Open Graph area. To do so, add the tags like below to that configuration option:
al:ios:url=example://applinks
al:ios:app_store_id=12345
al:ios:app_name=Example App
Those will be set on all pages automatically. Then, you can override each value with the {SCOpenGraph ..} tags on each page if you want to tweak them for some pages.
We have *no* method for reading or reacting to the intent blob that would be sent by Facebook. It sounds like you don't really need that though, so hopefully the above gets you going.
Please test and let us know how it goes. We'd love to hear your experience.
Thanks,
Alex