Developers

Connect your website

Send enquiries from your website into FullArc, and see which page produced each one. No developer needed for the first way.

Last updated August 20, 2026

In one minute

No developer? Turn on the FullArc form and paste its link. Have one? Create website a tracking token and a lead token, add the script to every page, and post enquiries from your server. Both are in Settings → Integrations → Your website.

Which one?

WayForWhat it takesWhat you get
FullArc formAnyone — no developer neededPaste a link or an embed codeEnquiries in Leads
Tracking scriptAnyone who can add one line to their siteOne script tag on every pageWhich pages each visitor saw, and taps to call or text your phone number
Your own formSites with a developer and a serverOne API call when the form is sentEnquiries in Leads, from the form you already have

They combine. The tracking script is what lets a lead say which page produced it, and it does that for enquiries from the FullArc form and from your own form alike.

Everything is set up in Settings → Integrations → Your website. You need permission to edit settings, which account owners and admins have.

The FullArc form — no code

Press Turn on the form. You get a link and an embed code. Put the link on a “Contact us” button, or paste the embed code into any HTML or embed block — Wix, Squarespace and WordPress all have one:

<iframe src="https://getfullarc.com/form/YOUR_FORM_KEY" title="Contact form"
        style="width:100%;min-height:680px;border:0"></iframe>

It asks for a name, an email address or a phone number, and a message. Each enquiry arrives in Leads as a website-form lead, and your lead settings apply to it as usual: who it is assigned to, who is notified, and the acknowledgement email if you have turned that on.

  • Spam is handled with a field people cannot see and a limit on how often one connection can send. Enquiries are never filtered on what they say — a filter that throws away a real customer costs more than a junk lead.
  • Turning the form off stops every link and embed at once. Turning it back on gives a new link, which is also how you retire a link that has started attracting spam.
  • With the tracking script on the same page, the enquiry is joined to the visit that produced it automatically.

The tracking script

Enter your website address and press Create tracking token. You get the FullArc URL, the token, and the tag with both already in it. Paste the tag on every page, in the head or before the closing body tag:

<script async src="https://getfullarc.com/fa.js"
        data-token="YOUR_SITE_TOKEN"
        data-site="yourwebsite.com"></script>

This token is public on purpose — it sits in your page source where anyone can read it. That is safe because it can only record visits, cannot read anything back, and is refused from any domain but yours.

It records the page someone landed on and the pages they viewed, where they came from (referrer, campaign tags, Google Ads click id), whether they were on a phone or a computer, and taps on phone-number links, to call (tel:) or to text (sms:). It sets no cookies: it keeps one random id in the visitor's browser storage.

To join an enquiry from your own form to the visit, add an empty hidden field and the script fills it in:

<input type="hidden" name="fullarc_session">

Call tracking

For many businesses most enquiries are phone calls. With the tracking script on your site, mark each phone number like this and a visitor sees a tracking number that ties their call to the visit:

<a href="tel:+19025550100" data-fa-number>902-555-0100</a>

The call rings through to you and arrives in Leads, joined to the page the caller was on. Your own number stays in the page and shows whenever no tracking number is available — the script only replaces it once one is ready, so tracking never costs you a call.

Tracking numbers are set up by FullArc: write to support. Settings → Integrations → Your website shows whether call tracking is on for your account.

Your own form, from your server

Press Create lead token on the same screen. When your form is sent, your server posts the enquiry to FullArc with it:

POST https://getfullarc.com/api/v1/leads
Authorization: Bearer YOUR_LEAD_TOKEN
Content-Type: application/json

{
  "channel": "WEBSITE_FORM",
  "contact": { "name": "Jane Doe", "email": "jane@example.com", "phone": "902-555-0100" },
  "message": "What they typed",
  "sessionId": "the value of the fullarc_session field"
}
  • Never put the lead token in a web page. Anyone who can read it can fill your leads with junk. Keep it in your server's environment settings. If it ever appears in page source, revoke it and create a new one.
  • sessionId goes at the top level, not inside anything else. Without it the lead is still recorded, just not joined to a visit.
  • A name and an email or phone are required. Everything else is optional. The full field list is in the API documentation.
  • Supplying a phone number is not permission to text. Only a separate, unticked checkbox the person ticks themselves is — see smsConsent in the API documentation.

Tokens: creating, losing and revoking

The two tokens are created separately — make the one your site needs, or both. The tracking token is locked to your domain and can only record visits; the lead token can create leads and nothing else. Neither can read your data, send email, or reach anything outside your account. The screen suggests a variable name for each value: the tracking ones start with NEXT_PUBLIC_ because they are public, and the lead ones must not.

Use the same names on every site, so any site can be read and fixed the same way:

  • NEXT_PUBLIC_FULLARC_URL: FullArc URL (the origin, e.g. https://getfullarc.com). Optional; where fa.js loads from. Defaults to https://getfullarc.com.
  • NEXT_PUBLIC_FULLARC_SITE_TOKEN: Tracking token (web_sessions:write, pinned to your domain). Every site: the fa.js tracking script.
  • FULLARC_API_URL: API URL (the origin, e.g. https://getfullarc.com). Optional; where leads are posted. Defaults to https://getfullarc.com.
  • FULLARC_API_TOKEN: Lead token (leads:write, subscribers:write, newsletters:write; also emails:send when the account's own sending domain is verified). Every site with its own form: POST /api/v1/leads, /api/v1/leads/events, /api/v1/subscribers, /api/v1/newsletters (drafts) and its own emails, from the server.
  • FULLARC_LISTINGS_TOKEN: Listings feed token (listings:read). Rentals sites reading the vacancies feed.
  • FULLARC_FORM_URL: Hosted form URL (https://getfullarc.com/form/<key>). Sites embedding FullArc-hosted forms.

Each is shown once. We keep only a fingerprint of each, so we cannot show them again. If you lose one, revoke it in the list on the same screen and create a new one. Revoking takes effect immediately — revoking the lead token stops your site sending enquiries until you replace it.

What to tell your visitors

The people who fill in your form are your customers, so you decide what is collected and why; FullArc processes it on your behalf. See the privacy policy for how that works.

If you use the tracking script, say on your own privacy page that your site keeps a random visit id in the browser, and that the visitor's IP address is recorded and deleted automatically after 90 days. The FullArc form states who receives the details on the form itself.

Show your vacancies — Rentals accounts

If your account has Rentals, your website can show the listings you publish in FullArc, so each unit is written up once. In Settings → Integrations → Your website, press Create listings token. It can only read listings, and only published ones — available, application pending or leased. Drafts and withdrawn listings are never in the feed.

GET https://getfullarc.com/api/v1/listings?status=AVAILABLE
Authorization: Bearer YOUR_LISTINGS_TOKEN

Call it from your site's server and keep the result for a while — rebuilding the page every hour is plenty. A page that fetches the feed from the visitor's browser publishes the token with it.

  • status — AVAILABLE, APPLICATION_PENDING or LEASED. Anything else returns all three.
  • slug — one listing, by the name in its link.
  • limit (default 50, at most 200) and offset — for paging.
{
  "success": true,
  "data": [
    {
      "slug": "384-hammonds-plains-road-upper-bedford",
      "status": "AVAILABLE",
      "headline": "3-bedroom upper unit in Bedford",
      "rent": 2450,
      "rentIncludes": [
        "Heat",
        "Hot water"
      ],
      "availableFrom": "2026-10-01T00:00:00.000Z",
      "photos": [
        {
          "url": "https://getfullarc.com/api/public/listing-photos/your-account/…",
          "alt": "Front of the house"
        }
      ],
      "unit": {
        "label": "Upper",
        "bedrooms": 3,
        "bathrooms": 1.5,
        "sqft": 1200
      },
      "property": {
        "addressLine": "384 Hammonds Plains Road",
        "city": "Bedford",
        "community": "Bedford"
      }
    }
  ],
  "pagination": {
    "total": 1,
    "limit": 50,
    "offset": 0,
    "hasMore": false
  }
}

To send an enquiry about one listing — an “Ask about this unit” form — post it to /api/v1/leads as usual, with the listing's slug in the context: "context": { "listingSlug": "384-hammonds-plains-road-upper-bedford" }. It arrives in Leads linked to that listing, and shows on the listing's page in FullArc.

Photos come in the order you set, each with the description you wrote for it. Their links work while the listing is published and stop when it is withdrawn. The API reference lists every field.

Applications and viewings — Rentals accounts

With the FullArc form on, every published listing has a rental application form and a viewing booking page, run by FullArc for you. Each listing's page in FullArc shows both links and their embed codes under Links for this listing, so there is nothing to build:

https://getfullarc.com/form/YOUR_FORM_KEY/apply/LISTING_WEB_ADDRESS
https://getfullarc.com/form/YOUR_FORM_KEY/viewing/LISTING_WEB_ADDRESS

Put the links in your ads, or embed the forms in your own site's listing pages. Add ?embed=1 when you embed: the form drops its own card and fits the page around it.

<iframe src="https://getfullarc.com/form/YOUR_FORM_KEY/apply/LISTING_WEB_ADDRESS?embed=1"
        title="Rental application" data-fullarc-form
        style="width:100%;min-height:720px;border:0"></iframe>
  • It sizes itself when the tracking script is on the page. Without the script, add this once to the page and the form grows with its content instead of scrolling inside itself:
    <script>addEventListener("message",function(e){if(e.origin!=="https://getfullarc.com"||!e.data||e.data.type!=="fullarc:form-height")return;document.querySelectorAll("iframe[data-fullarc-form]").forEach(function(f){if(f.contentWindow===e.source)f.style.height=e.data.height+"px"})})</script>
  • It looks like your site. The forms take their style from your brand kit (Settings → Brand Kit), the same place your emails take theirs: primary colour for buttons, accent for highlights, secondary for headings, plus the text, background and button text colours, the font and the corner radius.
  • Applications are stored encrypted in FullArc and reviewed there. Each applicant gives written consent to the checks in the form itself, and each other adult on the lease gets their own link to apply. Nothing about the applicant passes through your site.
  • Viewings offer the times set on Rentals → Viewings, one booking per time. The renter gets a confirmation with a link to cancel, and a reminder the day before.
  • If your site sets a Content-Security-Policy, allow https://getfullarc.com in frame-src.

Getting help

Stuck, or seeing something this page does not describe? Write to support@getfullarc.com with your website address and what you tried.