supportomnisend
Forum Replies Created
-
Forum: Plugins
In reply to: [Email Marketing for WooCommerce by Omnisend] Submit and signup rateHi @papadopoulos ,
Really glad the explanation helped clear things up! If any other questions come up while you’re rebuilding things, feel free to drop them here anytime.
Forum: Plugins
In reply to: [Email Marketing for WooCommerce by Omnisend] Submit and signup rateHi there,
Great question – the two metrics sound very similar, but they actually measure different things in the form journey.
The Submit rate measures the percentage of visitors who clicked the Submit button on your form.
The Signup rate measures the percentage of form viewers who became new subscribers — meaning new contacts added to your Omnisend audience.
For example:
If an existing subscriber fills out and submits the form again, they will count toward the Submit rate, but not the Signup rate, since they were already on your contact list.So in short:
- Submit rate = form submissions
- Signup rate = new subscribers gained
Looking at both together can give you a better understanding of how effectively your forms are converting brand-new visitors versus already existing contacts. If anything else around form reporting feels unclear, we’re always happy to help.
Hi @exploradora,
Thanks for checking, this is a very common point of confusion when exporting emails from Canva.
At the moment, Omnisend accepts only the HTML code itself and cannot process attached image folders or local image files during import. This means the images from Canva’s exported folder will need to be hosted online first, and the image paths in the HTML updated accordingly.
Here are the available approaches:Option A: Upload images to Omnisend
- In Omnisend, create a new Email Campaign
- Add an Image block and upload each image manually
- Right-click the uploaded image and copy its URL
- In your HTML, replace local image paths (for example
images/photo.jpg) with the Omnisend-hosted image URLs
Option B: Use external image hosting
You can also upload the images to:
- your own website/server
- Imgur
- Cloudinary
- another image hosting service
Then simply replace the local image references in the HTML with the full hosted URLs (for example
https://yourdomain.com/image.jpg).In short: the HTML import works perfectly fine, but the images must already be accessible online via direct URLs before the email can render correctly inside Omnisend.
If anything feels unclear while preparing the HTML, we’re always here to help you get everything rendering properly.
Hi @jurrevdv ,
Great question, this comes up quite often when setting up automations after your store already has activity.
- For event-based automations (like Order Placed or Subscribed):
You can enable “Trigger retrospectively” in the Trigger block settings. This allows contacts whose event happened within the first delay window to enter the workflow. - If you need to include contacts immediately or the automation doesn’t support retrospective triggering:
You can create a segment-based automation and enable “Trigger workflow for contacts in the segment”. This will include existing contacts who meet the criteria.
We’ve also prepared a guide that walks through how to run automations for past events (retrospective triggering) in more detail:
https://support.omnisend.com/en/articles/4294537-run-automations-for-past-events-retrospective-triggeringThis way, you can make sure your automations also capture contacts who were already active before the workflow was set up. If anything comes up while setting this up, we’re always here to help.
Hi @frbaguetix,
Great question, it’s always good to double-check where that data is landing.
You can find custom properties directly in a contact’s profile. Just go to:
Audience → Contacts → click on a contact
In the contact profile, look at the left-hand panel and scroll down to the Details section, that’s where any custom properties synced from your integrations will appear.

If you’re not seeing them there, it may be worth checking whether at least one contact has already received that data, as custom properties appear once they’ve been populated.
If you run into anything unclear or need a hand checking the setup, we’re here for you.
Forum: Plugins
In reply to: [Email Marketing for WooCommerce by Omnisend] Custom segmentationHi @davelo,
First of all, thank you so much for the kind words about our presence on the ww.wp.xz.cn forum, we truly appreciate it. And thank you as well for your patience while our team reviewed your use case in more detail.
Based on what you shared with us, we’d suggest the following approach:
B2B / B2C segmentation
A practical way to distinguish B2B from B2C contacts would indeed be to use the Company Name field from WooCommerce.
You can first check whether this field is being synced to Omnisend as a contact property by either:
- opening a contact’s activity/profile page, or
- checking the available contact properties in segment rules and looking for Company Name (it may appear under custom properties).

If it is available, you can create a segment like:
Company Name → exists
This segment will dynamically include all contacts where the company field is filled in, which can reasonably be treated as your B2B audience.
If you’d like to build an automation for this segment, you can set it up as follows:
- Go to Automations → Create Workflow → Create from Scratch
- Choose a segment-based trigger
- Select your B2B segment
- Optionally enable “Trigger workflow for contacts in the segment” if you’d like current B2B contacts to enter the workflow right away
This ensures the automation runs whenever a contact qualifies as B2B. Depending on your exact goal, there are a few different ways this can be configured.
Important: we recommend reviewing the frequency settings carefully, so contacts don’t re-enter the workflow unnecessarily if the segment logic changes later.
Language segmentation
For language, the most accurate and manageable options would be:
- segmenting based on Country if that property is available from billing or shipping details, or
- collecting language directly through signup forms or the checkout page
You can also use custom properties for this. Once at least one contact has such a property, it becomes available for segmentation and automation triggers in Omnisend.
From there, you could create for example:
- Segment: Language is NL
- Segment: Language is FR
These segments can then be used in several ways:
- for campaign targeting (include or exclude segments)
- as automation triggers
- as conditional splits inside workflows
We’ve shared the general direction that would make the most sense based on your setup. And if anything feels unclear or you run into any challenges while putting this in place, we’ll be very happy to guide you step by step so your segmentation and automations work in a way that truly supports your business needs.
Thanks for confirming, we’re really glad to hear everything is now working as expected.
We also appreciate you sharing your feedback regarding the WooCommerce hook placement. That’s a great observation, and we’ve passed it along to our product team for consideration in future improvements.
Regarding your question about identifying B2B vs B2C users and handling different languages (NL/FR), could you please share a bit more detail on what you’d like to achieve? With a bit more context, we’ll be happy to look into it and suggest the best approach for your setup.
Looking forward to your reply so we can help you find the best approach.
Hello @davelo,
We’d like to let you know that our team has implemented a fix, and the issue was resolved promptly on the same day it was identified.
When you have a moment, we’d appreciate your confirmation that everything is working as expected, and we’ll be here if anything still needs attention.
Hi @davelo ,
Thanks for sharing your Brand ID. We’ve passed this over to our technical team for further investigation and will get back to you as soon as we have an update.
In the meantime, if anything else comes up or you notice any changes, feel free to reach out, we’re just a message away.
Hi @davelo ,
Thanks for joining the thread and sharing these details, really helpful context.
We’d like to take a closer look at this on our end. Could you please share your Omnisend Brand ID with us? We weren’t able to locate your account in Omnisend using the store URL or name, so sharing your Brand ID will help us find it and look into this more efficiently.
You can easily find and copy it by clicking on your store’s name in the Omnisend app.

Once we have your Brand ID, we’ll investigate this further on our end and keep you informed as we continue working through this with you.
We’re so glad Melanie could make your onboarding that smooth! Getting set up in days instead of weeks means you can focus on what matters most, running your business. Thanks for trusting us with your migration. We’re here to support your success every step of the way.
Welcome back! We’re really glad the migration team made your return seamless. Sometimes it takes trying something else to realize what works best for your business. The combination of simplicity, value, and real support you experienced is exactly what we’re here for. Excited to keep supporting your success moving forward.
Thanks so much for sharing your experience! We’re glad the migration went smoothly and that our team has been there when you needed them. Consistent support makes all the difference when you’re focused on running campaigns and driving results. We’re here for the long run!
Hi @chopperstwisted ,
Thanks for bringing this to our attention, we sorry to hear you’re running into this connection issue. To help our clients resolve WooCommerce connection issues more quickly, we’ve prepared a step-by-step guide that covers the most common causes and how to fix them.
Please follow the instructions in this article: https://support.omnisend.com/en/articles/13336186-troubleshoot-woocommerce-wordpress-connection-issues
If the issue persists after going through these steps, feel free to share the following so we can investigate further:
- Your Brand ID (you can easily find and copy it by clicking on your store’s name in the Omnisend app)
- Screenshots of the notices shown in both the Omnisend app and on the WooCommerce plugin page.

Please keep us posted! If the issue isn’t resolved after following the steps in the guide, feel free to share the requested information so we can continue working through it with you.
Forum: Plugins
In reply to: [Email Marketing for WooCommerce by Omnisend] Too many DNS lookupsHi there,
Thanks for reaching out about this. The “too many DNS lookups” error usually occurs when the SPF record for your domain exceeds the limit allowed by the SPF standard.
Another possible SPF issue can occur due to too many DNS lookups. The SPF standard limits your record to a maximum of 10 DNS lookups. Each include:, a, mx, ptr, exists, or redirect mechanism in your SPF record counts as one lookup.
If your record exceeds this limit, SPF validation will fail even if the record itself appears correct.

In simple terms, your SPF record helps email providers verify whether the sending service is allowed to use your domain. When there are too many SPF lookups, the receiving mail server must check too many external DNS sources to confirm who can send on behalf of your domain.
As a result, the receiving server may skip SPF validation or reject the message entirely.
Example of a problematic record:
v=spf1 include:_spf.google.com include:mailgun.org include:test1.net include:test2.com ~allEach include tells the receiving server to perform another lookup. If there are too many, the SPF record becomes invalid.
To fix the error, review your SPF record and remove any unused or unnecessary include entries. For example, if you previously used another email service that is no longer active, its include line should be removed.
Keep only the entries for active services, such as Omnisend and your primary email provider.
Example of a valid SPF record:
v=spf1 include:_spf.google.com include:mailgun.org ~allThis version is shorter and remains within the 10-lookup limit.
If you need to keep multiple SPF entries because all services are actively used, another option is to set up a dedicated subdomain for Omnisend. When doing so, make sure to add the appropriate MX records to that subdomain. If you’re unsure which MX records to use, you can copy them from your root domain or check with your domain provider.
If you’d like us to take a closer look at your DNS setup and guide you through the adjustments, our support team will be happy to help. You can reach us via in-app chat or by emailing [email protected], where we can review your records privately and assist you step by step.