Click the Cloud Services tab, then from the Cloud Service Configuration drop-down list, select Adobe Target.
But we of course do not have a direct connection between Adobe Target and AEM because we are using DTM to make the bridge.
There is also the following statement:
"As a first-look feature, you must be provisioned with the Experience Fragments functionality within Target. In addition, you must be using AEM 6.3 with the appropriate feature pack. Your account representative can help ensure that you meet the requirements to use this feature if your company is provisioned with this feature."
Am I really unsure if we event have those privileges, how can I make sure?
Also, you can see that in the opt-in windows target connection fields are disabled, what is the reasoning behind this? Is it because it was used to connect to the classic target? Is the only way to make this exporting of fragments work to create a direct connection with the new target, if so where can I do that?
Some more information for you, Adobe Target classic has been decommissioned, so will AEM-Target integration would work now OR What happens to existing activities created with the AEM 6.1-6.3 / Target integration after the end-of-life date for the Target Classic user interface?
While the Adobe Experience Manager (AEM) 6.1-6.3 integration with Target does use a Target Classic API user behind the scenes, this is managed separately from the Target UI transition and will not be affected by the end-of-life plans. If you would like to set up an new integration with AEM and Target you will need to send a request to Adobe’s provisioning team, who can set up this integration for you.
The Marketing Cloud Help this an apt way to personalize XF with XF from target interface via VEC. But for this, you requires Feature Pack. Let me get some more information from product management about its public accessibility.