Dynamic variables in form fields | Marker.io Help Center

Inject context, reporter info, and metadata directly into issue descriptions and text fields. No manual copy-paste. No "which browser was this again?" back-and-forth.

💡 Available on Team plan and above.

Syntax

Wrap any variable in double curly braces: {{namespace.path}}

Example:

Input: [{{project.key}}] Bug on {{context.webPage.domain}} - {{context.browser.name}}

Result: [ACME] Bug on careers.acme.com - Chrome

Where to set up dynamic variables

Add variables to your form field mappings in: Dashboard → Website Project → Widget → Form. Variables work in any text-based field — descriptions, single-line text, and multi-line text fields.

Type {{ in any field to open the variable picker and see all available options.

Use cases

Auto-routing by reporter: Include {{reporter.email}} in descriptions. Your Jira automation can route issues to the right team member based on the email.

Support context with custom data: User ID: {{customData.userId}} Plan: {{customData.account.plan}} Company: {{customData.company.name}} Support sees account context instantly. No lookup needed. Set up custom metadata →

Timestamp for SLA tracking: Reported at: {{date.iso}} Machine-readable timestamp for automation rules and SLA calculations.

Audit trail for compliance: Reported: {{date.iso}} by {{reporter.name}} ({{reporter.email}})

Environment info in custom fields: Use {{environment.multiline}} or {{environment.oneline}} in a dedicated "Environment" text field. Keeps descriptions clean while capturing full technical context.

Available variables

Reporter information

Variable	Description	Example output
`{{reporter.name}}`	Reporter's full name	Sarah Chen
`{{reporter.email}}`	Reporter's email	sarah.chen@acme.com
`{{reporter.displayName}}`	Name and email combined	Sarah Chen (sarah.chen@acme.com)

Issue metadata

Variable	Description	Example output
`{{issue.markerId}}`	Unique Marker.io issue ID	MRK-a1b2c3d4
`{{project.name}}`	Project name in Marker.io	ACME Careers Site
`{{project.key}}`	Project key	ACME
`{{issueType.name}}`	Selected issue type	Bug

Date and time

Variable	Description	Example output
`{{date.now}}`	Current date and time	Dec 18, 2024, 3:45 PM
`{{date.today}}`	Current date only	Dec 18, 2024
`{{date.iso}}`	ISO 8601 format (for integrations)	2024-12-18T15:45:30.000Z
`{{date.timestamp}}`	Unix timestamp	1734536730

Browser and device context

Variable	Description	Example output
`{{context.browser.name}}`	Browser name	Chrome
`{{context.browser.version}}`	Browser version	120.0.6099.109
`{{context.browser.userAgent}}`	Full user agent string	Mozilla/5.0...
`{{context.operatingSystem.family}}`	OS name	macOS
`{{context.operatingSystem.version}}`	OS version	14.2.1
`{{context.deviceType}}`	Device category	desktop
`{{context.mobileDevice.model}}`	Mobile device model	iPhone 15 Pro
`{{context.mobileDevice.manufacturer}}`	Device manufacturer	Apple

Page information

Variable	Description	Example output
`{{context.webPage.url}}`	Full page URL	https://careers.acme.com/jobs/123
`{{context.webPage.title}}`	Page title	Senior Developer - ACME Careers
`{{context.webPage.domain}}`	Domain only	careers.acme.com

Viewport and screen

Variable	Description	Example output
`{{context.viewport.width}}`	Viewport width in pixels	1440
`{{context.viewport.height}}`	Viewport height in pixels	900
`{{context.screenSize.width}}`	Screen width	2560
`{{context.screenSize.height}}`	Screen height	1440
`{{context.screenSize.pixelRatio}}`	Device pixel ratio	2
`{{context.zoom.zoomFactor}}`	Browser zoom level	1.25

Integrations

Variable	Description
`{{context.fullStory.sessionUrl}}`	FullStory session link
`{{context.fullStory.sessionUrlAtCurrentTime}}`	FullStory link at exact moment
`{{context.logRocket.sessionUrl}}`	LogRocket session link

Custom data

Pass any data from your application using custom metadata, then reference it here.

Variable	Description
`{{customData.userId}}`	Any custom property you pass
`{{customData.account.plan}}`	Nested paths supported
`{{customData.permissions}}`	Arrays and objects JSON-stringify automatically

Environment summary

Get all environment data in a single variable.

Variable	Description	Example output
`{{environment.multiline}}`	Multi-line format	Device type: desktop ⏎ Browser: Chrome 120 ⏎ Viewport: 1920×1080 ⏎ OS: macOS 14.2
`{{environment.oneline}}`	Comma-separated	Device type: desktop, Browser: Chrome 120, Viewport: 1920×1080, OS: macOS 14.2
`{{environment.json}}`	JSON object	{"Device type":"desktop","Browser":"Chrome 120.0.0",...}

Supported field types

Variables work in text-based fields only: description fields, single-line text fields, and multi-line text fields.

Edge cases

Missing data: If a variable can't be resolved, the placeholder stays intact. {{reporter.email}} with no reporter email becomes literally {{reporter.email}}. Your team sees exactly what's missing.

Invalid paths: Unknown variables like {{context.fake.path}} are preserved unchanged. No silent failures.

Custom data without feature: {{customData.*}} variables only resolve if your plan includes custom data. Otherwise, placeholders remain visible.

How to Report Issues on Mobile

Webhook Notifications

Browser Extensions- FAQs

Intercom integration