Expand my Community achievements bar.

Announcement: Calling all learners and mentors! Applications are now open for the Adobe Analytics 2024 Mentorship Program! Come learn from the best to prepare for an official certification in Adobe Analytics.
SOLVED

Segmenting based on MCVID

Avatar

Level 2

Hi Team,

I have a question in regards segmentation based on Marketing Cloud ID. I would like to to target users who had been previously authenticated as a member however they come back to the site non authenticated.

I will have SiteCatalyst, Adobe Target and AAM

Scenario: a user comes in to the Home page(MID issued), moves into Member's portal when the user gets authenticated --> memberID is issued. Then I will match the memberID with an internal data base to create more specific segments. (age<30 etc.) Then I can create a segment in Sitecatalyst based on memberID (age<30).

However, all our users will come to the website unauthenticated, meaning the memberID will not be set. Can I then somehow use the MID to segment my group and pass it to Adobe Target?

As I know there is no MID available in UI, the MID is only available from the DW. 

Really appreciate your help on this.

Thanks,
jakub

1 Accepted Solution

Avatar

Correct answer by
Level 6

create an entry in your persistent cookie for the member id. Set it to expire say in 90 days. Then every server call pull that memberid value and put it in a prop or evar and use it for your master marketing profile. that way you will always have that id value to key off of. Also setup a 'logged in/logged out' based on where you get the member id from ie the customer is logged out on the home page but you pull the cookie value so they are logged out but have a member id. If they then log in you set them to logged in and save the new member id in the persistent cookie that way if they switch ID's you will record that. send that logged in/logged out and the member id on every server call you make with the master marketing profile and poof you have that available in target and audience manager. 2 props or evars (the member id can be a prop since you really won't be doing any reporting on it by itself since I would assume you could go over the 500K limit. But logged in/logged out would probably be a good evar since you can do your conversions against it though most of the good conversions (spending money, buying stuff etc) are ones you need to be logged in to do.

Also having the member id as something you always send makes it easier to upload your CRM data against it's value in the Master Marketing profile in the cloud.

And if you do put the member ID into an evar you can go one step farther and never set it to never expire so even after the cookie window (my example 90 days) you will still have the member id to report against in analytics and it will still work in segments pushed to the cloud but you won't immediately transfer it to AAM or Target since it won't be in the server call itself. However and I am still trying to get full verification from Adobe I believe that if you are using the server to server analytics to AAM transfer rather than directly calling the DIL code and sending the analytics data to both analytics an AAM that some processing happens before the server to server call and the stored values of evars are pulled into the call so that non-expired value will get sent even if you don't send it in the server call directly. [I may be wrong on that, please check with Adobe and verify]

View solution in original post

2 Replies

Avatar

Level 4

Hi Jakub,

potentially you could pass the MID into a prop and use that to segment based on visitor on their subsequent visit

cheers

Kristi

Avatar

Correct answer by
Level 6

create an entry in your persistent cookie for the member id. Set it to expire say in 90 days. Then every server call pull that memberid value and put it in a prop or evar and use it for your master marketing profile. that way you will always have that id value to key off of. Also setup a 'logged in/logged out' based on where you get the member id from ie the customer is logged out on the home page but you pull the cookie value so they are logged out but have a member id. If they then log in you set them to logged in and save the new member id in the persistent cookie that way if they switch ID's you will record that. send that logged in/logged out and the member id on every server call you make with the master marketing profile and poof you have that available in target and audience manager. 2 props or evars (the member id can be a prop since you really won't be doing any reporting on it by itself since I would assume you could go over the 500K limit. But logged in/logged out would probably be a good evar since you can do your conversions against it though most of the good conversions (spending money, buying stuff etc) are ones you need to be logged in to do.

Also having the member id as something you always send makes it easier to upload your CRM data against it's value in the Master Marketing profile in the cloud.

And if you do put the member ID into an evar you can go one step farther and never set it to never expire so even after the cookie window (my example 90 days) you will still have the member id to report against in analytics and it will still work in segments pushed to the cloud but you won't immediately transfer it to AAM or Target since it won't be in the server call itself. However and I am still trying to get full verification from Adobe I believe that if you are using the server to server analytics to AAM transfer rather than directly calling the DIL code and sending the analytics data to both analytics an AAM that some processing happens before the server to server call and the stored values of evars are pulled into the call so that non-expired value will get sent even if you don't send it in the server call directly. [I may be wrong on that, please check with Adobe and verify]