@AshwiniBh ,Access to a report depends on its selection type, display conditions, and access authorizations.You can go through the following doc for reference-https://experienceleague.adobe.com/docs/campaign-classic/using/reporting/creating-new-reports/configuring-access-to-the-report.html?lang=en

@MYSTERIOUSMAN ,As mentioned over thread,  we do not have a Facebook connection with AJO standalone (at present).This requires a RTCDP license.You can use this destination for audience targeting across Facebook’s family of apps that are supported by Custom Audiences, including Facebook, Instagram, A...

@MYSTERIOUSMAN , This requires a RTCDP license.Without that, it's not possible to send data to FB destination for AJO standalone.

@MYSTERIOUSMAN , We do not have a Facebook connection with AJO- do you mean the RTCDP destination?You would need a RTCDP license for FB connection.

@MatteMa ,Adobe Journey Optimizer is an agile and scalable application for creating and delivering personalized, connected, and timely customer experiences across any app, device, or channel.Customer can go through - https://experienceleague.adobe.com/docs/journey-optimizer/using/get-started/get-sta...

Please find the updated doc link -https://experienceleague.adobe.com/docs/campaign/campaign-v8/connect/ac-tw.html?lang=en&https://experienceleague.adobe.com/docs/campaign/campaign-v8/campaigns/send/twitter.html?lang=en 

@DhanushGM1 ,Documentation can be found @https://experienceleague.adobe.com/docs/campaign/campaign-v8/connect/ac-tw.html?lang=en&https://experienceleague.adobe.com/docs/campaign/campaign-v8/campaigns/send/twitter.html?lang=en Regarding the failure of the workflow - "Synchronization of Twitter Accoun...

@MYSTERIOUSMAN ,You can use Journey Orchestration (profile orchestration) with the updated profile node with flag segments that are pushed to the trade desk, Facebook, google. With this, you end up having lot of useless (operative) segments in their instance for each use case. It works, but not real...

@VandithaPa ,Sending proofs from workflows can be tricky. To do this, you can use Seed addresses. If seed addresses aren't used, issues with generation of targetData (which is generated during workflow execution, and not when trying to send a proof from a delivery workflow activity) can arise. 

@Divya104 ,Essentially the user causes the error when trying to execute an INSERT or UPDATE statement that has generated a duplicate value in a restricted field. The error can commonly be found when a program attempts to insert a duplicate row in a table.You can try to add a deduplication activity b...