Hi guys- have you seen this:
tried it yet, but in theory you can use the chrome Launch extension in
MS Edge. I found this thread when looking for an answer to this issue
earlier today and thought this might help.
@ipropsectt38068 I was provided the same keys as the ones linked in this
ticket from Customer Care. You could try utilizing the ones provided in
this ticket and if you run into issues open a ticket with Customer Care.
@skandg43264764Yes, I believe it is an Analytics issue, but it only came
into play when Target actions were enabled. As a follow-up, I was able
to rectify the issue by enabling component sequencing in Adobe Launch,
so I believe there was some odd timing issue that was occurring with our
doPlugins set-up. If someone similar runs into a same issue, I was able
to resolve by enabling the "wait, then" behavior that is used by default
with the Adobe Launch change.
For Safari, there is a solution that I just recently uncovered that has
been a lifesaver:https://requestly.io/desktop You can create rules using
the web extension in Chrome or Firefox that basically point the embed
code URL from the production one to staging, and then the desktop app
automatically runs your internet through the proxy in the tool and
applies them. All you need to select is "Request Redirect" and then
enter your production library URL from the embed code setup, and then
Thanks for confirming, it seems like the latter is the better option for
us, as this will be an ongoing identification adding previously unknown
data rather than deleting and needing to reupload data. Thanks again for