Skip to content
English
Customer portal
Visit us at Arise GTM
  • There are no suggestions because the search field is empty.

Personalised Hero — Setup & Configuration Guide

Overview

The Personalised Hero shows a hero section that tailors its eyebrow, headline, subheading, and primary CTA to the individual visitor via a personalisation API. Before personalisation loads, and whenever it is unavailable, it shows a fully editable fallback hero, so every visitor always sees complete content.

Best for: homepages, high-intent landing pages, and account-based marketing pages where returning, known visitors should see tailored messaging.

Getting Started
  1. Open any page in the HubSpot editor.
  2. Search for "Personalised Hero" in the module panel.
  3. Drag it onto your page.
  4. Set the fallback content (eyebrow, headline, subheading, CTAs), choose the Page Topic, and confirm the Personalisation API URL (see below).
Field Reference

Personalisation Service

Field What it does
Personalisation API URL HTTPS endpoint that serves the /identify and /generate API. Leave as provided to use the Arise GTM service, point it at your own deployment, or clear it to disable personalisation and always show the fallback.

Content (fallback + topic)

Page Topic, fallback eyebrow/headline/subheading, and primary/secondary CTA text + links. This content shows by default and whenever personalisation doesn't run.

Background / Typography / CTA style / Layout

Solid/gradient/image/video background with overlay, headline size/colours, CTA styles (filled/outline/ghost) and radius, and content position. All are field-driven via CSS variables.

How It Works
  1. The page renders the fallback hero server-side (visible immediately, and to search engines).
  2. In the browser, if a HubSpot visitor cookie (hubspotutk) is present and an API URL is set, the module calls /identify.
  3. If the visitor is recognised and a segment is returned, it calls /generate and swaps in the personalised copy.
  4. If anything is missing or fails, the fallback stays in place.
External Dependencies & Data Flow
Dependency Source Controlled by
Personalisation API (/identify, /generate) The Personalisation API URL (default: the Arise GTM managed service) Arise GTM (or your own deployment if you override the URL)
Google Fonts Only if a Google font is selected Google

How the service is operated: the default endpoint is a supported managed service maintained by Arise GTM on Cloudflare. No secret or token is present in the public page source — the service holds all credentials server-side. You may instead point the field at your own deployment, or clear it to disable personalisation.

Data flow:

  • To /identify: the visitor's hubspotutk cookie (which maps to a HubSpot contact) and the page topic.
  • To /generate: the returned segment and contact fields.
  • Server-side, the service reads HubSpot CRM contact and list-membership data to determine the visitor's segment, and passes context (including the visitor's first name) to an AI model provider — OpenAI or Anthropic — to generate the copy.
  • /generate responses are per-visitor and are never shared or cached across visitors.
  • Retention of request data is governed by the HubSpot portal attached to the CMS (it follows your portal's data-retention settings/policies).
Limitations & Known Behaviour
  • Requires JavaScript and a hubspotutk cookie to personalise; otherwise the fallback shows.
  • Generated subheading HTML is sanitised (basic inline formatting only) before display.
  • Multiple heroes per page are supported.
  • CTA links are always the editor-configured links (never taken from the API).
Troubleshooting
Symptom Likely cause / fix
Always shows the fallback No API URL set, no hubspotutk cookie, or the visitor isn't recognised — all expected.
Personalisation never applies Confirm the API URL is correct and reachable, and that the visitor has interacted with your HubSpot site before.
Brief flash before copy changes Expected — the fallback shows until personalised copy loads.
Support

Provided by Arise GTM. For setup help or to report an issue, contact support@arisegtm.com. Typical response time: within 2 business days (Mon–Fri).

Privacy & Terms
  • Privacy policy: https://www.arisegtm.com/privacy
  • Terms of use: https://www.arisegtm.com/terms-of-service
  • Endpoint operator & support model: Arise GTM — supported managed service (support@arisegtm.com; responses within 2 business days (Mon–Fri); [add stated uptime/SLA]).
  • Identifiers sent externally: hubspotutk cookie (maps to a HubSpot contact), page topic, and contact fields (incl. first name) used for personalisation.
  • AI model provider / subprocessors: Arise GTM (personalisation service) and an AI model provider — OpenAI or Anthropic.
  • Retention: governed by the HubSpot portal attached to the CMS (follows your portal's data-retention settings).
  • Consent basis: [add — the lawful basis / consent mechanism for personalising to identified visitors]
  • Cross-visitor cache safety: /generate responses are per-visitor and are never shared or cached.