Export Experience Fragments to Adobe Target with AEM 6.3

Recently I have gone through one use case of XF with adobe target. The problem statement was I was having one component which is having three variations. And I want to show different variations of the component to different audience using adobe Target.

So when I start implementing, I came to know that one way to achieve this is to create an XF and make three variations of that and Export it to Adobe Target.

So This blog only talks about how to Export the Experience Fragment to adobe target.

Prerequisites:
1. AEM needs to be successfully connected to “Adobe Target”.
2. In the cloud configurations of XF (in page properties), need to configure adobe target.

AEM 6.4 there is already a button available in the XF Console and it will directly publish the XF to target. But My project is using AEM 6.3.2.2 Version, I was not able to find the option of "Export to Target". But when I upgraded my system to AEM 6.3.3 then I got the option. But the client was not always ready about this upgrade so how can we do it with minimal things done on production.

While debugging this problem, I have gone through few documents that says different things and really a bit mislead me.

1. One document says that the prerequisite for this option need to be “Adobe Experience Manager 6.3 SP2 (or later)”.
2. Someone also face the same issue and raise it to adobe forum then they ask to update the instance (AEM 6.3.2) with one pack “cq-6.3.0-featurepack-24640-1.2.zip” and in the forum they mentioned also that “Open a daycare ticket to get access to it. It's not yet available at Adobe Package share cloud”.
3. Other document says that “This functionality requires the application of AEM 6.3 Service Pack 3 (6.3.3.0).

Now the actual things which I figured out are:
1. AEM 6.3.2.2 don’t support XF "Export to Adobe Target" option.
2.“cq-6.3.0-featurepack-24640-1.2.zip” package is a very small bug fix package and can solve the problem but it is available in packageshare. No need to raise a ticket to adobe.
3. AEM 6.3.3+ versions supports the option but you can make it available in AEM 6.3.2 with a very small(2 MB) Bugfix package but your client doesn't want to go for the big upgrade.