No. The data that hits our edge currently needs to be XDM. Your data
layer can match our XDM if you want to keep it super simple, or you can
map your data layer into XDM client side. Launch can help with that.
Not as a tag manager. There is a Config ID which needs to be in the data
stream (so the edge knows what rules to apply to it). That ID is created
in the Launch IU but it is a new section separate from the tagging UI.
The migration is meant to work with the Akamai hosting option. If you
are self hosting, you'd need to update the reference on your site to
point to the new host location. Alternatively, you'd have to replace DTM
js file with the Launch js file on your self hosted location.
Try logging out and back in via a new browser or clearing your cache and
cookies. Did the publish complete? If not you can try publishing again
and if it gets stuck again please contact customer care so they can look
at your specific instance.
Are you still experiencing this issue? Typically when you migrate you'll
get everything setup in Launch, test on staging, then publish to
production. Until you publish to production, the DTM library will
continue loading on your production site. After you've published to
production using your Launch instance, it's recommend to go back and
disable your DTM account so someone doesn't accidentally republish that
and overwrite your Launch library.
I believe the data element value is set the first time the data element
is called. From there you can set the storage duration within Launch for
that data element. Since this is happening on the same page you'd likely
need to use the none duration. That way each time the data element is
called it should run the code necessary to retrieve the value from your
Can you provide more context with your error log? In order for the
community to help you we need information on which product you are
using, where the error appeared, and any additional configuration
details you can provide.
We were unable to product this error on several test instances. Try
clearing your cache and cookies and logging out and back in again. Also,
try verifying your permissions in Analytics and Launch. If this issue
still persists, contact Customer Care so they can directly troubleshoot
your specific instance.
After you've completed the migration which ever product (DTM or Launch)
is last to publish will overwrite the file hosted on Akamai (assuming
you are using that). We typically recommend you disable your DTM
environment after converting to Launch so no one accidentally publishes
over the Launch instance again. If you are still having issue with it,
try a new browser or make sure you are fully clearing out your cache and
There are a number if browser plugins you can use to measure page
performance in addition to the built in inspector tools that most
browsers have. The increase in load time will depend on which tags are
being added and how heavy the tag is. Try adding the tags in staging and
measuring with one of the browser extensions.
You might be able to get some additional information from their page on
exchange.adobe.com. Here is the page. It looks like you might be able to
email email@example.com for questions. I'll also email them to see
if they can respond here incase others have the same question.
@TanmayMathur - Anything to add here?
There is a similar question over here that I just responded to -
@kautuk_sahni Incase you have more to add here.
Are you still seeing this issue? Occasionally we've had outages that are
typically fixed very quickly. Have you tried logging out and logging
back in again? Sometimes browsers do funky things with cookies that
cause weird issues. If you are still seeing the issue can you provide
some more information and possibly some screenshots? For example what
all has changed since your last build? Do you need to update and publish
any extensions? Ect.
As far as Launch is concerned, you can have as many environments as
you'd like. By default, there are 3 (Development, Staging, and
Production) however you can create more if you desire. Here is some
helpful documentation around creating and managing environments in
Launch. As for the AEM integration, I'll have to leave that to someone
on the AEM team that is more familiar with it. @kautuk_sahni Do you have
any additional info you could share here? As an alternative, you might
be able to manually...
There are almost an unlimited amount of ways to do most things in
Launch. If you want to have the Analytics Extension run code that sets
variables, you will need to clear those variable first in any rule where
you didn't want those variable included. Alternatively, you could likely
take the code out of the Analytics extension and create rule to
accomplish the same task. This would give you the flexibility of adding
conditions to the rule and only having those variable set when they
should be set...