Before you create a campaign
A campaign sends the personal links from a multi-link LinkSet. Create or choose the LinkSet first, then use it as the campaign recipient list.
The LinkSet remains available after the email is sent. You can still export its links or share them through another channel.
Email delivery only: contacts with a permanent email delivery problem are skipped when the campaign is prepared, but their survey links remain available for SMS, messaging or manual distribution.
Prepare the invitation
Choose the sender, subject, message, legal text and email style. You can personalize the copy with contact data and each recipient's survey link.
Hello {{ @contact.name }},
We would value your feedback.
{{ @link.url }}If you leave the survey link out of the message, Dayalogs adds a call-to-action automatically.
Choose an approved sender identity
The shared Dayalogs identity is always surveys@dayalogs.com. You may personalize its display name, but not invent another address on the Dayalogs domain.
On Team and Enterprise plans, a campaign may instead use an active address approved under a ready custom email domain. If its DNS later stops passing the required checks, Dayalogs blocks new branded sends until it is ready again; the shared sender remains available.
Send yourself a test first
A test email lets you check the sender, subject, formatting, personalized fields and survey button without contacting the real recipient list.
Preview sends nothing. A test reaches only the addresses you explicitly provide and does not start the real campaign. To make the check realistic, Dayalogs temporarily copies the complete personalization context of the first eligible LinkSet recipient. Their sample contact fields, tags, survey data and link variables may therefore appear in the test message and survey preview.
Use a trusted test address: the real recipient's personalized URL and token are never reused, and the test cannot change their contact, link, progress or response. The temporary context expires and is never placed in the preview URL.
Inspect the received message and open its survey link before you approve the real send. This catches broken wording, missing personalization or an unexpected survey path. Repeat the test after meaningful edits.
What happens when you send
Recipients are prepared
Dayalogs refreshes the LinkSet and leaves out contacts currently blocked from email delivery.
Messages enter the queue
The campaign starts processing recipients and updates its counters while email is sent.
Larger sends warm up gradually
A small initial batch helps protect sender reputation before the rest continues.
Failures can be retried
Retry sends only to failed recipients. Clone the campaign when you want a separate draft rather than changing the original record.
Once the real send starts, all recipients in that campaign see the questionnaire version that was current at that moment. Publishing a newer version later does not silently change an invitation already in progress.
Read the delivery status
Delivery is not the same as engagement
Delivered means the recipient's mail server accepted the message. It does not prove that the person opened it or clicked a link.
When explicitly enabled by Dayalogs, campaign results label image detections as Estimated opens. Image blocking and text-only clients can miss opens, while privacy proxies, image caches, security tools and preloaders can create or collapse events. These figures never prove that a person read the message. Test emails are not tracked.
Real campaign emails route eligible HTTP and HTTPS links through an opaque Dayalogs redirect. Campaign results show total and unique clicks, each logical link, first and latest click, and approximate device and country breakdowns.
The redirect still works when copied into WhatsApp, SMS or another browser, although every click remains attributed to the original campaign recipient. Security scanners and link previews may also follow links, so these figures are engagement signals rather than proof that a person clicked.
Dayalogs does not retain the click IP as campaign history, nor does it retain the full user agent or referrer. When country enrichment is enabled, the IP is accepted only as encrypted retry data during a five-minute window and is then discarded by the worker. The campaign keeps only a coarse device class and two-letter country code, or unknown when resolution fails. SES open IP addresses and user agents are discarded before persistence; Dayalogs keeps only the event time and per-recipient estimated-open aggregates.
IP address country data powered by IPinfo.