adobedocs / core-services.en Goto Github PK

License: MIT License

core-services.en's Introduction

Contribute article

We welcome contributions from our community as well as from Adobe employees from outside the documentation teams.

Adobe Open Source Code of Conduct

This project has adopted the Adobe Open Source Code of Conduct or the .NET Foundation Code of Conduct. For more information, see the Contributing article.

About your contributions to Adobe content

See the Adobe Docs Contributor Guide.

How you contribute depends on who you are and the sort of changes you'd like to contribute:

Minor changes

If you are contributing minor updates out of the goodness of your heart, visit the article and select the Edit link in the article that goes to the GitHub source for the article. Then, just use the GitHub UI to make your updates. See the general Adobe Docs contributor guide for more information.

Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the Adobe terms of use.

Major changes or new articles from community members

If you're part of the Adobe community and you want to create a new article or submit major changes, please use the Issues tab in the Git repository to submit an issue to start a conversation with the documentation team. Once you've agreed to a plan, you can work with an employee to help bring that new content in through a combination of work in the public and private repositories.

Major changes from Adobe Employees

If you are a technical writer, program manager, or developer from the product team for an [!UICONTROL Adobe Experience Cloud] solution and it's your job to contribute to or author technical articles, you should use the private repository at https://git.corp.adobe.com/AdobeDocs.

Tools and setup

Community contributors can use the GitHub UI for basic editing or fork the repo to make major contributions.

See the Adobe Docs Contributor Guide for details.

How to use markdown to format your topic

All the articles in this repository use GitHub flavored markdown. If you are not familiar with markdown, see:

Labels

In the public repository, automated labels are assigned to pull requests to help us manage the pull request workflow and to help let you know what's going on with your pull request:

Change sent to author: The author has been notified of the pending pull request.
ready-to-merge: Ready for review by our pull request review team.

core-services.en's People

Contributors

Watchers

Forkers

micapete yuhui mtalbot29 xinzhan cxux harnonlabs manbeneat

core-services.en's Issues

Outdated instructions for customers

Issue in ./help/interface/organizations.md

The instructions provided in this workflow are super outdated, the dashboard looks different now.

I was trying to send the instructions to the customer so they can connect their Adobe ID with their products but it did not work.

Any help and updates will be highly appreciated.

The article does not contain any useful information

Issue in ./help/interface/t-publish-audience-segment.md

I was redirected to this page from https://experienceleague.adobe.com/docs/analytics/components/segmentation/segmentation-workflow/seg-publish.html?lang=en by clicking "enabled for the Experience Cloud". It redirects to the page with content:

Publish an Analytics audience segment to Experience Cloud and to Adobe Target for audience marketing activities.

Refer to the Adobe Analytics documentation for instructions.

The documentation brings the user back to the initial page.

And round round round we go :)

Can we include instructions how to check if the Report Suite is enabled for the Experience Cloud:

Asset Sharing with Experience Manager Link on the page is non functional

Issue in ./help/interface/experience-cloud-assets.md

The anchor link on the page with name Asset Sharing with Experience Manager is non functional. It seems like we are unable to integrate with Experience Manager

Information is missing

Issue in ./help/interface/cookies-advertising-cloud.md

There is a lot of question about the security of the website. Could you please add more information wheather the cookie can have "httpOnly" and "secure" attributes checked?

Thanks,
Darpan

Please Revert SelectMap to ClickMap

Issue in ./help/interface/cookies-analytics.md

ClickMap has been replaced with SelectMap by the commit below.
93f5eda

Could you kindly revert it back to ClickMap?

Provisioning link is wrong

Issue in ./help/interface/audience-library.md

On this page: https://experienceleague.adobe.com/docs/core-services/interface/services/audiences/audience-library.html?lang=en#

There is a link to provisioning in this text:

Cannot find Audiences?	Ensure that you are provisioned. See Getting started - enable your applications for core services.Go here to request access to Profiles and Audiences (integrations provisioning form).

Cannot find Audiences? Ensure that you are provisioned. See Getting started - enable your applications for core services.
Go here to request access to Profiles and Audiences (integrations provisioning form).

That link (to allegiancetech) is dead. Use this one instead: https://survey.adobe.com/jfe/form/SV_ekBHTLSoP5Zki2y

Need to delineate between 1st and 3rd party cookies

Issue in ./help/interface/cookies-target.md

Some of the content on this page is confusing. For example, cookies don't have a "server domain" setting, they just have a domain setting. If it's a 3rd party cookie set by Target, then it will have a domain setting which includes "tt.omtrdc.net". If it's a first party cookie, it will be set on the customers domain.

I think country codes like .co.uk have had out-of-the-box support for many years.

The page still refers to "campaigns" instead of "activities". It should probably be revamped.

Typo

Issue in ./help/interface/experience-cloud.md

In the Access Experience Cloud applications section:

To access Experience Cloud applications and services provisioned for you within your organization, go to the application selector