Connect your website

Open Automations → Website. You need CRM configure permission.

Add your domains

Add the domains of your own websites, for example yourbrokerage.com. A domain includes its subdomains, such as www. You can add up to 10.

We keep page visits only from these domains. A link in your email to one of these domains also tells us who clicked.

Each domain shows when it last sent a page view, a click and an event. If a domain shows "No page views yet", check that the script is on that website.

Add the tracking script

Copy the script from the Tracking script section. Put it on every page of your website, in the page head or before the end of the body. The script needs no key.

If your website uses Google Tag Manager, you can add the script there. You do not need to change your website:

1. Make a new tag. Select Custom HTML.
2. Paste the script.
3. For the trigger, select All Pages.
4. Save the tag. Then select Submit to publish it.

The script gives each browser a random visitor ID. It keeps the ID in a cookie on your website.

Choose what the script records

In the Tracking section, each change saves at once. It reaches your website within 5 minutes. You do not need to change your website.

• Track page visits. Turn it off to stop all website tracking. The script then sends nothing.
• Track clicks. Clicks on links and on buttons that you mark. See Clicks.
• Wait for each visitor's consent. The script keeps and sends nothing until your website calls berchtold.consent(true), for example from your cookie banner. berchtold.consent(false) stops tracking and removes the visitor ID.
• Analytics events. Your website may already send events to its analytics, for example generate_lead. Add their names here. Type each name as your analytics sends it. See Events.

How a visitor becomes known

A visitor is known after one of these:

• They send one of your forms. A Berchtold form works on any of your domains: as a link, an embed, a popup or plain HTML. The script tells the form who the visitor is. You need no key.
• They click a link in your email that goes to one of your domains.

Then each page they visit goes on their contact timeline. A visit can start an automation with the trigger A known visitor views a page.

Before we know a visitor, we keep only their last 20 pages. These go on the timeline as one entry when the visitor becomes known. Visits from unknown visitors do not start automations.

Clicks

The script also records a known visitor's clicks. Each click goes on their contact timeline. Use the Clicks filter on the timeline to see them.

• A click on a link records the link's address. A click on a phone or email link records the number or address.
• To record a click on a button, add data-berchtold-event with a name, for example <button data-berchtold-event="schedule_showing">.
• If your website already sends click events to its analytics, we use them. An event whose name ends in _click, such as cta_click, names the click. Its label (cta_label, link_text, label or button_text) shows on the timeline, for example "Clicked “Get my home value”".
• To stop recording clicks on part of a page, add data-berchtold-ignore to it.

A click can start an automation with the trigger A known visitor clicks. We do not keep clicks from visitors we do not know yet. The same click within one minute counts one time.

Events

An event is something a visitor did, for example asked for a showing or saved a home. Your website can send events in two ways. Neither needs a key:

• From your analytics. Add the event's name under Analytics events. When your website sends that event to Google Tag Manager or Google Analytics, the script sends it to us too.
• From a page. After the script loads, call berchtold.track("schedule_showing", { listing: "123 Main St" }).

We keep only flat values: text, numbers and yes/no. We do not keep values with names such as email, phone or name.

An event from a known visitor goes on their timeline. It can start an automation with the trigger The website records an event. We do not keep events from visitors we do not know yet.

Server events

This part is for developers. Most websites do not need it. You need a server key only when your website's own server sends forms or events to us. For example, a headless website, or a WordPress form plugin that sends its forms to us.

Open Server events, then select Show the server keys and the events API. You must be a workspace admin.

1. Select Make a server key.
2. Copy the key. We show it one time only.
3. Put it in your website server's secret settings, for example an environment variable or wp-config.php on WordPress.

The same key also gets page summaries. Make one key for each website. Keep the key on the server. Do not put it in a web page: a server key does not work from a browser.

To change a key without a break, first make a new key and put it on your server. Then revoke the old key. If a key gets out, revoke it at once.

A chat key is different. It goes in your web page for the chat widget, and it works only for chat.

A server event names the person by their email address:

• We record the event only for an existing contact.
• Give each event its own id. We record each ID one time.
• Add up to 30 values in data, such as the listing address.

Privacy

The script does not run when the browser asks sites not to track it. To turn it off on a page, set window.berchtoldTracking = false before the script loads. To ask each visitor first, turn on Wait for each visitor's consent.

We remove URL queries and fragments, except the public listing ID on an iHomefinder property page. This keeps the property link useful. Other values, such as email addresses and tracking codes, are removed. The script does not read form fields or page text. We do not keep IP addresses.