Popular

↑↓ move ↵ open All results →

Sales · Sites and ads

Sites, UTM and Conversions API

How to carry UTM tags and form data from a landing page into a bot, see each customer's source and send events to the Meta pixel from the server.

How it works

Someone comes from an ad to your site, fills in a form and moves to the bot. A bot link cannot hold UTM tags and form data, so Bordee passes only a short visit code into the chat. In the chat Bordee recognises the code and joins everything up: the contact gets the name, phone and email from the form, the UTM tags and tags, and the entry's funnel starts by itself.

A form with a phone or email becomes a contact at once, even if the person never opens the chat. When they do, the chat joins that contact.

An entry

Sites and ads → Entries → New entry. An entry is a landing page, a site or an ad link:

  • Bot: where the person lands, a Telegram or Viber bot or a WhatsApp number;
  • Funnel: started instead of the regular /start;
  • After the form: Straight to the bot, or The site's thank-you page with a button to the bot;
  • Contact tags, Sites (domains allowed to send forms) and Form fields: where each field goes in the contact.

The entry's Instruction tab gives ready code with your real addresses for both options, for Tilda and for ad links.

Code on your site

The script goes on every page before </body>, and the form gets the data-crm-form attribute. Copy the exact code with your entry's address from the Instruction tab.

<script src="https://bord.ee/hooks/acme/sites/landing.js" async></script>

<form data-crm-form>
  <input name="name" placeholder="Name">
  <input name="phone" placeholder="Phone" required>
  <button type="submit">Get advice in Telegram</button>
</form>

The name, phone and email fields are recognised by themselves. For the thank-you page option, put a button with the data-crm-chat attribute on it: it leads to the chat with the same visit. On Tilda, use an HTML block with the script and data-forms="all".

Ad links

Without a site, people can go straight from an ad or a bio into the bot, and the link's UTM tags go into the contact. Meta ads accept macros:

https://bord.ee/hooks/acme/sites/landing/go?utm_source=facebook&utm_medium=paid&utm_campaign={{campaign.name}}&utm_content={{ad.name}}

Visits and leads

Sites and ads → Visits and leads lists every arrival: UTM tags, click IDs (fbclid, gclid, ttclid), the page, the form and whether the person reached the chat. Create UTM fields in contacts adds utm_source, utm_medium, utm_campaign, utm_content and utm_term, filled from the first visit.

Facebook Conversions API

Sites and ads → Conversions API: Bordee sends events to the Meta pixel from the server, so ads learn from real leads even when the browser blocks the pixel.

  • Lead when a form is sent; Contact when the person reaches the chat (switched on per entry);
  • the funnel action Event for Facebook, at any step of a scenario;
  • Purchase when a deal is won, with the deal amount.

You need the Pixel ID and an access token from Events Manager; a test event code helps you check the setup with Send a test event. Contact data is hashed before sending. Every event goes to the Event log with its state and Meta's response. If the site has the pixel, the script sends a browser Lead with the same eventID, so Meta counts the event once.