With the “Page event” element, you react to what a contact does on your page. Maybe they watch your video to the end, open the pricing section or click your call to action. Your page reports this to Quentn, and the campaign moves the contact along accordingly.
For example, you can send everyone who watched your webinar video to the end a different email than those who dropped off. Or you can tag them so you can target them later.
At a glance:
- Behavior, not guesswork: You react to what contacts actually do on your page.
- Events you define: You decide which moments count, for example
video_completedorcta_clicked. - Easy to add: With the AI prompt template, your AI tool takes care of it. For an existing page, one line of code is enough.
- Privacy-friendly: Quentn sets no cookie and only sends the events you explicitly add.
What you use the element for
Your page can report to Quentn what a contact does there, for example:
| Event | Meaning |
|---|---|
video_completed | watched the video to the end |
pricing_opened | opened the pricing section |
cta_clicked | clicked the call to action |
scrolled_to_end | scrolled to the end of the page |
The “Page event” element reacts to an event like this and moves the contact on through the campaign from that point.
Which pages can send events
- Pages of the “Page” element
- Static pages with custom HTML (pages with a path of your choice, including your domain’s home page)
Both must be on your own domain, and the domain must be live.
Note: Landing pages from the drag-and-drop editor can’t send page events.
Requirements
- Your domain is set up and live.
- The “Recognize contacts” toggle is turned on for the domain. You’ll find it in Domain Management. It’s on by default.
- The page is built from custom HTML (see above).
Setup in five steps
Step 1: Add the element
Drag “Page event” from the palette (“AI Code Tools” section) into your campaign.
Step 2: Enter the event name
Enter the name, for example video_completed.
- Allowed characters: lowercase letters, numbers and underscores, up to 64 characters.
- Automatic correction: Quentn converts uppercase letters to lowercase when you save. It also removes spaces at the beginning and end.
- Suggestions: As you type, Quentn suggests names you already use in other page events.
Step 3: Choose the page
| Option | Effect |
|---|---|
| Any page | The element reacts to the event no matter which of your pages it comes from. |
| A specific page | The element reacts only to events from this page. |
The list shows the pages grouped by domain, each with its path and title. Static pages are marked “(static page)”.
Step 4: Add the event to your page
You’re building the page with AI:
The page’s AI prompt template explains the events to your AI tool and lists the names your page events are waiting for.
Tip: Ideally, create your page events before you build the page. If there aren’t any yet, the AI tool picks suitable names itself and tells you what they are. You then enter them in the element.
You already have a finished page:
Add this line to your code where the event happens:
window.Quentn && Quentn.track("video_completed")
Step 5: Publish the campaign
A page event that only exists in the campaign draft doesn’t react yet. It becomes active only once you publish.
On the canvas, the element is then named something like “Page event: video_completed”.
Which contacts are recognized
Events only count for contacts that Quentn recognizes on the page. These are contacts who
- came to the page via a link in a Quentn email,
- came via a redirect element,
- were redirected to the page after confirming the double opt-in,
- were redirected to the page after submitting a Quentn form (landing page or form), or
- submitted a form on the page itself (“Page” element).
Other visitors don’t send events, and Quentn doesn’t store anything for them.
How it works technically: Quentn adds an identifier to these links (the
qtparameter). The page reads it when it loads and removes it from the address bar right away. So it won’t show up in shared links or in your web analytics. Links to pages from the drag-and-drop editor don’t get this identifier.
Good to know
When an event counts
- At most once every 10 minutes: An event counts at most once every 10 minutes per contact, event and page. If someone reloads the page several times or clicks repeatedly, the contact isn’t moved along more than once.
- Once per page view: The page sends each event name only once per page view.
- Only if something is listening: Quentn discards events that no page event in a published campaign is waiting for, without storing anything.
- Preview: In the preview, the page doesn’t send events.
Names and pages
- Multiple pages, same name: Two page events with the same name that wait for different pages don’t interfere with each other. An element set to “Any page” reacts to each page separately.
- Choose shared names carefully: Only use the same name on different pages for the same kind of moment (e.g.
video_completed). Otherwise, a page event set to “Any page” would react to both. - Page deleted: If the selected page is deleted, the element shows “Deleted page” and stops reacting. Choose a different page.
History and copies
- Contact history: Every counted event appears in the contact history as “Page event” with the event’s name. You can search for it specifically using the history filter.
- Copying a campaign: If you copy a campaign with a “Page” element and a page event waiting for that page, the copy waits for the copied page.
- Export and import: When you export and import a campaign, the page selection is lost. Choose the page again afterward.
Privacy
- No cookie: Quentn sets no cookie for page events and doesn’t store anything in the browser. A contact is only recognized during the current page view.
- Nothing automatic: The Quentn script doesn’t send anything on its own, including automatic page views. It only sends the events you explicitly add with
Quentn.track(). - Recognizing contacts on later visits: For this, your page has to store the identifier itself (e.g. in a cookie) and set it again on the next visit with
Quentn.setToken(). Whether you need your visitors’ consent for this depends on the law that applies to you. - Your responsibility: As the page operator, you’re responsible for obtaining your visitors’ consent.
- Turning recognition off: If you don’t want to recognize any contacts on a domain, turn off “Recognize contacts” in Domain Management. Links to this domain then no longer get an identifier, and the pages there don’t send events.
Editorial note: The consent texts (this section, the help text in the element and the note at the domain toggle) still need a legal review before going live.
For developers: the JavaScript interface
On every page built from custom HTML, Quentn provides the window.Quentn object before the page’s scripts run.
| Call | What it does |
|---|---|
Quentn.submit(values) | Sends the form values to Quentn (“Page” element with the form turned on only). Returns a promise. Doesn’t send anything in the preview. |
Quentn.track(name) | Sends a page event. Does nothing if the contact isn’t recognized, in the preview or if the name is invalid. Never throws an error. |
Quentn.token | The current identifier, or null. |
Quentn.setToken(token) | Sets an identifier that the page stored itself (e.g. after consent), or one from the response of a form that wasn’t sent with Quentn.submit() (contactToken field). Returns true if it was accepted. |
Quentn.preview | true in the preview. |
Important:
window.Quentndoesn’t exist while you develop the page locally. So always guard your calls, for examplewindow.Quentn && Quentn.track("video_completed").
FAQ
Can I use the “Page” element without my own domain?
No. Pages built from custom HTML only run on your own domain, and the domain must be live.
I uploaded the page again, but I still see the old version online.
Did you save the element and publish the campaign? The new version only goes live after both.
Images or scripts don’t load on the page.
Usually the paths are absolute (/assets/...). Change them to relative paths (./assets/..., in Vite base: './') and upload the build again.
My page event doesn’t react.
Check these points:
- Is the campaign published?
- Does the name in the element match the name in
Quentn.track()exactly? - Is the right page selected (or “Any page”)?
- Did the contact come to the page via a Quentn link or form? Pages opened directly don’t recognize anyone.
- Is “Recognize contacts” turned on for the domain?
- Did you test in the preview? No events are sent there.
- Has the same contact already triggered the event in the last 10 minutes?
Can I use page events on a landing page from the drag-and-drop editor?
No, only on pages built from custom HTML (“Page” element and static pages with custom HTML).
Can I upload videos?
No. Embed videos from another service instead, for example YouTube or Vimeo.