This feature may also be relevant for multi-tenancy purposes.E.g. you
have different profile attributes for multiple brands.Brand A has
Interest 1,2,3Brand B has Interest 4,5,6Of course it could be completely
different attributes as well which are only relevant for specific OUs
and should not be shown to others.
If the profile is extended to store custom data like e.g. Interests or
Structural assignments those are not available in the dynamic
reports.Would be very helpful to have those, since the custom files
often are the most interesting ones.
Currently SeedMembers may only use Profile Attributes which are directly
stored on the profile.If you want to have Dynamic content based on
Relations to a custom Schema (e.g. Interests) you wont be able to test
your profiles.As a consequence all those attributes need to be copied
over to the Recipient and Seed Member.
Hi Rudy!I think it's worth noticing that the cookie needs to be present
already before the DTM Tool is loaded.At this point of time the
_satellite.setCookie function is not available. So you need to use
standard JS functions to set the cookie initially.If you set the cookie
after DTM Script include you will loose the initial Tracking request
which leads to wrong analytics data.I'm wondering if there is a way to
set the cookie within DTM. Already tried a Page Load Rule with Top of