Integrations

Integrations connect RestartiX to your own accounts with other services: ad platforms and analytics tools, Cloudflare, Newsman for email, SendSMS for text messages, and Firebase for your mobile app. Each one uses credentials from your account with that service.

Access: admins only. Other roles who open the page see "You don't have permission to manage integrations."

Go to Settings → Integrations. Each integration has its own card.

How the cards work

• Each card saves on its own, with Save Configuration (or Save Cache Purge and Save Turnstile on the Cloudflare cards).
• Tokens, API keys, secret keys and the service account file are never shown again after you save them. Leave the field empty to keep the saved value; type a new one to replace it.
• Most cards have an enable switch. While it's off, that integration isn't used, even if its credentials are saved. A green notice on the card shows when an integration is active.
• Test Connection tests the credentials you've already saved, not what's typed in the form, so save first. It stays greyed out until the card has been saved once.
• Saves and tests are recorded in the Audit Log.

These services are your own accounts: your organization holds the agreement with each provider. See Annex III: Sub-Processors for what each one receives.

Tracking and consent at a glance

Where each browser-side integration loads, and what it does before and after a visitor's choice in the cookie banner:

Integration	Where it loads	Before the visitor chooses	After the visitor accepts
Meta Pixel	Public site, landing pages, attendee app	Loads and sends a page view, without setting advertising cookies	Sets advertising cookies once the visitor accepts advertising cookies
TikTok Pixel	Public site, landing pages, attendee app	Loads and sends a page view, without setting advertising cookies	Sets advertising cookies once the visitor accepts advertising cookies
Google Tag Manager	Public site, landing pages, attendee app	The container loads with every Google Consent Mode signal set to denied	Signals switch to granted for the categories the visitor accepts
Microsoft Clarity	Public site and landing pages only	Doesn't load	Loads once the visitor accepts analytics cookies
Turnstile	Landing pages with a form	Loads, whatever the visitor chooses	—

Server-side events (the Meta Conversions API and the TikTok Events API) are sent by the platform, not by the visitor's browser, and don't depend on the cookie banner. See Cookie Consent for how the banner works.

Add tracking through these cards rather than pasting tracking code into your landing pages: code inside a page isn't controlled by the cookie banner. See Landing Pages.

Meta / Facebook Ads

Loads your Meta Pixel and sends conversions to Meta from the server with the Conversions API.

Field	What it does
Pixel ID	Your Meta Pixel. Find it in Meta Events Manager → Settings.
App ID	Optional. Your Facebook App ID, used for the Messenger share dialog. Without it, sharing to Messenger opens Facebook's regular share dialog. Find it in Meta Developers → App Settings.
Conversions API Token	Needed for server-side events. Generate it in Events Manager → Conversions API → Generate Token.
Test Event Code	Optional. While it's set, server-side events carry this code so they show in Events Manager's Test Events tab. Clear it when you finish testing.
Enable Meta tracking	Turns the pixel and server-side events on or off.

Test Connection checks the saved Pixel ID and Conversions API Token with Meta. It fails if no token is saved.

What's sent to Meta:

• From the browser (Meta Pixel): a page view on every page, and a CompleteRegistration event when someone registers in the attendee app or submits a landing-page form.
• From the server (Conversions API, only with a token): a CompleteRegistration event for each registration and landing-page form submission, and a PageView for each visit to a landing page that belongs to a funnel. Registration events carry the person's email address and first and last name (all three hashed), an identifier for the registration, the visitor's IP address and browser, and Meta's click ID and cookies when present. Browser and server events share an event ID, so Meta counts each one once.

Server-side events and consent

Server-side events are sent without checking the cookie banner: they run under a legitimate-interest assessment, not cookie consent. Registration events aren't sent for contacts whose processing you've restricted (see GDPR). See Legal Documents for details.

TikTok Pixel + Events API

Loads your TikTok Pixel and sends registrations to TikTok from the server with the Events API.

Field	What it does
Pixel ID	Your TikTok Pixel. Find it in TikTok Events Manager → Web Events → Pixel details.
Events API Access Token	Needed for server-side events. Generate it in Events Manager → Web Events → Settings → Events API → Generate Access Token.
Test Event Code	Optional, for testing only.
Enable TikTok tracking	Turns the pixel and server-side events on or off.

Clear the Test Event Code before going live

While a Test Event Code is saved, TikTok shows your server-side events only in its Test Events tab. They never reach your production reporting.

Test Connection sends one made-up event to TikTok, marked as a test so it stays out of your reporting.

What's sent to TikTok:

• From the browser (TikTok Pixel): a page view on every page, and a CompleteRegistration event when someone submits a landing-page form.
• From the server (Events API, only with a token): a CompleteRegistration event for each registration and landing-page form submission, with the person's email address, name and an identifier for the registration hashed, the visitor's IP address and browser, and TikTok's click ID and cookie when present. There are no server-side page views for TikTok.

Server-side TikTok events follow the same consent rules as Meta's: they don't check the cookie banner, and they skip contacts whose processing is restricted.

Google Tag Manager

Loads your Google Tag Manager container, so you can manage Google tags such as GA4 and Google Ads yourself. RestartiX has no separate Google Analytics or Google Ads integration: use this one.

Field	What it does
Container ID	Your container, in the form GTM-XXXXXXX. Find it in Google Tag Manager → Admin → Container Settings. Required, even to save the card with tracking off.
Enable Google Tag Manager	Loads the container or stops loading it.

The container loads on every page of your public site, landing pages and attendee app, before the visitor makes a cookie choice. It starts with all four Google Consent Mode v2 signals (analytics_storage, ad_storage, ad_user_data, ad_personalization) set to denied, and the cookie banner updates them when the visitor chooses.

Your tags, your settings

Consent Mode only reaches the tags inside your container, and only if they're set up to respect it. It doesn't govern the Meta or TikTok pixels or Clarity. Check each tag you add in the GTM console.

Microsoft Clarity

Session recordings, heatmaps and rage-click detection for your funnel pages.

Field	What it does
Project ID	Your Clarity project. Find it on clarity.microsoft.com → your project → Settings → Setup.
Enable Microsoft Clarity	Loads Clarity or stops loading it.

Clarity loads on your public site and landing pages, only after a visitor accepts analytics cookies. It doesn't load in the attendee app. Set masking to Strict in your Clarity settings so recordings don't capture personal details. Microsoft processes Clarity data under its own terms; see Annex III: Sub-Processors.

Cloudflare Cache Purge

Use this if your public site (webinars.yourdomain.com) is served through your own Cloudflare account. It clears Cloudflare's copy of your pages when their content changes, so visitors don't see outdated pages.

Field	What it does
Zone ID	The Cloudflare zone of your domain. Find it in the Cloudflare dashboard → your domain → Overview.
API Token	A Cloudflare API token with the Zone → Cache Purge permission for that zone. Create it in Cloudflare → My Profile → API Tokens.
Enable Cloudflare cache purge	Turns purging on or off.

Click Save Cache Purge, then Test Connection. The domain to purge is taken from your organization's public site address, so there's nothing else to enter.

Test Connection checks that the token can read the zone's details. A token with only the Cache Purge permission may fail this check even though purging works; adding the Zone Read permission to the token makes the test pass.

What gets purged:

• When you save or publish a landing page, webinar, session or funnel, or clear a page's cache, and when a session changes status: the affected pages of your public site.
• When you save General settings or use Clear Cache there: the entire zone, including anything else it serves, such as your main website.

Turnstile Bot Protection

Cloudflare Turnstile checks that landing-page forms are submitted by people, not bots. It covers the form built into landing pages and custom forms that submit to a funnel. It doesn't cover the attendee app's own registration form.

Field	What it does
Site Key	From the Cloudflare dashboard → Turnstile → your site.
Secret Key	From the same place. Used to verify each submission.

There's no enable switch: protection is on while the keys are saved. Click Save Turnstile.

Most visitors see nothing. A small check appears above the submit button only when Turnstile needs the visitor to confirm they're human. A submission without a valid check is refused and the visitor is sent back to the page with no message; the page address then contains form_error=captcha_required or form_error=captcha_failed. If Cloudflare can't be reached, submissions are let through.

Clear the cache after saving the keys

Your public site keeps a copy of your settings and of each landing page. After you save the keys, click Clear Cache in Settings → General. Until you do, landing pages can show forms without the Turnstile check, and those submissions are refused.

Clearing the Site Key doesn't turn protection off

Submissions are checked whenever a Secret Key is saved, and the dashboard can't remove a saved Secret Key. If you clear only the Site Key, forms stop showing the check but submissions are still checked, so every submission is refused. To turn Turnstile off, ask the RestartiX team to remove both keys.

The Turnstile script loads whatever the visitor chooses in the cookie banner, and each submission's IP address is sent to Cloudflare for the check.

Newsman Email

Sends your organization's email from your own Newsman account: registration confirmations, reminders, "starting now" and replay emails, waitlist emails, segment broadcasts, automation emails and sign-in links. Each email uses a template you create in Newsman; the template IDs are listed in Email Notifications.

Field	What it does
Account ID	Your Newsman account ID. Required.
API Key	Your Newsman API key. Leave empty to keep the saved key.
From Email	The sender address of every email. Required.
From Name	The sender name of every email. Required.
Enable per-org Newsman email	Sends through your account.

While this is off, or before you set it up, emails are sent through the platform's default sending account instead of yours.

Test Connection checks your credentials and lists any required templates missing from your Newsman account. To send a test email, use Email Notifications.

Delivery webhook

After the first save, a Webhook URL appears on the card. Copy it into your Newsman dashboard under Transactional → Webhooks. Newsman then reports what happens to each email:

• opens, clicks, bounces, rejections, spam complaints and unsubscribes update the email's status in your email analytics and on the contact's page
• hard bounces, rejections and spam complaints also flag the contact's email address (see Contacts)
• unsubscribes also withdraw the contact's email marketing consent

Without the webhook, emails still go out, but these statuses aren't recorded. Regenerate creates a new URL. The old one stops working, so paste the new one into Newsman.

Newsman Marketing

Keeps segments in your Newsman Marketing list in step with your RestartiX segments, so you can send campaigns to them from Newsman.

Connect your account

Field	What it does
User ID	Your Newsman Marketing user ID. Required.
API Key	Required the first time; afterwards leave empty to keep the saved key.
List ID	The Newsman list that contacts are added to. Required.
Enable Newsman Marketing sync	Turns syncing on or off.

Click Save Configuration, then Test Connection, which reports how many lists your account has.

The Send email button on a segment's page appears only while Enable Newsman Marketing sync is on and a List ID is saved, although the broadcasts themselves go out through Newsman Email. See Segment Broadcasts.

Map segments

Once a List ID is saved, a Segment Mappings section appears.

1. Click Load Newsman Segments to fetch the segments in your Newsman list.
2. Click Add Mapping.
3. Pick a RestartiX segment under Platform segment... and the Newsman segment it fills under Newsman segment....
4. Repeat for other segments, then click Save Mappings.

Remove a mapping with its trash icon, then click Save Mappings. Admins and marketers can also link a segment from the segment itself with Sync to Newsman Marketing, which creates a matching Newsman segment for you. See Segments.

Unlink before you delete

If you delete a RestartiX segment that's still mapped, the next sync treats it as empty and removes every subscriber from its Newsman segment.

How syncing works

• Only members who have email marketing consent, whose email isn't flagged and whose processing isn't restricted are synced.
• Newsman receives each contact's email address, first name and last name. The name is split at the first space. No other fields are sent.
• Contacts new to your list are imported in bulk and added to the mapped segment; contacts already on the list are added to it. Contacts who stop qualifying are removed from the Newsman segment but stay on your list.
• Someone who unsubscribed in Newsman is never re-subscribed, and their email marketing consent is withdrawn in RestartiX.

Syncing runs automatically, every 30 minutes by default. Settings → Background Jobs shows the current schedule under Sync Newsman Marketing. While the integration is on, Sync Now starts a run in the background for all your mapped segments, and Last sync: shows when the last run finished. Newsman limits how many requests it accepts per minute, so large segments can take several runs. Results appear under Analytics → Webhooks with the source Newsman Marketing. See Segments for more.

Marketing webhook

After the first save, a Marketing Webhook URL appears. Add it in your Newsman Marketing dashboard under Settings → Webhooks. It reports:

• unsubscribes, which withdraw the contact's email marketing consent
• permanent bounces, rejections and spam complaints, which flag the contact's email address

SendSMS

Sends text messages through your SendSMS.ro account: reminders, "starting now" and replay messages, and SMS steps in automations.

Field	What it does
Username	Your SendSMS.ro account username. Required.
API Key	Generate it in your SendSMS dashboard. Leave empty to keep the saved key. A key is needed before you can turn SMS on.
Sender ID	The sender name recipients see: up to 11 alphanumeric characters. Required.
Enable SMS notifications	Turns SMS sending on or off.

Test Connection checks your credentials and shows your SendSMS balance. Delivery reports come back automatically; there's nothing to set up in SendSMS.

Turning SMS on also adds an SMS option to the phone opt-in that attendees see in the lobby, Vrei notificări pe SMS? ("Do you want SMS notifications?"), and to their preferences page. Messages go only to contacts who gave a phone number and SMS consent. See SMS Notifications.

Mobile Push

Sends push notifications to your organization's mobile app through that app's own Firebase project.

Field	What it does
Firebase Project ID	Find it in the Firebase console → Project Settings → General. Required.
Service Account JSON	The private key file from the Firebase console → Project Settings → Service Accounts → Generate new private key. Needed before you can turn push on. Once saved, upload a new file only to replace it.
Enable Mobile Push	Turns push sending on or off.

Test Connection checks that the service account works. It doesn't send a notification. See Push Notifications & Mobile App.

WhatsApp Notifications

This card has only the Enable WhatsApp notifications switch.

Turning it on adds WhatsApp to the phone opt-in that attendees see in the lobby, whose question becomes Vrei notificări pe WhatsApp? ("Do you want WhatsApp notifications?"), or Vrei notificări pe WhatsApp & SMS? when SMS is also on. It also adds WhatsApp to their preferences page and records their WhatsApp consent. That's all it does: RestartiX sends nothing on WhatsApp today, so people who opt in never receive a WhatsApp message, even though the card says attendees can opt in to reminders. Leave it off.

Sharing a webinar on WhatsApp and linking to a WhatsApp group don't depend on this switch. See Share Links & Referrals.