Rolex mu-plugin

  • Resolved ryandesigned

    (@ryandesigned)


    1 year, 3 months ago

    Hello,

    We are are currently using the updated version of your Rolex integration and it was working great, thank you!

    However, Rolex it seems it is deploying the Adobe Launch on a particular page that already contains it, due to a Rolex iFrame. Can we prevent the Adobe launch code from deploying on that one particular page while making sure Hybrid Cobrand line is still implemented there?

    Thanks so much for your help.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @ryandesigned,

    For a bit more detail, are we talking about: <script src="//assets.adobedtm.com/7e3b3fa0902e/7ba12da1470f/launch-5de25****d80.min.js"></script>

    As I understand it this should be added on HTML pages only, by the user. Complianz doesn’t enqueue the script, just handles its release on HTML, and Rolex uses the set Rolex consent cookie to handle it in the iFrame.

    So I would expect the code is implemented site-wide, but must be removed from iFrame pages.

    Is this correct, or didn’t I understand the question? regards Aert

    Thread Starter ryandesigned

    (@ryandesigned)

    Thank you so much for the answer and clarification, I just wanted to rule out that the plugin doesn’t enqueue the script. We have resolved the issue!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Rolex mu-plugin’ is closed to new replies.