• Resolved VIDEGRAIN

    (@edouard2)


    Hello,

    I’m using Omnisend for email campaigns and LiteSpeedCache with Cloudlare as Cache solution.

    I would like to add an exclusion in the ‘Drop Query String’ of LiteSpeed Cache because when users click on a link of the email campaign the page is very long to download.

    Can you confirm that a solution is to add omnisend in ‘Drop Query String’ àf LiteSpeed. An d if yes, what text should I add. For example : ‘omnisendContactID’ or ‘omnisend’ or ‘rie.soundestlink’ ?

    Thank you in advance.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support supportomnisend

    (@supportomnisend)

    Hi @edouard2,

    Thank you for bringing this up here on the WordPress forum!

    Based on what you’ve described, we would suggest using the parameter omnisendContactID in the Drop Query String setting of LiteSpeed Cache. This parameter is included in every Omnisend campaign link and remains consistent, which makes it a reliable choice for exclusion.

    After setting this up, we kindly recommend testing the change by sending a real campaign to yourself and checking how the landing page performs.

    Let us know how it goes — or if you have any follow-up questions that we might cover from our side. We’re here to help make things run as smoothly as possible!

    Thread Starter VIDEGRAIN

    (@edouard2)

    Thank you for this answer. It seems to be faster now.

    Also, I would like to know what can be done to reduce loading time for omnisnippet1.com and wt.omnisendlink.com.

    Do you have any advice to reduce this delay (measured with Uptrend) ?

    • This reply was modified 4 days, 20 hours ago by VIDEGRAIN.
    Plugin Support supportomnisend

    (@supportomnisend)

    Hi there,

    You’re most welcome @edouard2 — it’s great to hear things are already feeling faster!

    Regarding the loading time for omnisnippet1.com and wt.omnisendlink.com: our script (or JS snippet) uses lazy loading, also known as asynchronous load (asyncLoad). This means it’s intentionally loaded at the end of the page load process, so it doesn’t interfere with the loading of your site’s core files.

    As a result, the speed at which our snippet loads can depend quite a bit on how optimized the rest of the site is. A lightweight, well-optimized website — with fewer blocking scripts, smaller image sizes, and efficient use of CSS/JS — will allow our script to load and execute more quickly.

    We hope this helps clarify things and gives you a better sense of what’s going on behind the scenes.

    Let us know if you have any follow-up questions — we’re happy to help!

    Thread Starter VIDEGRAIN

    (@edouard2)

    Hello,

    Thank you for your answer. It is clear for me.

    Kind regards.

    Plugin Support supportomnisend

    (@supportomnisend)

    You’re very welcome — great to know everything’s clear now!

    If there’s ever anything else you’d like to discuss or troubleshoot, feel free to start a new thread here on the forum. We’re committed to supporting you — and the wider WordPress community — in getting the best possible results with Omnisend.

    Wishing you great success ahead — kind regards from the team!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.