Skip to main content

Settings

The Settings area is where you configure your project, connect delivery channels, manage teammates, and control how data flows in and out of JourneyLayer. Most settings are scoped to the current project, so make sure you have the right project selected before making changes.

This page gives a short overview of each settings area and links to the detailed guides.

Project settings​

Manage the core identity and credentials of your project:

  • Project name — a friendly label shown across the dashboard.
  • First-party tracker domain — the domain you serve the tracker script from so events come from your own origin. See Tracker domain.
  • API keys — your publishable token (used in browser/mobile SDKs) and server token (used for server-to-server calls). You can rotate either token here if it is ever exposed. See Tokens.
caution

Rotating a token invalidates the old value immediately. Update your installed snippet and any server integrations right after rotating.

SDK / Install​

Get the per-project install snippet for each platform:

  • Web — a small script tag to add to your site.
  • Android and iOS — initialization code for your mobile apps.

The snippet is pre-filled with your project ID and publishable token. See Install.

Allowed domains​

Control which website origins are permitted to send events to your project. Only requests from origins on this list are accepted; others are rejected.

Add your apex domain, www, and any staging hosts. See Allowed domains.

Channels​

Configure the delivery channels that your Campaigns and Journeys use to reach users. Each channel is set up once and then reused everywhere.

ChannelWhat you configure
EmailSMTP credentials or a SendGrid relay. Use the Test button to send a sample message and confirm delivery before going live.
WebhookA URL to receive outbound event payloads.
SMSTwilio account credentials and sender.
WhatsAppWhatsApp business sender configuration.
Mobile PushFCM for Android (upload the FCM service-account JSON) and APNs for iOS (upload your APNs key).
Web PushBrowser push configuration for your site.
tip

Use the Email Test button after entering credentials so you catch authentication problems before a campaign goes out.

Channels configured here are selectable when you build a Campaign or a Journey step.

Users & Roles​

Invite teammates and control what they can do:

  • Invite by email — send an invitation to a colleague. Invites are emailed and the recipient joins your project after accepting.
  • Roles — assign a role to each member for role-based access, so people only see and change what their role allows. The built-in roles are Admin, Creator, Member, Agent, plus any custom roles you create. See Roles & Permissions.

Billing​

Your account Admin can review the current plan, track usage, and keep billing contact details up to date. JourneyLayer billing is manual and contract-based — there is no online payment or card collection. See Billing & My Plan.

Audit logs​

Review a record of important actions taken in the project, such as setting changes, token rotations, and member updates. Use audit logs to answer "who changed this, and when".

CSV uploads​

Import users or build custom-list segments from a spreadsheet:

  • Upload a CSV file of user records.
  • Map the columns to user properties.
  • The uploaded users can be used as a static, custom-list segment for targeting.

This is the quickest way to bring an existing audience into JourneyLayer without writing any code.

Amazon S3 export​

Export your data to your own S3 bucket for warehousing, analytics, or partner integrations. Provide your bucket details and credentials, and JourneyLayer writes exported data to the location you specify.

Marketing Setup​

Define global guardrails that every campaign and journey respects:

  • Send limits — cap how many messages a user can receive in a given period so you don't over-message your audience.
  • Do-Not-Disturb (quiet hours) — block sends during hours when users should not be contacted.

These global rules apply on top of any per-campaign settings, so you can set sensible defaults once and trust that messaging stays within them.

Next steps​