Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Audience Manager File-based ID Sync overwriting

Avatar

Level 2

Hello community.

I am looking at file-based ID Sync for people-based destinations and have a question about behaviour of new files over old ones.

Say I have a customer with a hashed email against their Member ID, and on a subsequent file import, this person no longer qualifies for being targeted (no longer a member, or have explicitly requested to not be targeted). How do I remove them from the file? Do I blank out the email address associated with their ID, or do I remove the ID altogether from the sync file?

 

I have looked at some AAM documentation, but nothing seems to explicitly point this out.

https://experienceleague.adobe.com/docs/audience-manager/user-guide/features/destinations/people-bas...

https://experienceleague.adobe.com/docs/audience-manager/user-guide/implementation-integration-guide...

 

Any help on this would be greatly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Level 2

I have just received this from Adobe Customer Care.

 

"The best way is removing the complete record from the file altogether."

View solution in original post

4 Replies

Avatar

Employee

Hello,

If a person no longer qualifies for being targeted, then you can remove it from sync file and then remove it from associated traits. ID sync will be removed after 120 days automatically.

You can onboard a file using d_unsid or sid:0 or sid:-1 to remove the person from the trait. For the details, please prefer the following document.

 

https://experienceleague.adobe.com/docs/audience-manager/user-guide/implementation-integration-guide...

Avatar

Level 2

Hi there @m_nakayama , and thanks for taking the time to respond.

This isn't quite what I was after, I'm not trying to stop them being targeted in our normal onsite personalisation, just on 3rd party platforms with people based destinations.

 

I'll try and rephrase the question.

I have 2 data sources. One that contains all the Member IDs with their associated traits. Another data source contains the Member ID with a hashed email address for use with people-based destinations. It's the second source I'd like to understand how to stop targeting. The file looks like something this (From Step 3 here https://experienceleague.adobe.com/docs/audience-manager/user-guide/features/destinations/people-bas...😞

 

Member ID Hashed Email

6807998276567319850405265607445619603955e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149
6741268208341199572553877044362030758416d72e3edbeb089b299e0d12fc09522fdc5ece2d11dcb1304ecdd6fab4f7193a
89159024796760343733111707646026765593feec5debcea411f54462a345a0d90c9975415d2d4862745ff8af00c49b6b4ae6

 

Is the best way to remove them from this data source, or do I leave their Member ID in the file, but remove the hashed email address?

 

e.g. 1) Remove the hashed email, but leave the Member ID (last row)

Member ID Hashed Email

6807998276567319850405265607445619603955e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149
6741268208341199572553877044362030758416d72e3edbeb089b299e0d12fc09522fdc5ece2d11dcb1304ecdd6fab4f7193a
89159024796760343733111707646026765593 

 

e.g. 2) Remove the Member ID row altogether?

Member ID Hashed Email

6807998276567319850405265607445619603955e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149
6741268208341199572553877044362030758416d72e3edbeb089b299e0d12fc09522fdc5ece2d11dcb1304ecdd6fab4f7193a

 

Hopefully that makes sense.

Avatar

Correct answer by
Level 2

I have just received this from Adobe Customer Care.

 

"The best way is removing the complete record from the file altogether."