Git Product home page Git Product logo

audience-manager.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 click 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'll need to 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 Adobe Experience Cloud solution and it's your job to contribute to or author technical articles, you should use the private repository 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.

audience-manager.en's People

Contributors

alvawb avatar bbringhu avatar blakefrei avatar gipaul avatar jeftaylor79 avatar jryanhamilton avatar vfalon avatar vgiurgiu avatar vladfalon avatar yanlicao avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

audience-manager.en's Issues

"destination" word repeated twice

Issue in ./help/using/features/data-export-controls.md
Under Overview, the 2nd bullet point "Sending any data to a destination destination has a data export label that is blocked by a data export control on any of:" here the word 'destination' is repeated twice.
image

Facebook WCA integration no longer working

https://docs.adobe.com/help/en/audience-manager/user-guide/implementation-integration-guides/integrating-third-party/facebook-wca-integration.html

I believe this documentation page should be removed or not made public, as Facebook no longer allows this integration. The following comment was made by a FB rep

"Adobe is onboarding cookie-based audiences to our platform by passing segment_id as a custom parameter in the Facebook pixel. We also believe this DMP is building cross-publisher audiences by firing a single Facebook pixel across multiple websites. Both of these approaches violate our Facebook Business Tools Terms. We have contacted the DMP regarding this violation. The previous form of the ‘hack’ has been completely removed. At this time, there are no plans for a resolution on the roadmap."

Code Implementation section

Issue in ./help/using/integration/implement-audience-manager.md

The section of this page for "Code Implementation" has no instructions as to how to implement the code or links to resources showing how to do so. Can these be added?

Incorrect information on "Match Rate Considerations"

Issue in help/using/features/destinations/twitter-tailored-audiences.md

Under "Match Rates Considerations"

  • When using Twitter Tailored Audiences, the Segment Addressable Audience and Segment Match Rate metrics from the destination page will not display any values. This is normal behavior, since audience matching along with the match rates for this destination are handled and hosted by Twitter, not Adobe.

This no longer applies, as destinations exporting out UUIDs should now show 100% in match rates.
See JIRA AAM-51615 for this change.

Specifications on the use cases

Issue in ./help/using/features/audience-marketplace/marketplace-data-buyers/marketplace-data-buyers.md

It's not an issue but a suggestion.
It would be worth to add some specification when the customer is actually charged for cost in each use case.
For example, in the Modeling use case, he is charged when he run a model or when he activate the result of the model?

Frequency ... including users who have not realized the trait (?)

Issue in help/using/features/segments/recency-and-frequency.md

I feel there is an issue with the wording in the Frequency Capping Examples (see below).

The expression frequency([1000T]) <= 5 includes all users that have realized the trait with the ID "1000" a maximum of five times, including users who have not realized the trait.

I understand the fact we are using Less than or equal which includes zero but to me and some customers I've had, if the trait is gathering population, I assume the trait has been realised 1 or up to 5 times so the assumption is that a trait needs to be realised to be counted. The documentation statement seems counter-intuitive and leads to confusion.

My 2 cents, hopefully we can improve this somehow - Thanks

Insufficient specification

Issue in help/using/integration/receiving-audience-data/real-time-outbound-transfers/real-time-outbound-transfers.md

There is no information about how the request should look like. Only the response is specified.

Extra line added

Issue in ./help/using/features/data-export-controls.md
There is a line added here which does not fit. PFA screenshot.

image

Confusing warning on FTP transfers

Issue in help/using/integration/sending-audience-data/batch-data-transfer-explained/inbound-ftp-filenames.md

The warning regarding the FTP inbound not being supported is somewhat confusing / concerning to clients. Currently we still process files if they are sent to our inbound FTP endpoint (unless this changed recently??).

Could this be updated to reflect that existing FTP configurations will still continue to work for the time being?

d_ and h_ keys are not found in the Signals Search Feature

Issue in help/using/features/traits/trait-variable-prefixes.md

I think it is important to highlight that the d_ and h_ keys are not returned in the Signals feature. This means that if a customer is attempting to locate them in the Search function of the Signals feature, they will not successfully find them, however, if they create a trait expression that uses these keys the associated data will be captured in the AAM trait.

Use Case 2 Correction

Issue in help/using/faq/faq-inbound-data-ingestion.md

Hi there,

For cross device data sources, the data is stored for a later time if the user did not login during the time the crm files are processed. In use case 2, it indicates the opposite which is related to a cookie data source - can we confirm this and make the correction on the site? It is confusing our clients and also worrying them.

Syntax example is maybe misleading

Issue in help/using/integration/sending-audience-data/batch-data-transfer-explained/id-sync-file-based.md

Hi guys,
In this doc, it has filename syntax that starts with: adobe_id_ [c2c_id_] ...
I guess I thought that when you have something in square brackets, it is optional, which in this case would be wrong, because then you could start a file with: adobe_id_c2c_id...
Instead, it will replace the first part if it is PBD, right? Anyway, just wanted you guys to think about this one more time. It might just be me that would be confused by this, and on the actual PBD doc pages you give great filename examples. It's just on this page that is not specific to PBD where it might be confusing. Let me know if you have any questions.
Thanks,
Doug Moore

segment Frequency Cap

Issue in help/using/features/segments/recency-and-frequency.md

At the frequency level, can we have clear comment explaining <= will also consider '0' as a frequency qualification criteria and will consider all the user? this is not clearly mentioned and ended up populating a lot of user population at the segment level.

Incorrect Hyperlinks

Issue in help/using/reporting/audience-optimization-reports/aor-publishers/import-dfp.md

the links via google and via cookie destination, the landing URLs are swapped

BAAAM Folder API - Include Sub-Folders

Issue in help/using/reference/bulk-management-tools/bulk-management-intro.md

Can you please update the BAAAM retrieve folder to get all the sub-folders in the folder as well. Right now if I put nothing or Root. I only get the root folders, not all the sub-folders in the root and their sub-folders down to 5 branches. That is the limit AAM currently has.

The previous version only went in 4 tiers, when the limit was 5. Meaning the fifth sub-folder branch never would show up in BAAAM. So At least in that version you could figure out the sub-folders.

Feeds are limited to a Single Data Source.

Issue in help/using/features/audience-marketplace/marketplace-data-providers/marketplace-create-manage-feeds.md

It should be better highlighted that a Feed is limited to a single data source, it cannot have multiple data sources within a single feed.

BAAAM Folder API - Include Sub-Folders

This is related to issue #20. The new version only goes one folder deep. What I am looking to do is when I choose the root folder it gives me a list of all the folders, all their nested folders, all the nested folder's folders, etc. Basically I want to get a complete folder structure.

Table Structure Not Correct

Issue in help/using/reference/ids-in-aam.md

Looks like the top table structure was corrupted on one of the recent updates

Update Language to Indicate that all Uploaded IDs are Case-sensitive

Issue in help/using/faq/faq-inbound-data-ingestion.md

The answer to the question, "Are the data file contents case-sensitive? How about the ID sync?" should include that ALL uploaded IDs are case-sensitive; not just UUID. For example CRM IDs.

-- Answer:
There are two basic components of a data file: A Unique User ID (UUID) and profile data, usually in the form of key-value pairs or codes. The UUID is case-sensitive. Generally, profile or key-value data is not case-sensitive.

Wrong links

Issue in help/using/integration/receiving-audience-data/receiving-audience-data-overview.md

Links are wrong.

Folder Traits are Not Supported for Use as a Conversion Trait

Issue in help/using/features/audience-lab/audience-lab-manage-test-groups.md

In Item #5 on the page, it discusses Conversion Traits. A bullet point should be added to indicate that using a Folder Trait as a Conversion Trait is not supported. It will result in 0 Aggregate and Trend reporting being displayed within the test.

Jira References:
AAM-38962
AAM-38961
AAM-38684

Links not working

Issue in help/using/overview/data-security-and-privacy/data-privacy-consent.md

Links to Experience Cloud Opt-in Service not working

Screenshot out of date for integration page

Issue in help/using/integration/integration-other-solutions/aam-target-integration.md

Hi,
The screenshot on the page above is out of date. A customer had issues confirming the integration because his page didn't look like the screenshot. Could you update it?

Thanks,
Jonathan

Confusing terminology

Issue in help/using/integration/sending-audience-data/batch-data-transfer-explained/inbound-ftp-filenames.md

In the documentation it refers to DPID which looks like it's referring to the single customer ID (PID). However Jess and others are saying that it actually refers to the Data Source ID. Can this be clarified? There's the same issue in the S3 page as well.

Thanks,
Jonathan

experience cloud help pages

Issue in help/using/features/destinations/create-url-destination.md

hi

i recommend you improve the navigation and content for these pages e.g. https://docs.adobe.com/content/help/en/audience-manager/user-guide/features/destinations/custom-destinations/create-url-destination.html

when i navigate from left menu frame to topics; i get content but the left menu goes back to the topic of the topics menu; so have to scroll down to return to the topic i was reading.

This is so frustrating and poor in terms of design; you need links to stay where people were exploring instead of going up and down to pages.

This applies for all help pages using https://docs.adobe.com/

Can you rectify this navigation problem?

Also your content on some pages is vague and not always accurate

ravinder basra
Capture

d_rd URL needs to be Encoded Properly

Issue in help/using/integration/media-data-integration/click-data-pixels.md

There is a concern that the 'd_rd' value is not properly encoded in the URL examples of:
https://client.demdex.net/event?d_event=click&d_creative=123&d_rd=http%3A%2F%2Fadobe.com%2Fcallback%3Fcreative%3D%25d_creative%25

https://client.demdex.net/event?d_event=click&d_creative=1235&d_src=203&d_campaign=4709&d_adgroup=3408&d_placement=1001&
d_rd=http%3A%2F%2Fadobe.com%2Fcallback%3Fcreative%3D%25d_creative%25%26campaign%3D%25d_campaign%25%26adgroup%3D%25
d_adgroup%25%26d_placement%3D%25placement%25%26src%3D%25d_src%25

While recently working with an adobe consultant, they above examples were leveraged and the URL redirection did not work as expected. The issue was that the d_rd was not properly encoded. It was discovered that the d_rd URL needed to be encoded a total of 2 times. For example:

d_rd=http%3A%2F%2Fadobe.com%2Fcallback%3Fcreative%3D%25d_creative%25%26campaign%3D%25d_campaign%25%26adgroup%3D%25
d_adgroup%25%26d_placement%3D%25placement%25%26src%3D%25d_src%25

becomes:

d_rd%3Dhttp%253A%252F%252Fadobe.com%252Fcallback%253Fcreative%253D%2525d_creative%2525%2526campaign%253D%2525d_campaign%2525%2526adgroup%253D%2525%0Ad_adgroup%2525%2526d_placement%253D%2525placement%2525%2526src%253D%2525d_src%2525

Using an online encoder, the URL needs to be run through the encoding process 2 times for the d_rd parameter to be properly encoded and have the redirect function properly.

This is difficult to describe over text, you can email me or ping me in Slack if more information is needed.

DTM vs Launch instructions

It looks like much of the documentation for Audience Manager was created pre-Launch.
Looking at this section here about integrating modules. It might be useful in the "Pre-Req." section to clarify that the instructions are meant for DTM implementations as versus Launch.

Segment Addressable Audience and Segment Match Rate Display 0 values

Issue in help/using/features/destinations/twitter-tailored-audiences.md

It should be noted that the Segment Addressable Audience and Segment Match Rate within the Destination view will not populate values. This is expected behavior because the match tables are not hosted by Adobe but rather are maintained at Twitter.

I spoke with Terry Chen via slack and his response was:
"Terry Chen reason we're not showing addressable audience and match rates for twitter is because the matching happens in twitter in this case"
"we don't host the match tables for twitter as we do with other destinations"

Wrong PMR Rule details?

Issue in help/using/features/destinations/people-based-destinations-workflow-authenticated.md

In this file, in Step 3 (PMR), #3, it says to use the "All Cross-Device Profiles", but i thought that was only for the Offline Only use case. Shouldn't this one say Current or Last, which is shown in the screenshot?

Thanks,
Doug Moore

Wrong Google information

Issue in help/using/features/destinations/device-based-destinations-list.md

There in a item for Google in the list that is wrong (or at least confusing):

Google AdsWords Display 02/08/2018 Real-time Yes Yes No Yes

We do not have any S2S integration with Adwords product, since this destination is made via URL destination (https://wiki.corp.adobe.com/display/MCPI/Google+-+AAM+Destination).

The only S2S destination we have with Google, is not for Adwords, but for Google (DBM, DFP, DFP Premium). - https://wiki.corp.adobe.com/display/MCPI/Google+-+AAM+Destination

The S2S fields are not listed in the correct order and are missing some fields

Issue in help/using/reporting/dynamic-reports/segment-segment-overlap-report.md

Here are the fields and their order as that are actually populated in the header of an S2S overlap file:
"segment_id1","segment_name1","segment_id2","segment_name2","rangeid","datethru","segment_uniques1","segment_uniques2","overlap_uniques","Overlap_perc"

I propose that the documentation should be updated to reflect this information correctly.

How do I access the Unused Signals report?

Issue in help/using/reporting/dynamic-reports/unused-signals.md

I see information about what the unused signals report IS and what it DOES, but where can I find it? I've checked a number of different locations in AAM.

The steps for getting to this report, or where it is located, are unclear.

Issue with Bulk Delete Traits

Hello,

I am not sure where your API github is for logging issue with your Audience Manager API.
I am using the adobe.io endpoint and there is an issue when trying to delete traits by bulk, using the bulk delete method

It returns a 403.
My API has Admin right on the Audience Manager side.

Also, I am able to delete the traits one by one. Is there specific permission required for bulk deletion ?
Is it an operation not supported by the new endpoint ?

Best,

Add link to Experience League course

Issue in ./help/using/integration/implement-audience-manager.md

Can we add a link on this page (and/or other pages around it) to point people to the Experience League course called "Guided Analytics Implementation"? It walks them all the way from the beginning through a simple Launch implementation of Analytics. Link for it is: https://experienceleague.adobe.com/?recommended=Analytics-D-1-2019.1

Feel free to give me any and all feedback on the course.
Thanks!
Doug Moore

Pre-requisites are needed

Issue in ./help/using/integration/integration-aep/aam-aep-audience-sharing.md

Customers find it hard what is the minimum set of IDs needed for segments sharing to work between AAM to AEP. For example, is ECID always needed? Will this work if customer has a Declared ID (like CRM ID) but no ecid in AEP?

iFrame source

Issue in ./help/using/features/segments/segment-builder.md

The iFrame available right before the "Segment Builder Controls: Basic Information Section" section, reports the whole page, and not only the video.

Private instead of Public Data Feed

Issue in ./help/using/features/audience-marketplace/marketplace-data-providers/marketplace-data-providers.md

This should be Private Data Feed with no Branding. PFA screenshot.

image

Retain the last clicked topic as selected or keep the scroll near to the position of clicked topic.

Here is another feedback:
Whenever we click on any topic from left side menu, page refreshes and with that refresh my last topic-click doesn’t get retained. Which looks a bit annoying thing because again I have go all the way down or keep on opening the sub-options to reach till that specific topic which I clicked.

Change request: Retain the last clicked topic as selected or keep the scroll near to the position of clicked topic.

image

What are the required fields for inbound batch data transfer?

Issue in ./help/using/integration/sending-audience-data/batch-data-transfer-explained/inbound-s3-filenames.md

Describes the required fields, syntax, naming conventions and file sizes you need to follow when sending data to Audience Manager.

There is nothing on this page about required fields

PMR related update to Segment Builder page

Issue in help/using/features/segments/segment-builder-data.md

Hi there,

I confirmed with Ben and this page: https://docs.adobe.com/content/help/en/audience-manager/user-guide/features/segments/segment-builder-data.html under this section:
Segment Population Data for Merge Rules With a Device Graph Option

in the definition it references:

...with up to 3-other device profiles...

for both Real-Time Population (Existing) and Real-Time Population (Existing) Metric's definition.

3-other devices should be replaced with 100-other devices

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.