Can you state what action makes you think it's blocked? I guess my question is, how are you verifying this isn't working?
My suggestion to test would be to start a Trace when your user is logged in and then view your visitor profile attributes on the left navigation of Trace to see if the "Name" trait is present.
Otherwise all your configurations look correct.
thank you very much for your help.
I have found my problem, i cannot correctly tie the VisitorID to my user.
I have created an "trait" attribute that store the email address of my logged in visitors.
I have created a "VisitorID" attribute that get the email "trait" on every page view.
Using the AudienceStream Trace i can see the email "trait", but the visitorID remain empty.
What am i missing?
It sounds like it's setup correctly. Forgive my lack of knowledge on the account, but is visitor stitching enabled? Without it the data won't be able to sync, which is what I'm assuming is happening. I am working on getting a post approved and published here that discusses the proper steps to enable visitor stitching and hope to have it ready early next week.
great post, now i can verify that my isitorID is stitching in the right way.
Using the visitor trace i see the stitching do his work, but i do not get on my visitor the attributes which i setup in the omnichannel enrichment.
For the test i simply populate an attribute "Name" which get value through omnichannel in association with the visitorID i can see in the trace.
Is there a way to know why i do not get the "Name" attached to my ID?
How do i know if omnichannel fail because it has problem on the connction to the FTP, or with the parsing of the file or anything else?
Thank You very much for your help,
thank you for your help.
Since you are looking at this I have 2 question for you.
1) where do all the data sent to Audience Stream are collected, is the Database location in the US or in another country (EU maybe)?
2) Can i send the Omnichannel enrichment data through an SFTP account?
Thank you very much,
Just to let you know about the previous attribute stitching issue, we are still looking into this for you.
In regard to these latest questions:
1) The data is collected within 1 of 3 regions: eu; us west; us east. It is then distributed across to the other 2.
2) Currently only FTP is supported. If you need a more secure option that we recommend leveraging as S3 bucket.
about the first answer, is it possible to block all the data on 1 region (for example EU). For some client (bank in the first place) should like that theire data do not cross the EU border for privacy reasons.
I clarified with Engineering that any data that originates from a visitor geographically close enough or in the EU that is routed to our EU servers will not replicate outside of that region.
I was re-reading this and noticed this sentence: Using the AudienceStream Trace i can see the email "trait", but the visitorID remain empty.
When you say visitorID, is this a true "Visitor ID" attribute or just a Trait called "visitorID"? The distinction is important because as of now we do not allow updates to be made to "Visitor ID" attributes.
i think a have to make a little recap.
The situation now is that i setted normal trait that is populated with the email of the user (i read it for a query string parameter).
This trait is also mappend to VisitorID attribute named "eMail".
Right now the Visitor Trace is not working so i cannot give you a screenshot, but if I trace my navigation on the site i see my trait and my VisitorID being polpuated and eventual different session for the same VisitorID merged.
After that i configured an Omnichannel enrichment that add to my VisitorID some more information like the name mapped to a normal trait "Name".
I cannot see the "Name" being mapped to my visitorID, if i trace my visits or if I use the Discovery function i cannot see it.
If you want i can give you access to our account in order to let you have a more clear view of our work on the account, i only need an email to send you these information.
Let me know if can help you in any way.