IYS compliant trade fair communication: The detail overlooked by the marketing team

Fair marketing teams send tens of thousands of emails and SMS messages throughout the season: registration reminders, program announcements, B2B notifications, post-fair thank-yous. The question is: How many of these communications are covered by legal consent? Has IYS registration been completed? In Turkey, compliance with the Message Management System (IYS) is mandatory for sending commercial electronic messages. The exhibition sector is particularly visible in terms of risk due to high volume registrations and campaign traffic.

Risk often arises not from «malice» but from process disconnections. There's a consent checkbox on the form; consent is recorded in Excel; the campaign is sent from another tool; the IYS update is forgotten. At the moment of an audit or complaint, the chain appears broken. Marketing demands speed; legal demands proof. If the two don't meet in the same record, the problem escalates by season's end.

Is «there's a checkbox on the form» sufficient?

A checkbox is a start; it's not sufficient on its own. The consent record must be processed in IYS, sending must be stopped in case of refusal, and the consent history must be traceable. Keeping an «opted-in» column in Excel is weak evidence during an audit. Without a timestamp, channel (email/SMS), consent text version, and refusal record, the defense weakens.

A common mistake in fair forms is combining commercial communication consent with informational communication in a single checkbox. A visitor might find a commercial campaign added to what they thought was a «program email». Separated text and clear purpose affect both compliance and complaint rates.

IYS integration in QEMENT

The platform automatically processes consents from registration forms with IYS integration. Email (EuroMessage) and SMS templates in the marketing automation module operate according to consent status. The cycle of «we sent it but forgot to enter it into IYS» is broken. This reduces the marketing team's need to consult legal for every campaign; however, it does not remove responsibility for campaign text and segmentation.

The operational gain is that registration and sending meet in the same data model. If consent is in one system and sending in another, synchronization delays create legal risk. Registration + marketing + IYS on a single platform reduces this risk at an architectural level.

Practical checklist

Is the consent text on the registration form clear and separated? (Commercial communication / informational)
Is the consent record kept on the platform or externally?
Are automatic sends to unsubscribed users blocked?
Is the pre-campaign segment filtered based on consent status?
Is the post-fair «thank you + future event» email also subject to the same rules?
Are B2B notifications and marketing campaigns separated in terms of channel and consent?
Is a version record kept when the consent text changes?

The list may seem long; but each item corresponds to a past complaint or audit question. The phrase «We obtained consent» remains weak without these items.

Bridge between marketing and operations

The Consent Management System (IYS) is generally separated from operations as «legal's job». However, consent data is part of the registration form. If the registration platform and the marketing platform are separate, synchronization delays create risk. Operations opens the form; marketing requests the list; IT delays integration. This triangle breaks during fair season.

Practical model: Form design is done with marketing + legal approval; consent processing flows automatically on the platform; campaign sending is linked to the consent filter; opt-outs are removed from the common record. Operations is freed from the task of «manual list transfer»; marketing is relieved from the uncertainty of «are they consented?».

Failure scenarios

Campaign with old list: Last season's Excel is reused; opt-outs are not reflected.
Single checkbox consent: Informative and commercial communications are inseparable.
The post-fair thank you trap: Sales content is added to the 'thank you' email, exceeding the scope of permission.
Forgetting SMS: Email is processed in IYS, but the SMS channel is not managed separately.
Manual exception: An unauthorized 'one-time' message is sent to the VIP list; the exception becomes the rule.

The common thread in these scenarios is the pressure of speed. When the trade fair calendar is tight, compliance steps are left for 'later.' 'Later' usually arrives with a complaint or an audit.

Measurable indicators

Opted-in / Opted-out registration rate
Delay in processing to IYS
Number of blocked sendings after opt-out
Pre-campaign consent filter application rate
Complaint / opt-out volume (per channel)

Send volume alone is not success. Consent-based sending and low complaints are better indicators of sustainable trade fair communication.

Compliance gates in the seasonal calendar

Remembering IYS only on campaign day is risky. Add three gates to the seasonal calendar: consent text approval before form publication, consent filter test before the first bulk campaign, and opt-out list sync before post-fair thank you/future announcement. Without these gates, the marketing calendar overrides legal control.

If an agency or external SMS provider is used, the source of the list must be documented. Exporting from the platform and telling the agency to "send to all" leaves opt-outs behind. Sending based on consent status on the QEMENT side requires the same filter rule to be applied when an external channel is used. Otherwise, internal platform compliance is breached externally.

In mixed lists of international visitors and domestic numbers, channel rules must be evaluated separately. A single segment "SMS to everyone" approach is fragile in terms of both cost and compliance. Segmentation is not only about marketing efficiency but also a legal boundary.

Opt-out channels must also be visible. If "unsubscribe" under an email and IYS opt-out records operate in different systems, the user might think they've opted out of one but continue to receive messages from the other. This inconsistency generates complaints. When consent status is managed from a common record on the QEMENT side, both email and SMS filters are linked to the same truth after an opt-out. If the "blocked sends" line appears in the campaign report, compliance is working; if there are no blocks, the filter might actually be off.

Frequently asked questions

Does a B2B meeting reminder fall under IYS scope?

Evaluation is required based on the nature of the message and the relationship between the parties. Operational notifications and commercial campaigns should not be mixed in the same template pool; clarify with legal.

Do emails sent to participants follow the same process?

Participant communication may be based on a separate contract and consent basis. Nevertheless, channel, opt-out, and record discipline must be maintained.

Does IYS integration automatically make marketing text legal?

No. The integration supports consent processing and the sending filter. Text, segment, and purpose are still the team's responsibility.

Can a campaign be run without cleaning old lists?

It should not be done. Old lists do not carry opt-out and current consent status. First, the consent status should be verified, then the sending should be planned.

Compliance is not a checkbox, but a process

IYS compliance is not 'we checked the checkbox'; it's a process. As the trade fair communication volume grows, manual consent management is not sustainable. A single line extending from the registration form to IYS, from segment to sending, generates both speed and evidence.

Review QEMENT marketing automation and IYS compliance or to review your trade fair communication process contact us.

Legal compliance requirements may be updated; legal advice should be sought for final evaluation.